0

Failure saving cal data...

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

7 comments

Date Votes
0
Avatar
Dexter

Hey Jeff, I haven't run across any of those specific error messages but I have frequent issues with Met/Cal failing to upload data to Met/Team and creating a caldump.txt file. I do not know if your issues are the same as mine but when I contacted Fluke about it they said that they are aware of it and MAY address it in a future release. You should touch base with them but their response to me was essentially that I am completely out of luck and losing 1 in ever 4 power meter cals (that take about 4 hours to run) is just life now. Sorry I don't have better news. Below is the e-mail they sent me:

 

Hello Steven,

I hate to bear bad news, but there is currently no way to push the information in the caldump.txt file into the certificate in the same way as if MET/CAL had successfully written the data.  An option you have, outside of re-running the procedure, is to attach the .txt file to the WO and reference it on the certificate.  This has been an item placed on the improvement list in development queue and may be addressed in a future release.

I will mark this as solved, though you may reply to reopen it.

Neil Hutchings | Technical Support Engineer | Phone: +1 877 355 3225

0
Avatar
Chad D.

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

0
Avatar
Jeff Hulkonen

I can't, no.  I have no METTEAM folder...  

0
Avatar
James Steeds

I've had the E5483 message once.  

0
Avatar
Troy Howard

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.

0
Avatar
Chad D.

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

0
Avatar
Chad D.

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.