DR problem - Failed to delete server scene file

[RSF]

Hello!
I'm having lots of problem (having all set correctly and nevertheless nodes don't get files) with DR and I think this is the problem.
Here's the last message I get in the vraylog

[2009/Mar/22|19:39:28] warning: Failed to delete server scene file "C:\Documents and Settings\Default User\Local Settings\Application Data\Autodesk\3dsmax\2009 - 64bit\enu\temp\vray_server_scene.max" (32)

Manually deleting the file is possible only if I stop the vrayspawner service.
What's happening? How is this supposed to work?

Thanks

[vlado]

You can try to use the "Restart slaves on render end" option for DR and see if it helps.

Best regards,
Vlado

[RSF]

Hi.
Tried "Restart slaves on render end" and it still can't delete the file although it is unlocked and the next render will correctly show any updates to the scene.
This is almost a workarround but theres another problem: Xref objects don't show in the slave buckets and the paths are all correct.
Remember the scene was rendering correctly until a while ago.
I'm hoping there's a common cause for both.

[RSF]

Hello Vlado.

I started a blank scene and could merged all the objects again and got it working.

For my despair I think this problem doesn't have a solution.
It's an old problem where some object (or material) gets corrupted and messes the whole scene (unfortunately and although I sometimes manage to isolate the entity causing the problem I never figured out what was wrong with it).

This time I couldn't isolated the problematic entity thought.

Once I had to rebuild a material that was causing lots of problems and couldn't find a single difference between the 2.

Do you have any advice?
What can be causing this objects to mess the entire scene?
What should I look for?

Thanks and sorry for the inconvenience

PS: By the way...I had a problem with objects coming from rhino and I found that having a "floating point" number in a vertex coordinate would mess thinks up. I think you acknowledge this as a bug then. I think it was more evident when using "interpolation" in reflections.
How is this issue? Is this solved or should I worry about it?