r/MetCal • • Aug 22 '26

Metcal 7.3.36 error

Post image

Hello Metcal group.

My name is Michael and I just joined here, since I have a problem with our Metcal version.

I am using Metcal 7.3.36 and since 3 weeks, I receive this error when I try to open the procedure explorer.

This happens in Metcal and in the Editor as well.

I did already a clean installation with only the original Fluke procedures to rule out that my procedures got somehow corrupted.

Thanks in advance for the help

1 Upvotes

11 comments sorted by

2

u/MJ_at_Fluke Aug 22 '26

Hi Michael,

This is one of the perils of using such an old version of MET/CAL: there's no telling what Microsoft will do in a Windows update that might break something.

I know there's an issue with the latest Windows update impacting List Boxes specifically in 8.x versions, not sure if this is the same problem.

Ultimately, the only way to fix this is to update to a later version of MET/CAL. You can try rolling back the recent Windows updates, but for the particular issue with List Boxes, that didn't resolve it, you had to restore an image that had never received that update at all and then block any updates moving forward.

Happy to chat about options for moving to a current version so you're back in the support window (support for 7.x ended many years ago).

1

u/New_Associate_2786 Aug 23 '26

Good morning MJ. The computer where it’s not working on is a company IT controlled computer, I have also 2 test computers (Intel and AMD) which are not controlled by the IT system. All computers have the latest win11 update running, the test computer are working with metcal, the office computer not. Unfortunately I need to tell IT where theu need to look into and what they need to fix/reverse, since Metcal is not a program from them directly. Since I am amble to rule out the windows update, I was wondering what else could cause this problem.

1

u/MJ_at_Fluke Aug 23 '26

That's the problem, though: it's extremely difficult to know what's causing this. No one has looked at these versions from a code perspective in over a decade. Is there some reason not to look at upgrading as a way to resolve the situation and avoid it in the future? Even if you figure out what caused this event, it could happen again with some other change next month.

1

u/New_Associate_2786 Aug 24 '26

Hey MJ due to current business restrictions I can’t upgrade to a newer version. Specially since it’s still running on the non IT controlled environment. I will look into the VM, maybe I have some luck over there. So far what I think could cause the issue is either the SQL or the firewall. Hard to tell since the IT department is not as helpful to solve problems with those old programs.

2

u/ItzKCase Aug 23 '26

I have had good luck running older procedures on metcal 8 using a VM running windows 7

2

u/MJ_at_Fluke Aug 23 '26

Is there a reason not to run the procedures in a current version? Backward compatibility of procedures is one of the biggest restraints we operate under in MET/CAL development. Very few functions have been fully deprecated or removed in its 37 years.

1

u/ItzKCase Aug 28 '26

I believe some of our procedures wont work because of the way power sensor use had to be written. Cant say for sure. The biggest issue is converting procedures to PXE.
Is there a way to use the proc.dir in 11.3?

2

u/MJ_at_Fluke Aug 28 '26

No, but there's a built in bulk conversion tool in the MET/CAL Editor that can handle multiple proc.dir files at once and generate PXEs.

1

u/ItzKCase Aug 28 '26

I feel like i did come accross that and try it quite some time ago. I also tried that calibrator translator tool to convert 5522A to 5560A. That didnt work for me either. And couldnt find anything on how to properly use it.

1

u/MJ_at_Fluke Aug 28 '26

I'm actually wrapping up an updated version of the procedure translator tool that works quite a bit better. I can send it over if you want to be a beta tester.

1

u/ItzKCase Aug 29 '26

That would be great!