07-20-2005 09:08 AM
07-21-2005 04:09 PM
Hello,
Just a few questions. Does this happen on all Win 2k computers? Are the 2 computers on the same subnet? Also, would you be able to provide a screenshot of the error? Thanks!
Regards,
Chris J
07-28-2005 11:51 AM
This happens on all Win 2k computers when trying to browse the DataSocket items on a Win XP computer. The Win 2k and Win XP computers are always on the same subnet (and usually sitting within a few feet of each other).
As far as I know this problem didn't exist when we were using the LV 6.1 runtime engine (but then, XP wasn't that prevelant back then either).
Thanks for any assistance.
07-28-2005 11:55 AM
07-31-2005 11:54 PM
Hello Archimedes,
I'll try and reproduce this issue on my computer. I'll let you know what I find out. Thanks!
Chris J
08-01-2005 03:16 PM
Hello Archimedes,
This problem is a bit difficult to track down. I have Win 2k SP4 and WinXP Pro computers and am unable to reproduce the issue at the moment. However, I have found information that this issue has occurred in the past. In some instances it appears that changing the DataSocket Select URL.vi's Preferred Execution System to something other than "user interface" (eg. "Same as caller" or "standard") from VI Properties>>Execution resolves the problem. However, this is not a guaranteed workaround. R&D is aware of the problem and is working to fix it. I apologize for any inconvenience.
Best Regards,
Chris J
National Instruments