I had this problem as soon as I started using SWX 07 exclusively. I have a fairly large assembly with many sub-assemblies. I had one particular sub-assembly, that when suppressed within the main assembly, caused the "fail to save" error. When not suppressed, the assembly would save just fine. I had to spend a lot of time finding the particular subassembly that was causing the problem. Through more time and frustration, I found a part within that sub-assembly that was causing the error. When this part was suppressed, you could then suppress the sub-assembly within the main assembly and all is good. What a pain. Basically, I had to suppress a part within a sub-assembly and then everything worked great. I hope this helps.
Brandon
I've tryed everything our VAR has suggested including upgrading to 3.1 Friday. Withing 3-hours we had another "Failed to Save". The VAR claims it is somthing we are doing wrong and wants to charge us cosulting fees to come out to see what is happening. It only happens with SolidWorks and it happens both on the network and local drives. We have Intel Core Duo Extreem with 4Meg L2 cache 4GB RAM w\ 3\Gig switch nVidia FX3500 512Meg with the current SW sanctioned drivers.
Contrary to what our VAR says it is a SolidWorks problem as this and may other post show.
It seems to happen in bunches. Our users will get three or four "Failed to Save..." in a row (with a slight file name change in between), then suddenly it will save!?! Meanwhile we have bunches of Zero Byte files scattered on the server share with two handles locking them so you can't delete it... not even the Admin with God Privilages from the server can delete them until both handles are killed.
These zero byte files evaporate in a couple of hours or a day when ever windows gets tired of holding on to those two handles.
In the previous post on this subject thread559-163921 meintsi suggested that his IT guy did somthing on the network and it all went away... but meintsi never said what they did....
ok so here i am 2.5 months later and im working on a file that is suddenly giving me the evil eye once again.
I've tried everything suggested in this thread and still.. no dice. weird. This is by no means a 'large' assembly. Probably 40 parts max. One thing it does have is many configurations (around 20)
The problem with this is... is that not every one is getting it and its a random event. if anyone can reproduce this on file they need to record this in a SW RX and send it to their VAR. There is not an exact known way to fix this issue.
I did find this in the SW KB, that any of you can find for yourself.
From SW KB: Question: Why does the error message "Failed to save" appear when saving a file across a network location? Answer: Here are a few recommendations:
1) Check the location of the SolidWorks journal file. This should be on a local machine rather than on the network.
2) Under Tools->Options->System Options->Backups, set Save Auto recover info every n changes to a higher value. In addition, reduce the number of backups per document to 1.
3) If the location of the backup files is the same as the original file, (Tools->Options->System Options->Backups->Save backup files in the same location as the original is checked), then change it to another location on a local drive.
This can be caused due to a network error too, please check with network administrator.
Its Easy to point fingers, its a lot harder for someone to take the time to work on the issue to help others to help them!
![[cheers]](/data/assets/smilies/cheers.gif "[cheers] [cheers]")
![[pc2]](/data/assets/smilies/pc2.gif "[pc2] [pc2]")
