.
 
.

ÜberwareTM

View Forum Thread

Anyone can view the forums, but you need to log in in order to post messages.

> Forum Home > Support > Looking for any solutions to: Error Line 1: File Not Found

  Mon, 29/Jan/2018 1:16 PM
Alexander
1 Post
I have a render farm with 20 nodes, only one seems to be working with Maya 2018, and I'm completely stumped. In my render log:

Waiting for downloaded file...
"C:\Program Files\Autodesk\Maya2018\bin\Render.exe" -r file -proj "A:/Animation/Projects/Client/Johnsons/0009_Johnsons Petite Planet/Project Directory/02_Production/04_Maya" -rd "A:\Animation\Projects\Client\Johnsons\0009_Johnsons Petite Planet\Project Directory\02_Production\04_Maya\images\Anthem_sh011" -s 1 -e 1 "A:/Animation/Projects/Client/Johnsons/0009_Johnsons Petite Planet/Project Directory/02_Production/04_Maya/scenes/05_Lighting/Anthem_Shot_011/Lighting_Scene_Anthem_sh011_v005_kl.ma"
=================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================

--- switching to standard error stream ---

Starting "C:\Program Files\Autodesk\Maya2018\bin\mayabatch.exe"
--- switching to standard output stream ---
[2018/Jan/29|12:10:57] V-Ray: V-Ray for Maya version 3.60.03 from Dec 2 2017, 17:58:58

[2018/Jan/29|12:10:57] V-Ray: V-Ray core version is 3.60.04

[2018/Jan/29|12:10:59] V-Ray: Loading plugins from "C:\Program Files\Autodesk\Maya2018\vray/vrayplugins/vray_*.dll"

[2018/Jan/29|12:10:59] V-Ray: 77 plugin(s) loaded successfully

[2018/Jan/29|12:10:59] V-Ray: Finished loading plugins.

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node vrayMultiProjection (id: 1115335/0x001104C7)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRayCurvature (id: 1115347/0x001104D3)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRayTriplanar (id: 1115362/0x001104E2)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRaySkinMtl (id: 1115348/0x001104D4)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRayPointParticleMtl (id: 1115353/0x001104D9)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRayStochasticFlakesMtl (id: 1115359/0x001104DF)

[2018/Jan/29|12:11:00] V-Ray: Registered dynamic node VRayAlSurface (id: 1115350/0x001104D6)

info: Loaded "C:\Program Files\Autodesk\Maya2018\bin\mayabatch.exe"

info: MDL SDK 2017, build 287000.5634, 12 Apr 2017, nt-x86-64-vc11

info: Loaded library "C:\Program Files\Autodesk\Maya2018\bin\libvrayfreeimage.dll".

Initialized VP2.0 renderer {

Version : 2016.11.38.12. Feature Level 5.

Adapter : Quadro P600/PCIe/SSE2

Vendor ID: 4318. Device ID : 0

Driver : nvoglv64.dll:23.21.13.9065.

API : OpenGL V.4.6.

Max texture size : 16384 * 16384.

Max tex coords : 32

Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).

Shader compiler profile : (Best card profile)

Active stereo support available : 0

GPU Memory Limit : 2048 MB.

CPU Memory Limit: 62157.6 MB.

}

OpenCL evaluator is attempting to initialize OpenCL.

Detected 2 OpenCL Platforms:

0: Intel(R) Corporation. Intel(R) OpenCL. OpenCL 1.2 .

Supported extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_fp64

1: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 9.1.84.

Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_khr_gl_event cl_nv_create_buffer
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.

OpenCL evaluator is unable to find a GPU device that can share VBOs with OpenGL.

pymel.core : INFO : Updating pymel with pre-loaded plugins: mayaHIK, invertShape, GamePipeline, CloudImportExport, curveWarp, tiffFloatReader, MASH, poseInterpolator, bifrostvisplugin, hairPhysicalShader, ATFPlugin, ikSpringSolver, ik2Bsolver, xgenToolkit, AbcExport, retargeterNodes, vrayformaya, gameFbxExporter, VectorRender, OpenEXRLoader, lookdevKit, Unfold3D, Type, mayaCharacterization, renderSetup, fbxmaya

Maya 2018 importing module pymel 1.0.10 (C:\Program Files\Autodesk\Maya2018\Python\lib\site-packages\pymel\__init__.pyc)

Error: line 1: File not found: "A:/Animation/Projects/Client/Johnsons/0009_Johnsons Petite Planet/Project Directory/02_Production/04_Maya/scenes/05_Lighting/Anthem_Shot_011/Lighting_Scene_Anthem_sh011_v005_kl.ma"

   
  Mon, 12/Feb/2018 2:45 PM
Robin
1136 Posts
Hi there

It looks like your scene file on the A: drive is not being found. Most likely the issue is that the A: drive is not mapped correctly on the render nodes. This may be an issue if you are using Smedge as a service, because even if you log in to the render node console and see the drive mapped, the service will still not have it mapped.

If it is, indeed, the drive mapping, you have a few options. You can try using UNC paths, and avoid drive letters altogether. Maya doesn't have any issue with UNC paths, nor does Smedge, and you can avoid all drive mapping. Another option is to use the Smedge drive mapping wizard (available in the Engine menu in Administrator Mode). Or you can mount your drives yourself in some way as part of the start of the SmedgeEngine process or the render work process (like with a simple wrapper batch script to map the drive if needed).

If you are not using Smedge as a service, and know that the drive is mapped correctly, and can verify that there is not something simple like a typo or content that was moved on disk, contact directly and we can arrange a time to remote connect and take a look.

Thank you,
-robin
   
Page 1 of 1

.
.
.
.
©2000 - 2013 Überware. All rights reserved