max.net unhandled exception on render node

[Neilg]

On one of our render nodes, we've suddenly (as of this weekend) started getting an error message pop up before the rendering starts. We've not changed max versions, not installed any software, save version of vray that was working last week. If you press send and close or just close, the rendering starts normally - but it means every render job has to be kicked in manually.
The message is this:


I read the bit about corrupt memory... what kind of memory? RAM or disk?

[Morbid Angel]

I assume you tried to reboot it etc?

[Neilg]

yep. no change.

[Morbid Angel]

if there was absolutely no installs of any kind, perhaps blowing 3ds max folder in user/documents might resolve and also

C:\Users\<user>\AppData\Local\Autodesk\3dsMax\2016 - 64bit\ENU

be sure to back it up before (max should rebuild them upon reload) but you never know.

[RotemS]

I read the bit about corrupt memory... what kind of memory? RAM or disk?

Don't worry, it's not referring to the physical memory being corrupt, more like 'this is often an indication that other DATA in memory is corrupt.'

Have you contacted Ephere?

[Neilg]

Don't worry, it's not referring to the physical memory being corrupt, more like 'this is often an indication that other DATA in memory is corrupt.'

Have you contacted Ephere?

I didnt notice that name - I just googled them and it seems like max.net is optional? not sure why it's kicking in.

Our IT guy is away, might leave contacting them up to him when he gets back in jan.

[RotemS]

Is this a recent release of 3dsmax? I think max.net was integrated and used as a basis for MCG maybe? My memory fails me.

[Neilg]

2014. maybe railclone or some other plugin uses it?

[RotemS]

Oh I remember now, it was State Sets.