Cannot find procedure "shaderBallRendererMenuUpdate".

When commandline rendering using Maya, we always get this error:


Cannot find procedure "shaderBallRendererMenuUpdate".

The error itself doesn’t seem to affect the render and the render completes just fine. However, this becomes an issue since all errors during rendering are being submitted into a Slack channel. This error completely spams the channel as it *always* is being hit on every single render.

What could be causing this to happen?
The error appears in this context which causes me to think it could be related to V-Ray:


[2017/Feb/16|14:04:25] V-Ray: V-Ray for Maya version 3.40.06, revision 27073 from Nov 22 2016, 21:23:16
[2017/Feb/16|14:04:25] V-Ray: V-Ray core version is 3.25.01
Initializing V-Ray for Maya

[2017/Feb/16|14:04:25] V-Ray: Loading plugins from "//192.168.0.226/pipeline/bin/vray/builds/161122_vray_v3.40.06-b27073-stable-maya2017_win64/maya_vray/vrayplugins/vray_*.dll"
[2017/Feb/16|14:04:29] V-Ray: 75 plugin(s) loaded successfully
[2017/Feb/16|14:04:29] V-Ray: Finished loading plugins.
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node vrayMultiProjection (id: 1115335/0x001104C7)
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node VRayCurvature (id: 1115347/0x001104D3)
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node VRayTriplanar (id: 1115362/0x001104E2)
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node VRaySkinMtl (id: 1115348/0x001104D4)
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node VRayPointParticleMtl (id: 1115353/0x001104D9)
[2017/Feb/16|14:04:31] V-Ray: Registered dynamic node VRayStochasticFlakesMtl (id: 1115359/0x001104DF)
Error: line 1: line 1: Cannot find procedure "shaderBallRendererMenuUpdate".
File read in  8.3 seconds.
Result: //192.168.0.226/prod/proj2/maya/scenes/scene68.mb

Have you seen this before and/or have any idea why it might be happening?

I have come across this before and I think it’s Maya itself. shaderBallRendererMenuUpdate is related to the new material viewer in the hypershade. Not sure what the problem is exactly, though.

Thanks Yolov. You’re right, it wasn’t V-Ray.