ERROR storing texture file on server

[regionfive]

Hey there,

I finally wanted to switch from blender v.2.68 + Octane Server v.2.8 up to the latest Octane 2.0.
So I installed Blender_Octane 2.06 with Server v.6.5.
Everything works fine up to the point I want to load up any image texture to any slot.
In the attached example, the cube has only one material. In the diffuse slot an image texture is applied.
Suddenly the console says that it cannot load the image file to the server.

What am I doing wrong? The Node system has changed a lot since 1.20

Thanks for help.

René

[JimStar]

Look at the user-directory of the user under which you are running the OctaneServer. Is there "livedb\client\textures" directory present?

[regionfive]

Hi,

yes, it is there. And all other directories too.

The Material LiveDB is not available. Neither in the Plugin, nor in the Standalone.
But at least in the Standalone I am able to add a texture to a diffuse node.

The Firewall is deactivated and there are also writing permissions within this folder structure.


octane server 2.8 is still running without any problems. could there be a conflict if both versions are installed?

cheers
René

[JimStar]

The Material LiveDB is not available. Neither in the Plugin, nor in the Standalone.

It's very strange. It looks like some network access problems may still be present... Perhaps some antivirus blocks these executables from network access?..
About folder permissions - to check if it may be the case, you may start OctaneServer "as Administrator" and check if the texture file problem still exists. This is really weird issue, as nobody reported anything similar for all the time Blender plugin exists...

octane server 2.8 is still running without any problems. could there be a conflict if both versions are installed?

Installer places the newly installed executable files in place of old ones.
Are you sure that you have the Standalone 2.0 and the 2.0 standalone and plugin licenses activated on your computer?

[regionfive]

Hi Jimstar,

I kind of "solved" the problem now. It was windows-wise.. obviously not an octane / blender problem.

After I made a new windows admin user account and logged in the standalone and the plugin licenses, everything worked fine.
There must have been some wrong settings regarding network or whatever...

You can close the thread.
Thanks anyway.
Cheers