Most of the time if that message comes up, rebooting the computer then trying the code again is sufficient to clear the problem.
This is definitely incorrect for "most of the time" and should not be presented as a solution, especially when that solution is as drastic as a reboot. I have
never seen this message caused by anything other than script errors. I wonder though, has it
ever happened to you (the exact same script run on the exact same data being fixed after a reboot)?
