Inspect "cannot access probe file" error message

Hi all-

I know this should go in the Inspect forum but literally no one has posted there in like 3 months and I need help!

So I have a customer running their programs through Inspect 5.1 and they are running through the programs fine but at the end of their program running they get this error:

The process cannot access the file '(file path)\(their probe).probe' because it is being used by another process.

Does anyone know the reason this could be or has anyone had experience with this error before?

I will be going there tomorrow to try to fix it but I was curious if anyone had any ideas. Why would Inspect need to access this file concluding a measurement routine? Any help is appreciated, thanks.

Parents

0 Jeremiah Fitzmartin 9 months ago

I have run into this alot. In most cases it turned out to be either an antivirus or antimalware software that flagged it for monitoring. Having my IT exclude those files from their monitoring software fixed it for me.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Jeremiah Fitzmartin 9 months ago

I have run into this alot. In most cases it turned out to be either an antivirus or antimalware software that flagged it for monitoring. Having my IT exclude those files from their monitoring software fixed it for me.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Cole Bergeron 9 months ago in reply to Jeremiah Fitzmartin

I'm in need of some clarification:

The antivirus or antimalware is keeping Inspect from accessing external files?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Neil Challinor 9 months ago in reply to Cole Bergeron

Whilst PC-DMIS is executing a routine, it is constantly reading from and writing to the .prg file and reading the .prb (probe). Once the routine has finished executing and is closed, PC-DMIS releases those files. However, if an anti-virus application is scanning a file at the same time PC-DMIS needs to access it, you will get a message like the one you are seeing because, as far as the PC is concerned, the file is already in use.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel