Daemon Install Error | Cound not find the startup directory Tweet

[LichtUndSchatten]

Hello

Iam trying to setup render daemon for Network Rendering and get the following error:
"ERROR: Could not find the startup directory"

What could i try to get it work?

Thanks for your support

[bepeg4d]

Hi,
where did you install the Render-Node app?
Normally it should be installed in C:\Program Files\OTOY\ directory.

ciao Beppe

[LichtUndSchatten]

Hello Beppe.

Thx for your answer. I´ve used the default path for installing the renderslave app.

[bepeg4d]

Please try to disable any kind of internet or antivirus software, sometimes they are interfering with daemon installer.
ciao Beppe

[LichtUndSchatten]

Hey Beppe,
I tried out 3 different machines, all WIN10. On each of them, I can not run the batch "_install_daemon.bat" at folder "OctaneRenderEnterprise Slave 2020.1.5" or "_install_daemon.bat" at folder "OctaneRender Enterprise Network Render Node 2020.2". I just get the same error "ERROR: Could not find the startup directory" everythime and cannot install the daemon.
On one other WIN10-machine, I can run both of the batchfiles and istall the daemon.
Firewall and Antivirus is disabled on all machines while I try to install.

If you have any suggestions what else should be checked, please let me know.

Best regards!

[Tugpsx]

While setting up a Carrara render node, it was relatively easy to get the Daemon working. During the install process be sure to "run as Admin" that will provide the correct application access. then also ensure that the network options are applied. You can also go to your firewall setting and adjust the applications that have LAN/WAN access.
Based on the language difference shown you may have to edit the batch file to properly locate and launch the application.
You can test by launching the executable from a command prompt to determine if its able to launch at all.

[LichtUndSchatten]

While setting up a Carrara render node, it was relatively easy to get the Daemon working. During the install process be sure to "run as Admin" that will provide the correct application access. then also ensure that the network options are applied. You can also go to your firewall setting and adjust the applications that have LAN/WAN access.
Based on the language difference shown you may have to edit the batch file to properly locate and launch the application.
You can test by launching the executable from a command prompt to determine if its able to launch at all.

Hey Tugpsx, I can confirm that it was pretty easy to get the Daemon working on on machine. But not on three others. The OS and language settings are equal on all machines. I did not edit the batch script and it installed smooth on one machine but fails to install on three others. Firewallsettings should only be relevant when it comes to communication between the the server and the nodes, but not while running the bash-script install_daemon.bat, right? Running the script as Admin did not change anything.

you may have to edit the batch file to properly locate and launch the application.

Could you show me what kind of changes you would suggest? I am willing to try out whatever might help.

Best regards!

[Tugpsx]

I take it you are not installing from a central location.
In the script there is a hard path for "\Microsoft\Windows\Start Menu\Programs\Startup\run_octane_slave_daemon.bat"

Your location is different c:\programme\OTOY\ent...

Code: Select all

set BATCH_FILE=%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\run_octane_slave_daemon.bat
if not exist "!BATCH_FILE!" (
    set BATCH_FILE=!USERPROFILE!\Start Menu\Programs\Startup\run_octane_slave_daemon.bat
    if not exist "!BATCH_FILE!" (
        echo Daemon startup script does not exist. Please install the daemon first.

when the configuration file is created it will only respond to like version.
In your octane network setting specify the entire subnet to see other render nodes on your network. be sure to select the nodes and bind them or bind all.