Since moving to Met/TEAM and Met/CAL 9.1, our lab has had difficulty saving cal data. At it's best, it would sporadically lose one or two calibrations a day. This has only gotten worse with a recent upgrade to Met/CAL 9.1.1. Currently, I'm only successfully saving cal data one attempt out of eight. It appears to be limited to a few error codes, but every once in a while we see a new one. Has anyone else encountered this problem to this degree? I've added some snips of the error messages
Hi Jeff, I am going to convert this post into a support ticket for you. This is most commonly caused by a non-standard character in the procedure name, but we need the log files from the server to be able to pin it down. They are located at C:\inetpub\wwwroot\METTEAM\Logs by default. When you get the new ticket notification, can you please respond to it (not here) and attach your log files?
Thank you,
Chad
I can't, no. I have no METTEAM folder...
I've had the E5483 message once.
Chad, what characters are not allowed in the procedure name? I have some programs that either won't save data or cannot use procedure sectioning and that is probably the reason.
Hi Troy, I'm not 100% sure on this (it has been a while since I've done heavy coding in MET/CAL) but I am pretty sure ampersands are not compatible with procedure sectioning. If you would like more confirmation, we can create a software support ticket and confirm if other characters may affect it.
-Chad
We always recommend sending in the cal dump file to Fluke Software Support because it sometimes explains the reason the error occurred.
Also, version 9.1.1 fixed some issues present in 9.1 which may have contributed to certain cal dump errors.
-Chad
Please sign in to leave a comment.
6 comments