07-08-2005 04:52 AM
07-14-2005 07:04 AM
07-14-2005 07:49 AM
Sacha,
I've found that this seems to be a problem with CVI 7.1.1 generally, rather than the TestStand operator interface. If I start CVI 7.1.1 the installer starts as well. The thread http://forums.ni.com/ni/board/message?board.id=180&message.id=16824&view=by_threading&page=2 seems to be the same problem
i.e.
The error deals with a shared component to contain ActiveX controls. CVI loads this at startup using COM, and if the registry keys are not correct then MSI launches to fix itself. If you cancel and do not allow it to reapir you should notice that FunctionPanel help is straight HTML not displayed as it should be. There seems to be something stomping on our registry keys here, and something like this happened around the 6.0 timeframe and seems to be happening again here lately.
To solve this you should be able to go to [Program Files]\National Instruments\Shared directory. Run regsvr32 on nicont.dll and nicontdt.dll in this directory. That should reregister the control for COM for you and stop the MSI dialog from showing up.
However I've run regsvr32 on these DLL's and it doesn't make any difference.
Regards,
Brian
07-15-2005 09:21 AM
07-19-2005 02:33 AM
Sacha,
The non-networked user is already has administrator privilege.
Regards,
Brian
07-20-2005 07:43 AM
Hi Brian,
as per that forum link you put in last time, there's still some content that isn't correctly registered that's shared between LabVIEW and CVI then.
Since this is an additional user, then it can really only be a registration issue.
The idea of using regsvr32 is still valid then, however knowing which dll's and ocx's to work with is the difficult part.
There's an error log which you should be able to find I think it's cvierror.txt.
It's actually an xml layout, but if you could open up cvi, get the error for the installation, cancel it, and then search your hard drive for .txt files generated "today" then you should be able to find it. Attach it to this thread, and then we'll see if that yields any ideas as to which components aren't showing up as registered correctly (try the windows\system32\cvirte\bin directory)
Thanks
Sacha Emery
National Instruments (UK)
07-20-2005 09:51 AM
Sacha,
I don't think that cvierror.txt file is an error log. I searched for cvi*.* (everything for the past day) on my entire hard drive and basically found nothing. (except recent entries for cvierror.txt, but that's because I'd opened it with notepad...)
Regards,
Brian
07-21-2005 07:42 AM
Hi,
when the installation window comes up does it say anything like :
Event Log Warning Message 1
Detection of product '{B652CC58-6222-4149-B52D-C632AEE8C66C}', feature 'LVRT' failed during request for component '{95A2F34E-BBED-429D-AD92-49FB0BAE03F2}'
in the event viewer?
(start->settings->control panel->administrative tools->event viewer
and then select system or application)
Thanks
Sacha Emery
National Instruments (UK)
07-21-2005 08:51 AM
Hi Sacha,
Similar, Its
Detection of product '{B652CC58-6222-4149-B52D-C632AEE8C66C}', feature 'LVRT', component '{A4C7356A-DA80-11D3-80E5-0050049FD55D}' failed. The resource 'C:\Program Files\National Instruments\shared\LabVIEW Run-Time\6.0\models\pb_h.ptc' does not exist.
Detection of product '{B652CC58-6222-4149-B52D-C632AEE8C66C}', feature '3DGraph' failed during request for component '{95A62C27-864C-11D3-AB56-006008CA11D7}'
and
Product: NI LabVIEW Run-Time Engine 6.0.2 -- Error 1706. No valid source could be found for product NI LabVIEW Run-Time Engine 6.0.2. The Windows installer cannot continue.
Hope this is useful!
Regards,
07-22-2005 08:12 AM