LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

CVI 2019 Debug 64 bit error "_ExtractParamInfo" could not be found

Just migrated code from my development computer (CVI 2017 W10) to my laptop (CVI 2109 W7 SP2).

I should mention that this a new install on CVI2019 from the beta.

 

Release64 compiles, launches, and runs fine.

Debug64 compiles, fails on launch with the following error "The procedure entry point _ExtractParamInfo could not be located in the dynamic link library cvirte.dll."

 

Pic of error and NIMAX report attached.

 

Looking for help. Thanks in advance.

Greg

Download All
0 Kudos
Message 1 of 7
(3,463 Views)

Your image shows some licensing wizard errors and your email address - not the _ExtractParamInfo error you describe.

0 Kudos
Message 2 of 7
(3,407 Views)

Apologies. This should be the appropriate file.

0 Kudos
Message 3 of 7
(3,403 Views)

Hello,

 

Are you deploying the Application into your new computer with LabWindows CVI 2019? Is the error appearing when you run the application? 

 

The Run Time Engine of LabWindows CVI 2019 should be able to run applications developed in previous versions of LabWindows/CVI.

0 Kudos
Message 4 of 7
(3,381 Views)

In each case, I am running from the code base with a few dlls linked in.

The program has been successfully compiled and run in the following IDE environments on two separate computers

CVI 2017 Release64 Dev Comp W10

CVI 2017 Debug 64 Dev Comp

CVI 2017 Release64 Laptop W7 SP2

CVI 2017 Debug64 Laptop

CVI 2019 Release64 Laptop

 

The same code compiles without incident but fails to fully launch with the supplied error in the following case

CVI 2019 Debug64 Laptop

 

I am trying to evaluate the the impact that upgrading might have on various projects on the dev computer. Currently those plans are obviously on hold.

 

Greg

 

0 Kudos
Message 5 of 7
(3,372 Views)

Hi Greg,

 

Could you share a screenshot of the error you get when you compile / run the executable when using Debug64 with CVI 2019?

0 Kudos
Message 6 of 7
(3,342 Views)

Here are the screen shots. The program compiles successfully. The first error popups right as the program attempts to run and before the GUI pops up. Second error happens after the first error is dismissed and CVI grinds for about 30 to attempt to "recover".

 

Greg

Download All
0 Kudos
Message 7 of 7
(3,337 Views)