In the last 30 minutes we've just had exactly the same issue. It took 10 or so times to try to save which it eventually did.
So its not just yourself!!!!!
I have a specific file that corrupts no matter how many times I recreate it from scratch. This is with 2017 SP1. There is an SPR1005204 for that.
I'm keeping my eyes peeled on this as I am debating and tentatively scheduled to roll-out SP2 on Tueday.
Scott, at this time my advice is DON'T DO IT!
Since this is with several different files I will send it off for an SPR and reference your's when I do.
I had that happen right after we upgraded to SP2 - but it only lasted for a few days.. Even if and when I made changes and I tried to save and that message would pop up, I would try to save again and then select cancel instead of ok, then another dialog box would pop up and ask if I wanted to keep or discard the changes and I'd hit keep and all was well.
But now it didn't happen for awhile, now I'm like is it going to come up again, or is it a relationship with a timeout issue, which is what I suspected what's happening. So for me if it came up, I don't know of any info loss..
The inability to check-in due to the over 100ms issue was supposed to be addressed with SP2. - May be related.
Well, the first attempt at an RX failed as the assembly worked fine for several new parts. But a co-worker had the problem as I was working - go figure. He has never run an RX and just kept going so I will try again a few times today.
Are you sure it's not your hardware or your modelling techniques? That's what I've been told by Timothy Taby, and he should know, he's evaluated my computer setup and my methods. It can't be the software!!!!
That's it! The hardware hasn't changed, the methods haven't changed. And it's happening to all 3 of us that upgraded to SP2 last week. It must be our fault.
ONE and TWO
Well it could be any of the following updates;
- LinkedIn (They just got a new look)
- or Yahoo (billion user gotcha's)
- Adobe Reader
- Windows 98
- Windows 99
- Windows 2000
- Windows NT
- Windows 7
- Windows 8
- Windows 9
- Windows 10
- SolidWorks 2017 SP2 (nah surely not that)
- Yep - you take the blame again (bravo)
Dennis Dohogne wrote:
some remedial training.
The only training we were getting is "Medieval Training" - just like a cow chewin it's cud - eat new stuff, regurgitate and chew the old stuff anyhow.........
I've been getting corrupt files since 2017 SP2. It seems to be related to assemblies, configurations, design tables, and even maybe to the new Tree Order option. SP2.1 needs to be released ASAP.
Well so far based on my experiences of 2017 in general, come 2018 I will be waiting until at least sp3 before installing. For me this version has been as buggy as I can remember and I've been a user since 2006.