Has the matter of the error message that my file is "corrupt and cannot be saved" ever been solved?
I have found that if I go to in assembly mode click on the tab Evaluate, then Performance Evaluation icon and look at Previous Version References and update those file that I am able to file the assembly.
I have been dealing with this problem for a week or so now.
work arounds are how I manage to get work done when the software gives me problems.
Contacted the var and was informed that 90% of my problem was the network connection. A little time out or interruption could cause this. If you ever had the opportunity to work on a file off a floppy drive you know how much traffic a model in SolidWorks can create.
Just in time for lunch I had my file go corrupt again. save as to the net work, fail....create a corrupt folder on the desk top and save file there then save back to network everything works fine.....
Also had to restart my e-mail around this same time so it had to be a connection problem. ...
We were having the problem even when saving to our C drive. Turned out that it was a bug that was fixed with SP 3.0 if I recall correctly. We have had no problems since moving to a newer SP
Try this. With the model open, go to the configuration tree; right-click at the top; "Rebuild/Save Mark -> Remove mark and purge data for all configurations". Then try saving. This has worked for me and coworkers, hope it helps you too.
I have been burned too many times by trying to work off the public drive and having it hiccup and not work that I tell all my coworkers that they'll get burned if they try to do it. Luckily, I haven't heard of any problems. And, I do know some of them are doing it.
We do have Auto-Recover turned off, though (which as someone else stated may be causing/contributing to your problem).
How do you handle more than one person working on an assembly at a time if you all work locally? Do you have PDM? Without PDM we work of the server and if someone else has an assembly open we can only open it read only. I have been other places where guys work locally and then "he who saves last wins". I can see that being a big problem.
That is a very good question. We used to have WPDM (still do on 2014). But we are transitioning to DDM, but don't have it installed yet. So, we have quite the kludge going on right now. Hopefully we get DDM setup soon.
But, to be clear, I don't advise collaboration without PDM. Maybe someone has figured it out, but that person is not me. But sometimes companies only spring for SWX Standard, and users don't have access to PDM. I gave my answer in that context. Thanks for bringing this up to clear that up.
Jim Steinmeyer wrote: David,We were having the problem even when saving to our C drive. Turned out that it was a bug that was fixed with SP 3.0 if I recall correctly. We have had no problems since moving to a newer SP
Jim Steinmeyer wrote:
2017 x 64 sp 3.0
it hit me right at the end of the day, again and I think I lost the assembly and the drawing....could not open any thing I saved to the hard drive.
Do you have the auto save turned on? Shut that off and see if it helps.
Jim's right. Was that fixed in SP4 or SP5? I don't have the time to find that information in the With SW2017 SP2 we are seeing frequent corrupt files in assemblies thread. Regardless, I never turned it on, thankfully.
I was having this same problem peroidically, (once a week). I was using 2017 SP 3.0, SP 4.0 was broken, SP 4.1 and SP 5.0 we didn't try. We have move to 2018 SP 1.0 and haven't seen any of this error all month.
Well tech support said it was a network problem....now I hear that it could be a software problem. Since I am the only one really seeing this I was thinking that I had a mouse problem chewing threw a cable somewhere. Now I am not sure to call out the tech guys to check the cables or not...
Try shutting off auto backup and see if the problem goes away. Fails once and you can always call tech support.
them auto backups are valuable. Many of times have saved projects that someone else had decided to delete. Tech support already said the problem was the network. Just every now and then I get problems... maybe while working on that assembly I can turn them off to keep it right.
I've run into this a few times, but have always managed to get around it. See if any of the suggestions at I got an error message when I tried to open a SW file. will work.
Today is a bad day to be working on parts and assemblies that are corruptible. Usually I can get the drawing to bring them back in line but this time they took the drawing with them. Any idea how much of this is caused by sharing files. I am constantly having to get write access and give write access to some of these files that are being so difficult.
Retrieving data ...