Crash to desktop because of "Transfer missing assets"

[kosso_olli]

Just to make sure, I tested sending this job to any of our slaves. Each and every one of them crashes with the same error message.

Also, a quick search here on the forum reveals I am not the only one:

https://forums.chaos.com/forum/v-ray...am-error-in-dr
https://forums.chaos.com/forum/v-ray...lestream-error

Just noticed that I replied with the exact same message I am getting now on January 2020... The file in question is again the exact same file that gets written at render end.

https://forums.chaos.com/forum/v-ray...58#post1057258

[^Lele^]

I wonder why the vrimage was written in the previous test, but not now that it's the only output.
Does it work if you turn transferring of missing assets off?

EDIT: there is no trace of any jira entry that has backburner and file output, much less so from the past two years (stuff fixed in 2014 isn't relevant anymore.).
We have not been able to repro it locally either, so we may need your scene and more data besides to see where things may be failing.

[kosso_olli]

Does it work if you turn transferring of missing assets off?

The file renders totally fine with transfer missing assets of, yes.
The vrimg gets written this time around, too. But it doesn't stop V-Ray from crashing.

[^Lele^]

I found a jira entry about BB failing for asset transfer errors (although that was for GPU), with a possible fix: turn on the max task error limits (in the BB Manager) and set it to some number higher than 1 (the default of 4 should do it.).
See if it avoids the crashing.

[kosso_olli]

I found a jira entry about BB failing for asset transfer errors (although that was for GPU), with a possible fix: turn on the max task error limits (in the BB Manager) and set it to some number higher than 1 (the default of 4 should do it.).
See if it avoids the crashing.

I tried it with the settings below and restarted the manager. Sadly, this did not work either. Will try restarting the whole farm tomorrow, but it is busy making noises.

[kosso_olli]

So, after changing settings for the BB manager and restarting the whole farm, it does not work either. Same message as before:

[2022/Feb/23|10:26:46] error: Cannot send asset \\XXX\RENDER\PREVIEWS_TESTS\override_TEST\Test02.v rimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]
[2022/Feb/23|10:26:46] Server 172.16.2.54:20204: Asset "\\XXX\RENDER\PREVIEWS_TESTS\override_TEST\Tes t02. vrimg" was not received.
[2022/Feb/23|10:26:46] error: Cannot send asset \\XXX\RENDER\PREVIEWS_TESTS\override_TEST\Test02.v rimg Error opening file: [PFileStream::Open] 2: (2) [RenderClient::getStream]

The only help I can offer now is a teamviewer session.

Edit: Just a small thing I noticed while testing: The output path of course appears in the asset tracker with the associated vrimg file. Clicking "remove missing assets" in the tracker, the output path gets lost in the render settings window.

[^Lele^]

I've raised your request with support, they should contact you to arrange the teamviewer session.

[Svetlozar Draganov]

Hello kosso_olli

Would you please send a request for a remote session from the Help Center page here.
Make sure to post link to this thread as a reference and select 3D and rendering help from the Request Type dropdown menu in the contact form.

Thank you very much in advance.

[kosso_olli]

We are still getting this error as soon as we enable "Transfer missing assets".
Also, it now does happen with DR on my workstation as host. The file in question can not be transferred, but V-Ray does not crash. It only does when sending to BB.

[vladimir_krastev]

Hi you have cleared and disabled this path, right?

[kosso_olli]

Yes, 100%.

[Martin.Minev]

Hi,

Backburner detects some of our warnings as fatal errors. Could you please try to disable the user task error limit in the manager here.
Also, make a test and decrease the verbosity level to 1 here, or set the log window to never. Let us know how it goes.

[kosso_olli]

I already did this to no avail, see my posts in this thread from 22 an 23 of February.

[Martin.Minev]

Hi,

In this case, it will be best to connect to your machine and troubleshoot. We sent you a remote request in February, but there was no reply.
Please send a request for a remote session from the Help Center page here. Make sure to post a link to this thread and select 3D and rendering help for the Request Type.
In case you are not able to provide us remote access, please let us know on a ticket so we can troubleshoot using email.

Thanks!

[jromero]

We are having spawner dr issues since upgrading to Vray 6. We would get blank buckets. I've narrowed it down to having the vrayspawner2023.exe installed in the now default "C:\ProgramData\Autodesk\ApplicationPlugins\VRay3ds Max2023\bin\ folder". I un-installed & re-installed it in the second option during the install process, which is the "C:\Users\*\AppData\*** folder". That fixed the problem for 9 of the 10 identical render machines.

The one computer still could not find the network assets. I re-installed it back to the default "ProgramData" folder. It somewhat works, but it can only work if the backburner server is not running at the same time as the vrayspawner2023.exe.

BTW Our last version 3dsmax2021 running vray next (installed in their default "C:\Program Files\Autodesk\3ds Max 2021\vrayspawner2021.exe" still works flawlessly. I know you can't have vrayspawner2021.exe and vrayspawner2023.exe running at the same time.

SO is it possible that we are having Windows restricted permission issues when vrayspawner2023.exe now has moved to the ProgramData folder or C:\Users\ folder? (Ive tried making sure the user has full control of these folder and still nothing has worked, and I gone through a complete fresh Windows 10,3dsmax2023,Vray6 install and still the same issue)