Has anyone ever had issues with DataSocket communications related to Windows Screen Saver or Login Screen turning on?

[ATE_Dude_22]

I have two applications running on two separate hosts using the DataSocket Server to communicate. When the programs are running, everything seems to work just fine, but as soon as the screensaver or the windows login page turn on, I get corrupted data. I've tried disabling screen saver and power features to keep this from happening, however my company pushes out a policy which turns the windows login screen back on after xx minutes, for security purposes.

Has anyone ever seen this type of behavior?

[DylanC]

I have not found anyone that experienced this problem with DataSocket communications. What OS and LabVIEW versions are you using?  Would it be possible to add some type of mouse movement in your VI to prevent the computer from locking? Here is a link to another forum post where a user created just that:

http://forums.ni.com/t5/LabVIEW/Crash-on-screensaver/td-p/1132346/page/2

DylanC

[ATE_Dude_22]

Windows XP 32-bit. I'm also going to implement a mouse movement function to keep Windows Logon from opening. It appears that it's my 3rd party SW that is having the issue, not LabVIEW's datasocket server. I have written stand alone programs that simulate the datasocket connections, and I can't get it to fail whether the Logon window comes on or not.

Thanks for your help Dylan.