Shared Variable using Datasocket in Windows Vista

[IDILIO]

I have an. EXE that reads in a loop with datasocket read a series of shared variables published in a remote machine.

This works well in any computer running Windows XP (with and whitout develloper system), but i tried to run it in a computer with Windows Vista and it don't works.

It don't give any error, it seams that is executing the code but extremamly slow. (sometimes if the application are running several (30min.) it start to work reading correctly the values). 

When this occurs all other computers stop working also, and only restart to work a while after the aplication in vista was shutdown.

During this time using variable manager i can see taht the quality of the variables are "Connecting, Disconnected"

I'm using Labview 8.2.1

There is any limitation of using datasocket read or shared variables in Vista?

Can someone apoint somethin i'm missing...

[BenjaminR]

Hi Idilio,

Thanks for coming in National Instruments Forum. 

Did you take a look at this links?

NI Networking Protocol and Windows XP SP2/Vista Firewall Compatibility Issues

Security Alert Dialog Box Appears When Launching LabVIEW on Windows XP SP2/Vista

[IDILIO]

BenjaminR, 

 Of course this is not the problem, Firewall is Disabled!! (to despite everything)

Please see attached vi:This vi reads a shared variable "c13618_value" (double) in a library "Sym" published in a remote machine 192.168.10.25. Note the "wait for updated value" = FALSE.

I build an exe with this vi and I run it in a computer with XP SP2, it reads the value fast and its ok! I run the same .exe in other computer with vista and it takes more than 7 SECONDS and the entire vi/application is freezed during this period (it seams that is working because at the end the value read is correct, but it takes a long time, and all the application freeze during this time, you can imagine what appends when the application reads much more variables).

To run the EXE in the computers I installed Run-Time 8.2.1, Shared Variable Engine, and DataSocket. (If I don't install Datasocket the vi takes normal time to run, of course it can't read the value).

A strange thing is that I tried to install DataSocket running directly Datasocket.msi in \Volume\bin\p0\DSC.DS.440 folder, it installs ok in XP, but in Vista it reaches an error: Error 1721 - A program needed to finish the installation can't be executed. 

This is a simple vi, this problems occurs running in any Vista (business 32 bits) computer, so it's supposed that this should be a very know issue.

I don't know what more I can test. Please I need help.

Message Edited by IDILIO on 11-26-2008 04:11 AM

[BenjaminR]

Hi Idilio,

Error 1721 will only happen if the MSI is run by itself on VISTA due to the way VISTA handles security: by default it will run the part as a Least User. The executable will not have enough permission to run and it will trigger error 1721. Do you have the Admin Right? Running the setup.exe will cause Vista to promote the setup.exe to Administrator and this error should not crop up.

[IDILIO]

I suppose I'm the administrator (unique user in S.O) but with Vista nobody knows....

Anyway this is only a curiosity, the problem still remains....

Message Edited by IDILIO on 11-27-2008 03:46 AM

[IDILIO]

3 years later and I stopped in the same point...

I need to install NI Datasocket in a client using Windows 7, when I run the setup it reaches an error:

"Error 1721. There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor."

Then I googled, and surprise, the only item related was my post from 3 years ago related to vista.

It's strange how this problem doesn't happen to everybody, but...

I supect of this ridiculous extra security issues, then after hours of investigaton I discover that changing 

Control Panel -> System and security -> Change User Account Control Settings to Never notify the installer runs perfectly. Then it can be back to default...

Stupid security issues from Microsoft....Who payed this hours?