Error writing to file on save?

[Anonymous]

Every so often when I try to save I'll get the 'error writing to file' message. This will usually last for 30-60 mins and will then go back to normal and allow me to save. I'm trying to save to an office server but it will allow me to save to the desktop during these episodes. 

I've only ever seen this error before when there isn't enough disk space, but there is over 100GB free. I've tried creating a new file with just a sphere and the same error message pops up!

Any ideas?

[tony_markham]

Hi,

Did you ever manage to solve this issue? We seem to have the same issue when we try to save to our server.

I've looked around and can't seem to find a solution.

[Anonymous]

Hi,

I think it's something to do with the memory limit, I noticed it always happened when the physical memory was 80%+. I'm not sure why that would affect just saving on the server and not desktop, but closing programs excess before saving seems to have fixed it for me. 

Would be interesting to know if that's the case for you too?

[joakim]

The error message goes away if you uncheck "compress on save" in the Preferences. However, this is not such a good solution, since the files get extremey large without compression enabled. I only get the error when I have more than two instances of 3ds Max open at the same time. It is not an memory issue. I have 64 gb ram in my pc and get the error even if only a fraction of the memory is used.

[Anonymous]

I've found the same, it only happens with two versions of max, but unticking compress on save doesn't work for me. I also tried unticking backup on save - same error.

Sounds like it must be something to do with multiple versions of max open at the same time. I said memory limit as it will only start working when I get the memory limit below 50%, but of course that's usually a result of closing the less essential max programs... 

[Anonymous]

This error is a plague in our studio, mostly for people working on large exteriors.  None of the fixes work %100.  I just spent ages trouble shooting my scene.  Ended up being a bad curtain proxy for me.  deleted the curtains and it saved fine.  Impoted the mesh for the curtains and it saved fine.  

For this scene it was only to do with the troublsome proxy.

[Anonymous]

That's interesting, I don't have any proxies in the scenes at the moment but they do have purchased models which may not be 100% clean... Did you find that you couldn't save any other files whilst this problem was happening? I am also finding it triggers more on the larger scenes, but if I open a new instance of max, create a box and save I will get the same error despite it being a completely clean scene with what would be a tiny file size. 

Right now I'm unable to save, I only have one instance of max open (so it's not the number of max files open!) CPU is at 16% and memory at 56%.

Most of the time I can force it to save by closing down windows explorer or windows photo viewer, weirdly. 

I've emailed Autodesk about this, they said it was to do with memory leak and said upgrading to the latest service pack would fix it - we did and it didn't fix the problem. 

[Anonymous]

It seems to be caused by many different scenarios. I can always save
locally. I think the resolution lies in that fact. I hope auto desk can
sort this out asap because sometimes it crashes and we lose work/time/money
for the company.

[Anonymous]

I am getting this error as well, I am using a lot of memory when it occurs but I do not know if that is related or not. It may be a specific corrupted asset. A fix for this would be great, or at least more information about what is going on. This is the error log I get:

2016/05/02 14:28:42 INF: [16592] [09744] creating file \Documents\3dsMax\autoback\AutoBackup02.max.sv$
2016/05/02 14:30:14 INF: [16592] [09744] deleting \Documents\3dsMax\autoback\AutoBackup02.max.sv$
2016/05/02 14:30:22 ERR: [16592] [09744] Error writing to file

[Anonymous]

I submitted a report to autodesk and am now speaking to someone about this, so far he hasn't found a solution but the fact that they're looking into it must mean we'll have an answer soon!

The advice we've had so far is to log all crash reports. Autodesk can access these so if you find your 3ds Max is crashing after this error I'd say log the reports and then open a case with autodesk and get them to check into the reports. Unfortunately (?) ours isn't crashing, so we don't have anything else for Autodesk to go on other than random ideas of the problem! 

Does anyone else get a weird error around the same time where max starts to lag and flicker? We can't use any drop down boxes without it seeming to refresh itself and close them, and the key frame button will flick between white and grey. This can be fixed by closing down all instances of windows explorer, if there are none open the only fix is to close down max and reopen. (Bearing in mind we can't save at this point!!)

It might not be related and I might have just discovered a new irritating error, but it would be interesting to know if it was linked?

[Anonymous]

So, we also have this issue now. First time we have seen it. We are using max17. Any news from your side?

[Diffus3d]

From what I've seen the crash on save is a result of the Chaosgroup license server.  Download a new version of Vray and install it plus the updated license server and you should be good to go.  

Make sure to submit your CER reports when you crash, a support person can see what was causing it.  

Best Regards,

AJ

[Anonymous]

It dosent crash for us, just an pop up saying file cannot be saved.

[Diffus3d]

It may be a new issue, maybe related to a Windows or .net update.  Are you all on W10? 

Compress on Save does have a logged issue right now, so I don't recommend using it for now.  (Related to the zip exe being 32-bit.)  The Vray license server also can cause this problem, and so can certain file sharing services. 

Are any of you saving into a shared folder for OneDrive, DropBox, etc?  Those online backup services can 'grab' a file as it's being created and cause save problems as well.  I think this article has some more info.

Best Regards,

AJ

[Anonymous]

Hi,

We've not actually had the error for a several months. However, in that time we've replaced our server, updated Vray, upgraded to 2018 Max, many PCs have had upgraded RAM etc so I can't say for sure what was the fix or even if it has been fixed and isn't just dormant. 

Would be good to find the actual cause to prevent this happening again in future!

[Anonymous]

Hey,

Windows 7 still 😉 , will look in to the compkress on save, is that issue also on max2017?

[Diffus3d]

It's possible, do you see any improvement with it off?

Best Regards,

AJ

[jon.bell · Accepted solution]

Hi folks,

Just wanted to revive this thread to note that we have a troubleshooting article on these issues.

"Scene File Save Warning: Unable to create temporary scene file" when saving a file or an autobackup...

Could anyone who's still seeing this behavior in their copy of 3ds Max read the above article and let me know if they have any other questions? Thanks!

[vtkong.com]

Run Script and try save 3dMax

while (numNoteTRacks TrackViewNodes.Max_MotionClip_Manager > 0) do deleteNoteTrack TrackViewNodes.Max_MotionClip_Manager (getNoteTrack TrackViewNodes.Max_MotionClip_Manager 1)

[zeeshus28]

I got the solution . Where ur file located check there's space ...and free up some space problem will be solve...