Strange Error affecting All CMMs: Critical Error

are you saving programs to the desktop or to a server? 

Server

do you get the same error if you save locally to the desktop? 

Hmmmm, not sure! We can't really experiment with that easily since our programs require an extensive approval process to modify, even if just temporarily. Are you saying that because you think the server we are saving it to has memory issues?

Could you just copy and paste the existing program from the server as is to your Desktop for the experiment? To see if there is a memory error similar to when accessing programs from the server when you execute the reporting section

I could... I dont think I could take the time to reproduce the error through this method since I can't take the CMM out of production for that long, but I could monitor the memory useage when running from the desktop versus when running from the server. Ideally, I would expect this to show a spike in data useage when ran from the server. Maybe the error would occur when that spike is so great, it uses all memory resources for that second. If ran off the dekstop, maybe I wouldn't see such a spike?

I could... I dont think I could take the time to reproduce the error through this method since I can't take the CMM out of production for that long, but I could monitor the memory useage when running from the desktop versus when running from the server. Ideally, I would expect this to show a spike in data useage when ran from the server. Maybe the error would occur when that spike is so great, it uses all memory resources for that second. If ran off the dekstop, maybe I wouldn't see such a spike?

"Generally" speaking it's best to run programs from the local CMM instead of a network drive if possible. This eliminates network lag/errors/corruption and doesn't stop inspection when the server goes down. We use a process where all the master CMM programs are stored on a backed-up network drive that's write protected so only certain people have access to it. The programs are copied and loaded locally on the CMM that needs them. This also saves on calibration time, as we have a process of adding/removing programs when needed and only have to calibrate the probes/tips needed for those jobs.  

And things wont grind to a halt if a firmware update or windows update creates a situation that the Demon finds unpleasing.