TestStand Message Popup Steps, LabVIEW and CVI OIs Fail to Execute After Installing LabWindows/CVI 9.0.x Run-Time EnginePrimary Software: TestStandPrimary Software Version: 3.5 Primary Software Fixed Version: 4.0 Secondary Software: LabWindows/CVI Development Systems>>Base Package
Problem: I'm using TestStand 3.5 or prior and I recently upgraded to LabWindows/CVI Run-Time Engine 9.0.x. After upgrading I am now receiving error -143 ActiveX Control Error when TestStand executes a Message Popup step, and my LabVIEW, LabWindows/CVI OIs fail to launch. Why is this happening and how do I fix it? Solution: Note: The problem described in this document does not occur with TestStand 4.x and later. TestStand user interfaces built with LabVIEW and LabWindows/CVI use an NI ActiveX Container DLL to load the TestStand UI Controls. Similarly, the TestStand Message Popup step utilizes the NI ActiveX Container to support displaying web pages in the Microsoft Internet Explorer control. The LabWindows/CVI 9.0.x Run-Time Engine installs a new version of the container, which depends on the Microsoft Visual C++ 2005 MSVCP80.DLL and MSVCR80.DLL; however, the LabWindows/CVI 9.0.x Run-Time Engine does not install these two, necessary DLLs. When the dependent DLLs are not present on the system, an application utilizing the NI ActiveX Container fails to load, resulting in an error. Deployment installers created using the TestStand Deployment Utility include a copy of the system's LabWindows/CVI Run-Time Engine and the NI ActiveX Container DLL. The problem discussed in this document may also occur when the deployment installer packages the LabWindows/CVI 9.0.x Run-Time Engine and does not install the dependent DLLs on the target system. Installing the Microsoft Visual C++ 2005 Redistributable Package or an NI component that installs the necessary DLLs will solve this problem on a development or deployment system. To preemptively correct this behavior in a deployment installer, you must include an NI component that installs the dependent DLLs , such as the NI Variable Engine. Related Links: KnowledgeBase 4XPBOIXU: Error -143 Occurs When Running a Deployed CVI Program Using an ActiveX control KnowledgeBase 3OPEORS9: Why Do I Get Error -143 When I Call my CVI DLL from TestStand? Attachments:
Report Date: 06/03/2009 Last Updated: 06/08/2009 Document ID: 4Y29CNXU |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
