It’s been a while since the last post – I’ve been busy with an Endpoint Summit (I’ll post the likely embarrassing video after Symantec does) and several customers, and my free time has been consumed with family and Dark Souls II. So it’s past time that I post something.
During a working session with a customer two weeks back, I ran into something I haven’t seen in a while. After making some major changes with data types and mapping in the project, I attempted to spool the debugger, and got this:
Now, once upon a time, this error meant to me that “oh crap, there goes an hour’s worth of unsaved progress”, because this problem prevents saving the project as well. While I don’t have a sincere diagnosis for the problem, I certainly figured out the hammer as a solution.
What this error seems to mean is that there is a really horrible problem somewhere in one of the models (possibly the primary model). The only way I’ve been able to recover from this is to start at the primary model, select everything (Ctrl + A) and either: 1. Delete or 2. Cut (Ctrl + X). Yes, as I said, it’s a hammer. Then, attempt to save the project. If the save works, then go ahead and Undo (Ctrl + Z, whether you deleted or cut) or Paste (Ctrl + V, if you cut). If it’s a complex model, it may take a bit to restore the model. After it’s restored, validate the model and attempt to save again. If the save attempts are not successful, try other models one at a time.
So far, this issue has only occurred twice in 7.5 (earlier versions of 7.5, anyway), but it would happen once a day back when I did full time development in 7.1. Suffice it to say that I really wish I’d known about this “fix” back then, because I lost a lot of work back in those days to this bug.
Hope that helps someone in the future!