CAD Forum

I have seen this error pop up several times over the years and quite frequently of late. Usually it has been a complete disaster of immensely frustrating proportions.

But recently while I was suffering thru this desperately trying to find a way to save the file I went thru some steps that have helped in the past.
Save to a different location, save as a different filename (tho I would not recommend this for assy document) save to a different drive, etc.
None of this worked.

BUT.... While I was exploring thru a different folder structure I happened upon an old folder I did not require anymore and had meant to delete.
It popped up a warning saying it could not delete folder as the process "COM Surrogate" was holding it in usage..??!?!!!

I was too flustered to consider the consequences and allowed myself to be distracted by this fresh frustration, I went straight to task manager and ended the COM Surrogate process(es). Imagine my surprise when I next tried to save the same file, it. just. worked..
Experience has since proven this was not a fluke.
It has worked every time the fail to save dialog has appeared since.

I do not know if this is the golden bullet for every occasion. But maybe it may help another...

Yes, Solidworks has its fingers all over the place.

A while ago, I was having some lag issues whenever I selected a surface. As I was looking into it, I noticed that every time I selected a surface or a face of a solid, the "ethernet" graph on the performance tab of the Task Manager would spike. Coincided with the lag. At the time, this part was on the server.

So I looked into it, and after some investigation, I moved everything to my hard drive. Including all the pointers in the "File Locations" area of the options.

This made the lag less, but it was still there. So I called my VAR, and they couldn't replicate it on their end, so nothing moved forward. I told my IT department about it, and instead of looking into it, they just decided to nuke it from orbit and re-installed windows.

It was still there after the re-install.

After upgrading to SW 2022, I haven't seen the lag since. But it was a pretty weird thing.