Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting error: folder named does not exist #14

Open
wmoindrot opened this issue Sep 2, 2016 · 5 comments
Open

Getting error: folder named does not exist #14

wmoindrot opened this issue Sep 2, 2016 · 5 comments

Comments

@wmoindrot
Copy link

Hi, we got our hosted server moved from NA to Europe server: https://lstmed.cloud.panopto.eu/. Now we're finding that the Scheduling Tool is not finding supplied recording folders on the server unfortunately.

Getting error: "Folder does not exist
The folder named 'Wills PTM3' does not exist for recording 'Introduction to malaria'. Would you like to use the default folder instead?"

Any ideas? Thanks, Will

Downloaded the Jan16 version (most up to date?)
Updated all of the .config to our new server
Have tried to use the default #Test folder, but then get message: "An error occurred. Details: The folder named '#Test' does not exist. This folder must exist as the default location for recordings."
Verify login passes ok
Very simple CSV schedule (see attached), recording folder name is correct
Have tried supplying folder ID instead but gives same error.

@hohno-panopto
Copy link
Contributor

Hi Will,
Thank you for the report. Could you contact our support team so that they may investigate your situation further?

@wmoindrot
Copy link
Author

Hi Hiroshi-p, have just done this. Thanks!

@mvl22
Copy link

mvl22 commented Oct 6, 2021

We've run into exactly the same problem. Is there any resolution or identification of the cause yet? @Panopto

The folder definitely exists (I've done a diff of the name and it is identical). I've done a similar test with a single entry in the CSV file.

PS It would be helpful if the eventual result message stated what has/hasn't been imported within an overall batch, if there were a failure. It looks like everything up to the failure point did get imported, plus (oddly) the one after it, but then subsequent ones didn't go in.

@hohno-panopto
Copy link
Contributor

Hi mvl22,
Thank you for the report. Could you contact our support team so that they may investigate your situation further?

@mvl22
Copy link

mvl22 commented Oct 6, 2021

We have now found the problem - which was a trailing space in the folder name. However, this is basically almost impossible to spot!

I've created a new issue on the issue of the result message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants