
Open the scene and make sure the errant object is assigned texture coordinates. Add an Alternate Map Path on the Network Job Assignment dialog that points to the folder containing the missing map.ĮRR: Object (UVW 1): Sphere01 requires texture coordinates and may not render correctly.


Autodesk backburner error receiving information full#
Make sure that you have used either the full UNC path name for the bitmaps or that the maps directory has been mounted to the same drive letter on each machine.If all maps are being shared from a single directory, make sure the directory is correctly shared with full permissions.To fix the problem, do one of the following: The Server could not find 3ds.cel in the local path specified, which means that the path to this map is not been correct for network rendering. You can learn more about log files in “Configuring Backburner Log Files” in the Autodesk Backburner User Guide at Here are some of the error messages related to 3ds Max, along with a likely cause, that you will see in the Errors tab of the Queue Monitor when a failed server is selected:ĮRR: D:\MAPS\3DS.CEL Many of these reasons are covered in “Troubleshooting” in the Autodesk Backburner User Guide at One reason that is specific to 3ds Max which can cause a server to fail is the presence of a scene which does not contain texture coordinates.Īll errors are recorded in the appropriate log file. Servers can fail for a variety of reasons during a network render job. If the queue is clear of rendering jobs and the server is still flagged as busy, stop running server on each of the problem machines, and restart the service after a few seconds. If the server should not be busy, verify that the queue is clear of jobs by opening the Queue Monitor and connecting to the Manager. The yellow icon means that the server is busy rendering another job. Then click Refresh in the Network Job Assignment dialog to display the most recent information about the server. This "purges" the server and may solve the problem. If you've checked for and corrected these conditions and the servers are still unavailable, stop running Server on each of the problem machines, and restart the service after a few seconds. The server has experienced abnormal termination.(See “Setting the Availability for Rendering Nodes” in the Autodesk Backburner User Guide at The server has been disallowed for the current time period in the Properties dialog of the Monitor.(See “Setting Up Backburner Server” in the Autodesk Backburner Installation Guide at The server has not been correctly started.This state can occur for several reasons, including: The gray icon means that the server is currently not available to render a job.


S138| >set "PATH=C:\RR_localdata\renderer_exe\maya\win_圆4\Redshift_1.4.2.0\Plugins\Maya\2017\nt-x86-64 C:\RR_localdata\renderer_exe\maya\win_圆4\Redshift_1.4.2.0\Plugins\Maya\2017\nt-x86-64\extensions C:\RR_localdata\renderer_exe\maya\win_圆4\Redshift_1.4.2.0\bin C:\RR_localdata\renderer_exe\maya\win_圆4\mtoadeploy_2017_1.4.2.0\procedurals C:\RR_localdata\renderer_exe\maya\win_圆4\mtoadeploy_2017_1.4.2.0\bin \\SERVEUR_M\core\00_RoyalRender\render_apps\renderer_plugins\maya\win_圆4\2017\plug-ins \\SERVEUR_M\core\_ARNOLD\MTOA\2017\bin C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\WINDOWS\System32\WindowsPowerShell\v1.0\ C:\Program Files\Common Files\Autodesk Shared\ C:\Program Files (x86)\Autodesk\Backburner\ C:\Program Files (x86)\QuickTime\QTSystem\ C:\Users\Administrateur.Regardless of their state in the Network Job Assignment dialog, servers can always be assigned new jobs.
