Failed to save document. - DASSAULT: SOLIDWORKS 3D Design (2024)

thread559-178809

Chris
SolidWorks 07 2.2/PDMWorks 07
AutoCAD 06
ctopher's home (updated 02-10-07)

that thread ends with no conclusion except you saying 'go search'

oh well i terminated sw and started it up again.working now on getting back up to where i was at.

btw, im working completely off a network, all parts were originated on my computer and theyre all on my computer.

uGlay,
Sounds like your PC may not be big enough for the assembly you are working on.
My advice is to save often.

Bradley
SolidWorks Professional x64 2007 SP2.2
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
NVIDIA Quadro FX 3400

I suspect somebody was hacking.

I am almost back up to where i left off before the accident.

What are your system specs and settings? Particularly RAM and VM.
Are you using the /3GB switch?

uGlay,

This is a common problem with no real solution.There are many things you can do that sometimes work but no guarantee.Unfortunately you never know when it will happen and it is not repeatable (at least we have been unable too), thus making getting an Rx impossible.

SA

good morning all,

I actually had this happen to me over the past couple of days.I got the "Failed to save document" error last Friday and as I was angrily trying to resolve the problem, I received the "Solidworks must close due to blah blah blah" error message and I lost a few hours worth of work.

This morning I got the same "Failed to save document" error on the same large assembly (731 components with 219 top level mates).Using a fresh upbeat monday morning outlook (yeah right), I approached the problem with a nicer attitude.

Basically, I went through and resolved ALL assemblies, sub assemblies, parts, etc.Having everything fully loaded and unsuppressed, Swx allowed me to save.

Just thought I would pass this along in hopes it will save someone else some heartache down the road.

Solidworks 2007 SP2.0
2GB Ram/3GB Switch
Quadro FX1300
P4 3.40GHz Duo XP Pro SP2.0

mmh interesting.

Ive been getting the same error this morning with the same file.Ive been saving after every 3 ops or so.

Ill try to resolve everything if this happens again.

Just FYI from my personal experience...if the assembly is already resolved, then setting it to lightweight and then back to resolved, by right-clicking on the top menu tree item, will solve the "failed to save document" issue as well.

SW2k7 SP2.2

I have been getting this error a lot lately. Failed to save document
I removed light weight, regenerated, no help there. So I have upgraded to sp 3.0 to see if that helps.

Bradley
SolidWorks Professional x64 2007 SP2.2
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
NVIDIA Quadro FX 3400

I got this error today which is what lead me here via a google search. I'm on SP2.2

I was able to fix the problem (got the assembly to "SAVE")by deleting all of the configurations that I created AFTER the last time I saved the Assembly. I'm guessing it did not like the configurations that I created since that was the only change I made to the Assembly.

I just downloaded SP3, we'll see if that helps.

I upgraded to SolidWorks 2007 SP 3.0 and turned on “Verification on rebuild” under tools, options, System Options, Performance. Since doing these two things, I have been able to save all morning without issue.

I think this will fix the Windows XP issue “Failed to save document”. If you do get this message check your file size, to see if it is 10 times what you think it should be. Then call your VAR.

Bradley
SolidWorks Professional x64 2007 SP3.0
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
Virtual memory 12577 MB
NVIDIA Quadro FX 3400

I got the "Failed to save document.." problem as well, and I've no idea how to fix this problem.

I only work with very little files (assemblies of max. 3 parts). The strange thing is that the problem doesn't occur with drawing files, but only with parts and some (!) assemblies (not even all.)

My graphics card is a GeForce FX 5200, not recommended, but since I work with this card for 3 years, I don't think this is the problem.(the pc in for 3 years in the same configuration; Pentium 4, 1 gig RAM, 120 gig HDD, SolidWorks 2005!, on a netwerk (that has been reconfigured last days....can this be the problem?))

It started today, by shutting down the program while I was making an adjustment in a sketch. When I reloaded the program to continue my work, I couldn't save the documents no more. Since then, I don't no what to do. Please, help me to find a solution.

Arnout, did you try all the suggestions on this thread?

Like resolving all components and then trying to save again.I havent gotten this message again but then, im not working on that particular file anymore where i was getting the error window.

Arnout,
Our VAR told me about this one. Upgrade to SolidWorks 2007 SP 3.0. Also turn on “Verification on rebuild”. Since I have done this I have never gotten the Failed to saved message.

Bradley
SolidWorks Professional x64 2007 SP3.0
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
Virtual memory 12577 MB
NVIDIA Quadro FX 3400

It sounds like the “Verification on rebuild” does the same as using Ctrl-Q before a save.

"Verification on rebuild" and CTRL-Q are not the same....

As for Ctrl+Q vs Ctrl+B (Standard rebuild)- a standard rebuild rebuilds any feature which has the rebuild icon over it – or rebuilds a sketch while editing.A Ctrl+Q rebuild rebuilds every sketch and feature from the beginning of the tree.

Verification on Rebuild=From the on-line help: by default, each time a feature is added or modified, the feature is checked against any adjacent faces and edges. To increase the level of error checking, turn on the ‘Verification on Rebuild’ option. When this option is turned on, the software checks every new or changed feature against all existing faces and edges, not just adjacent faces and edges. Features that cause invalid geometry fail when this option is turned on. This option has a negative effect on performance. Rebuilding the model is considerably slower and more CPU-intensive. This option applies to all documents, not just the active document. Use this option only when needed, and then be sure to turn it off when done.

Cole M
CSWP, CSWST, CSWI, CPDM
SW06
SW07
IBM T42p, 2g proc., 1g RAM,ATI Mobility Fire GL T2
HP XW4100, 3g proc., 3g RAM, Nvidia Quadro 980 XGL
HP XW4300, 3.4g proc, 2.5g RAM, ATI Fire GL 3100

Verification on Rebuild is turned on and I resolved the assemblies. I turned the virtual memory to 4096 (min&max) (I read that somewhere else) and emptied my Temp. files.

So far, I am able to work in assemblies & drawnings, but when I try to save a part, the program will shut down.

When I save the same file on my laptop at home (no network), the problem doesn't occur.

Does the resolve function has influences on parts? Must I set everything on 'always' in the System options -->Performance --> assemblies ?

Well, maybe I should upgrade sw to SolidWorks 2007 SP 3.0...

I upgraded to SP 3.0 and upgraded our vault to SP 3.0, to fix a different problem. I turned on “Verification on rebuild”. I saved everything for about a day without any issues. Then last nights save failed. Now are there any ideas on how to fix this problem?

Bradley
SolidWorks Professional x64 2007 SP3.0
Intel(R) Pentium(R) D CPU
3.00 GHz, 3.93 GB of RAM
Virtual memory 12577 MB
NVIDIA Quadro FX 3400

We've been battling this one also.

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: Failed to Save meintsi suggested that his IT guy did somthing on the network and it all went away... but meintsi never said what they did....

Mikka

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)

Can you do a Save or Save-as if you delete the Design Table.

Make a copy of the assembly first ... from Windows if necessary.

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!

Regards,

Scott Baugh, CSWP
www.scottjbaugh.com
FAQ731-376: Eng-Tips.com Forum Policies