LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

jam.exe and clang.exe errors

From timt to time I get the following errors when I start CVI 2013

clang error.jpgjam error.jpg

 

To get rid of it I have to start a repair of the runtime engine.

What can I do to avoid these messages in the future?

 

By the way I got no feedback for my post "Go to definition issues" from 12/22/14.

I still have this problem.

If I make a right click on a function and select "Go to definition" I go to the definition in the .h and not in the .c file.

 

If I make a right click on a control in the uir editor and select "View control callback" I go to the callback in the .h and not in the .c.

 

Sometimes it's working correctly and sometimes not.

It happens that recompiling the project or closing and starting again CVI solves the issue.

 

I don't know if the problems are comming from my project (even if I didn't had this problems with CVI2010), but I'm a bit disappointed by the stability of CVI2013.

 

Best regards

 

0 Kudos
Message 1 of 3
(4,493 Views)

Hi,

This error is probably due to an usb key that CVI held the reference.
According to this Microsft KB I would advise you to run the disk utility "diskmgmt.msc" to figure out what is that device.
Just try to disable it and you should not see this message again.
Another workaround could be to create a new project and include the existing files that have been created.

Thanks

 

 

Paolo_P
Certified TestStand Architect
Certified LabVIEW Architect
National Instruments France

0 Kudos
Message 2 of 3
(4,457 Views)

Hi

 

I did run diskmgmt.msc and got the following screen.

diskmgmt.jpg

 

Which device should I disable?

 

Bertrand

0 Kudos
Message 3 of 3
(4,414 Views)