Issue with Revit Live Session Creation

jeromelwk · May 2, 2024, 2:12pm

Hi,

I’m attempting to initiate a live session from Revit (version 23.0.20.21), but I’m encountering a persistent issue. Each time I create a new live session, Revit crashes.

Below are the steps I’ve followed to create a live session:

Open my RVT file (Note: This file is not hosted on Microsoft OneDrive).
Export as Prop.
Initiate a new live session.

At this point, the application consistently crashes.

Could you please assist me in identifying the root cause of this problem? Any guidance or suggestions would be greatly appreciated.

Thank you

Revit crash report :
dmpuserinfo.zip (1.7 MB)

Nucleus logs :

2024-05-02 14:00:27 [2,892ms] [Info] [carb.launcher.plugin] [33276] C:\b\w\29e5db4c08dcb0b0\source\plugins\carb.launcher\ProcessCommon.cpp:_readFromHandleThread():620: done the read thread for ‘launcher stderr reader’ for the process 12696.
2024-05-02 14:00:27 [2,892ms] [Info] [carb.launcher.plugin] [25308] C:\b\w\29e5db4c08dcb0b0\source\plugins\carb.launcher\ProcessCommon.cpp:_readFromHandleThread():620: done the read thread for ‘launcher stdout reader’ for the process 12696.
2024-05-02 14:00:27 [3,148ms] [Info] [omni.core] [444] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\omni.core\impl\servicesclients.cpp:connect():486: Connecting to Auth service…
2024-05-02 14:00:29 [4,225ms] [Info] [omni.server] [24284] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\omni.server\omniverseserver.cpp:OmniverseServer():121: waiting for Core to startup (done)
2024-05-02 14:00:29 [4,239ms] [Info] [omni.server] [24284] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\omni.server\omniverseserver.cpp:OmniverseServer():134: Omniverse C++ ApiServer server started.
2024-05-02 14:00:29 [4,971ms] [Error] [omni.core] [7500] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common\childprocess.cpp:stderrReadCallback():31: From process omni-lft-service\omni-lft-service.exe:2024-05-02 16:00:29,748 - system_log - INFO - [WinError 1225] Le système distant a refusé la connexion réseau

2024-05-02 14:00:29 [4,972ms] [Error] [omni.core] [7500] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common\childprocess.cpp:stderrReadCallback():31: From process omni-lft-service\omni-lft-service.exe:2024-05-02 16:00:29,749 - system_log - ERROR - Traceback (most recent call last):
File “idl\connection\transport\omni.py”, line 166, in prepare
File “websockets\legacy\client.py”, line 650, in await_impl_timeout
File “asyncio\tasks.py”, line 445, in wait_for
File “websockets\legacy\client.py”, line 654, in await_impl
File “asyncio\base_events.py”, line 1081, in create_connection
File “asyncio\base_events.py”, line 1060, in create_connection
File “asyncio\base_events.py”, line 969, in _connect_sock
File “asyncio\proactor_events.py”, line 709, in sock_connect
File “asyncio\windows_events.py”, line 826, in _poll
File “asyncio\windows_events.py”, line 613, in finish_connect
ConnectionRefusedError: [WinError 1225] Le système distant a refusé la connexion réseau

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File “lft\server.py”, line 556, in await_connection
File “idl\connection\transport\omni.py”, line 174, in prepare
idl.connection.transport.TransportError: [WinError 1225] Le système distant a refusé la connexion réseau

2024-05-02 14:00:30 [5,973ms] [Error] [omni.core] [7500] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common\childprocess.cpp:stderrReadCallback():31: From process omni-lft-service\omni-lft-service.exe:2024-05-02 16:00:30,750 - system_log - INFO - reconnecting …

2024-05-02 14:00:30 [5,977ms] [Error] [omni.core] [7500] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common\childprocess.cpp:stderrReadCallback():31: From process omni-lft-service\omni-lft-service.exe:2024-05-02 16:00:30,753 - system_log - INFO - connected

2024-05-02 14:00:30 [5,981ms] [Error] [omni.core] [7500] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common\childprocess.cpp:stderrReadCallback():31: From process omni-lft-service\omni-lft-service.exe:2024-05-02 16:00:30,758 - system_log - ERROR - Server started

2024-05-02 14:00:47 [22,251ms] [Fatal] [omni.core] [15336] c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\omni.core\impl\deltamanager.cpp:pingTask():615: Failed to connect to DeltaApplier process.

Simplychenable · May 3, 2024, 11:14am

@jeromelwk i am just another OV user, and would it be safe for me to assume you are trying to do a livesync with Composer? if so, what’s the version of the app? in addition, if you could upload the most recent .log file from the respective app, it could help the devs/mods help troubleshoot.

also, could you repro the same crashing behavior on a simpler scene?

cbothma1 · May 3, 2024, 11:38am

Hi Jerome, I tried to reproduce, but live was running fine for me. I am running Revit 2024 (should not make huge difference), with Composer 2023.2.5, and Revit connector 202.1.2503. Might be worth testing on smaller scene, or screen grab scene if that is possible.

jeromelwk · May 3, 2024, 12:42pm

Hi @Simplychenable

I’m currently using Omniverse Composer 2023.2.5, and I’ve attempted to integrate it with both Revit v23.0.20.21 and v24.2.10.64. My Revit plugin version is 202.1.2503.

By default, the Omniverse Server is set to localhost:34080/omniverse. However, I consistently encounter the error message: “Either ‘localhost:34080/omniverse’ is not a valid server, or you do not have access to this server.”

Additionally, when I export as Prop and attempt to initiate a live session, Revit crashes.

The Test Revit project is very simple :

Any insights or solutions to these issues would be greatly appreciated. Thank you!

Simplychenable · May 4, 2024, 8:47pm

i wonder if you’ve set up the OV nucleus service and server prior to this? do you mind taking a screenshot of the Nucleus section of the OV launcher and upload it for further assessment?

jeromelwk · May 6, 2024, 7:37am

@Simplychenable

Richard3D · May 6, 2024, 6:58pm

Can you look at the REVIT crash logs and give us the error message ?

jeromelwk · May 14, 2024, 1:03pm

@Richard3D

RVTCrashReport.zip (1.7 MB)

Richard3D · May 14, 2024, 4:08pm

Thanks, I will take a look. Something I just read here, does not look right at all…
“By default, the Omniverse Server is set to localhost:34080/omniverse. However, I consistently encounter the error message: “Either ‘localhost:34080/omniverse’ is not a valid server, or you do not have access to this server.””

That looks odd. Are you sure you set it up correctly ? Did you manually try to change this address ? It should just be “localhost”. If you “can” and you will not lose work, can you delete and reinstall your localhost and leave it everything as default. Use a VERY simple username and password, like “admin / admin”

jeromelwk · May 14, 2024, 4:40pm

I tried to setup again Nucleus server with default parameters.
-The folder location is now C:/Omniverse
-Admin for username and password
-No changes to default settings
I still have this message

Revit is still crashing when I attempt to start live session

Richard3D · May 14, 2024, 5:34pm

So this is not a Revit issue then. This is a Nucleus issus for sure.
Why is your Nucleus not running ? That is the question. Check your anti virus, your firewall,
How did you change folders ? In Launcher ? I don’t think it is that simple. Did you wipe OV completely and start over or just Nucleus ?

Go to http://localhost:3080/ and show me everything there. Better still restart your computer and go through fresh and record a video of you

starting Launcher
starting Composer
Accessing your localhost server

Forget Revit for a second, that is the not the issue.

Richard3D · May 14, 2024, 5:37pm

Show me your Localhost Nucleus in Launcher. Can you get in and access your demo projects ?

jeromelwk · May 15, 2024, 8:19am

Richard3D · May 16, 2024, 3:21pm

Ok so you HAVE to figure this out. If you cannot get your localhost to work, LIVE workflow will not work.
Go to http://localhost:3080/ and show me everything there

Richard3D · May 16, 2024, 3:22pm

Show me this

jeromelwk · May 16, 2024, 3:38pm

Screenshot + Log file

Nucleus (4).log (8.1 MB)

Richard3D · May 16, 2024, 3:54pm

DATA_DIR: C:\Users\J.LOYWICK\OneDrive - BYCN\Documents\Omniverse Nucleus\server
Ok first problem. You are using ONE DRIVE. This breaks Omniverse horribly. Please disable
Second, you have tried to install your NUCLEUS localhost “inside” one-drive ? That will certainly not work

Third, what is this ? Your system is trying to connect to this all the time. Did you install some custom code from GITHUB?
c:\gitlab-runner\builds\sr9_1st2\0\omniverse\backend\api_server\source\plugins\common

I think you need to do a COMPLETE OV WIPE off your system and reinstall everything outside of one drive. Do you have a D Drive ? Like “D:/omniverse”, If not use “C:/omniverse”.

Richard3D · May 16, 2024, 4:02pm

Please try to find this file and send it
“C:\Users\USER.nvidia-omniverse\config\Nucleus\Omniverse.toml”

This is my Nucleus install path = “D:\Omniverse\Library\nucleus-workstation-2023.2.3-rc.10\Nucleus”

jeromelwk · May 16, 2024, 4:06pm

Thanks for replying Richard
Bellow my toml file (inside zip folder)
Omniverse.zip (381 Bytes)

Richard3D · May 16, 2024, 4:08pm

and what is this ?