I installed the new Drive 200.0.0 on a Windows 10 v 21H2, GeForce RTX 2060 driver v 528.49, NTFS HD: I was able to mount a folder without any problems.
Same thing on a remote Windows 10 v 21H2, GeForce RTX 4070 Ti driver v 528.49, NTFS HD: when I launch, I see the “spinning wheel+Launching…”, but after a few seconds it goes away and nothing happens.
Please validate that you are not placing the folder into another cloud service drive (i.e. making an Omniverse Nucleus server folder within a OneDrive folder).
Also, please upload your log files if you could. They are located in the .nvidia-omniverse/logs/Drive 2/ directory within your user folder
I don’t even get to the point of placing the folder. The Drive launcher stops and nothing happens. Here is the content of the log:
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [I] Press ctrl-C to stop gracefully
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [I] -------------------------------
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [D] ui: started UI server on port 59510
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [E] error loading config: Couldn’t find config at C:\Users\zambetti.nvidia-omniverse\config\odrive-config.json
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [I] setting odrive2 conflict sync status to ‘no conflict’
[Wed Mar 1 14:46:28 2023 -06:00] [tid 29240] [I] setting odrive2 sync status to ‘Omniverse Drive’
[Wed Mar 1 14:46:32 2023 -06:00] [tid 26132] [I] Press ctrl-C to stop gracefully
[Wed Mar 1 14:46:32 2023 -06:00] [tid 26132] [I] -------------------------------
[Wed Mar 1 14:46:32 2023 -06:00] [tid 26132] [I] Seems like the application is already running, exiting.
That was my mistake also. However, after changing the Server URL to point to a folder which was not in OneDrive, Drive is not creating the folder and showing it within File Manager as expected.
I don’t know if this was noticed in my original post, but, so far as I can tell, Drive 200.0.0 works fine on my local laptop, but fails on a remote workstation.
I
@zambetti1 are you using Launcher 1.8.3 on your remote machine?
Can you also please upload your logs from the remote machine that isn’t working please? The directory is listed in the above reply.
The logs I sent are from the remote workstation.
This is the blog from the other remote machine that did not work:
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [I] Press ctrl-C to stop gracefully
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [I] -------------------------------
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [D] ui: started UI server on port 59066
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [E] error loading config: Couldn’t find config at C:\Users\zambetti.nvidia-omniverse\config\odrive-config.json
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [I] setting odrive2 conflict sync status to ‘no conflict’
[Mon Mar 6 08:47:15 2023 -06:00] [tid 16068] [I] setting odrive2 sync status to ‘Omniverse Drive’
[Mon Mar 6 08:48:12 2023 -06:00] [tid 18588] [I] Press ctrl-C to stop gracefully
[Mon Mar 6 08:48:12 2023 -06:00] [tid 18588] [I] -------------------------------
[Mon Mar 6 08:48:12 2023 -06:00] [tid 18588] [I] Seems like the application is already running, exiting.
[Mon Mar 6 08:52:10 2023 -06:00] [tid 24592] [I] exiting from the listening thread
[Mon Mar 6 08:52:10 2023 -06:00] [tid 20968] [I] Starting COM shutdown
[Mon Mar 6 08:52:10 2023 -06:00] [tid 20968] [I] Shell services task done
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [I] Press ctrl-C to stop gracefully
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [I] -------------------------------
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [D] ui: started UI server on port 59560
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [E] error loading config: Couldn’t find config at C:\Users\zambetti.nvidia-omniverse\config\odrive-config.json
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [I] setting odrive2 conflict sync status to ‘no conflict’
[Mon Mar 6 08:54:06 2023 -06:00] [tid 17260] [I] setting odrive2 sync status to ‘Omniverse Drive’
[Mon Mar 6 08:54:13 2023 -06:00] [tid 18328] [I] Press ctrl-C to stop gracefully
[Mon Mar 6 08:54:13 2023 -06:00] [tid 18328] [I] -------------------------------
[Mon Mar 6 08:54:13 2023 -06:00] [tid 18328] [I] Seems like the application is already running, exiting.
[Mon Mar 6 08:54:56 2023 -06:00] [tid 10204] [I] exiting from the listening thread
[Mon Mar 6 08:54:56 2023 -06:00] [tid 27772] [I] Starting COM shutdown
[Mon Mar 6 08:54:56 2023 -06:00] [tid 27772] [I] Shell services task done
FYI:
I copied the odrive-config.json from may laptop, where it works, to one of the remote workstations, where it did not work, and then re-installed Drive 200.0.0 which then worked.
What seems to be missing in both remote workstation, is the UI that let one set up the configuration, which is then written out as a JSON file in the Config folder.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.