09-24-2015 03:04 PM
I am a developer on a radar test equipment project using LabWindows 2013 SP2 on Windows 7 Ultimate edition.
Our project uses an Active-X control from Foresight Imaging to display radar video using a frame grabber card. The Active-X component file is loaded into the Windows registry using the "regsvr32" command. The program runs on a PC in a closed lab.
Recently our Security official had to implement a bunch of new settings and protocols on the PC at the direction of the Defense Security Service (see the attached document). Now when I try to run the program, I'm getting a popup message that says "Error code -143: ActiveX control error". The program will only run if I right-click on its icon and select "Run As Administrator".
We are both combing through the document trying to find which setting is responsible for screwing up the program, but we haven't figured it out. Any ideas?
09-25-2015 09:22 AM
Hello,
You may want to give this knowledgebase a look over:
http://digital.ni.com/public.nsf/allkb/ECFFD8EC36AE92B9862575C20061B2D1
Please let me know if this doesn't help.
Thanks,
09-25-2015 09:47 AM - edited 09-25-2015 09:48 AM
It didn't work, I'm still getting the same error.
09-25-2015 09:50 AM
It didn't work, I'm still getting the same error.
The situation in the knowledge base article involved someone trying to run a previously built executable on a different PC. I'm running on the same PC as before, just with different security settings.
09-30-2015 08:38 AM
09-30-2015 09:17 AM
The controls are in the following locations on the PC's hard drive:
c:\Program Files\Foresight\Idea\System\IdeaCtls064.ocx
c:\Program Files (x86)\Foresight\Idea\System\IdeaCtls.ocx
I am an Administrator on this PC so I am able to get to these folders/files and set their security settings to give all Users full control, but the only change in the results is that the error changes from -143 to -145. I don't know of any restrictions imposed by the vendor.
We are not using any development environments on this PC other than LabWindows.
If we can't find a way to fix the security settings, is it possible to somehow use LaunchExecutable or some batch-file function from within a LabWindows program to automatically launch another executable with administrator privileges? I'd be looking for some function call that does the same thing as right-clicking on an icon and Windows and selecting "Run As Administrator", but from C code.
10-01-2015 08:59 AM
Our security person found the problem. It was this setting:
User Account Control: Run all administrators in Admin Approval Mode
https://technet.microsoft.com/en-us/library/jj852217.aspx