corrupt datasocket instalation?

[Wolfgang]

Dear All,

I am running CVI 7.0 (Windows XP SP2) and have the following problem: When selecting a URL from one of the datasocket functions (such as Open) a popup panel shows up: NI LabView Run-Time Engine 7.1.1: The feature you are trying to use is on a network resource that is unavailable. Click ok to try again... the installation package 'lvruntimeeng.msi' ...

I am a bit confused that LabView is complaining about its incomplete installation: I have no LabView at all but LabWindows/CVI; anyway, shouldn't CVI work without any LabView RTEs, or has CVI mutated to a wrapper for LabView??

Because this could be a problem of my software installation let me just tell you that this happens on a new, clean install of CVI together with the CAN, Serial, GPIB, and DAQ drivers...

Is there someout out there willing to tell me how I can fix this annoying problem? To finish the story: After clicking about 4 cancel buttons of the popup panel mentioned above, the installer finally gives up and shows the URL/opc browser. But the next time the same procedure happens again...

THANKS!

[dilution]

Hi Wolfgang,
... me again !
Did you try with c:\ ..\CVI71\samples\datasocket\OpcClient\OpcClient.cws ?
That's THE example for the use of DS functions with OPC.

I tried again just a few minutes ago with my Eurotherm OPC server. No problem, you can read any readable value.

Regards,

[Wolfgang]

Hi,

nice to hear from again so soon! Yes, I have tried exactly the sample code you mentioned! In general it does work for me as well, but only with this LabView RTE complication (installer starting) I was reporting about. Do you have any clue what the reason for this could be? Where/why does datasocket require LabView? Thanks :-)...

[dilution]

Oups! I didn't know that DataSocket needs LabView RTE.
On my computer LabView RTE is installed for sure (I have a LabView app. running).
I will try to check that on another forum.

[jlaney · Accepted solution]

Hello,

There is some more information that can help up figure out this problem.  Right click on "My Computer" and select Manage. Go to the Event Viewer>>Application log and look for MSIErrors.  The error that is  most helpful is the one that has a GUID in it and a file path.  Can you post the test from those logs?

What is happening is MSI is not finding a file or registry key that was set up as a key component of DataSocket.  It then goes and find the first thing that has that file in it to try and repair it, which just so happens to be the LabVIEW Runtime engine.  Also, CVI does not depend on the LabVIEW RTE, it is the Example finder Application that CVI uses that is written in LabVIEW nad requires the RTE.

Jeff
NI

[Wolfgang]

Hi Jeff,

Thanks a lot for your suggestion which actually solved my problem: It is me to blame, not datasockets...: Here is what I found in the application log (usually I pressed the cancel button...):

1)

Detection of product '{62DBBC58-6C51-4793-BA66-45012F8BA32C}', feature 'DataSocket.LVW71RTE', component '{713943EB-D52A-4905-AAB9-22542176A4B2}' failed. The resource 'C:\Documents and Settings\All Users\Start Menu\Programs\National Instruments\DataSocket\' does not exist.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

2)

Detection of product '{62DBBC58-6C51-4793-BA66-45012F8BA32C}', feature 'DataSocket.LVW71RTE' failed during request for component '{C5AE951F-BD96-4818-9B50-985BC02C3148}'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

3) 

Product: NI LabVIEW Run-Time Engine 7.1.1 -- Configuration failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

On my system (which is used by students as well) I moved the startup program folder 'National Instrument' from all users to administrator, so indeed Windows can not find the path specified above; I just tried by copying the folder back to 'all users', and then datasocket works nicely. Puh, Thanks a lot! But please let me ask if there is a possibility to change this default search behavior of datasockets so that it will search with a different path? I have some executables the students may use for data acquisition, but I did not want them to play with the source code - that's why I made the changes in the startup folder...