LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

"NI Network Browser Error!" When Using 'DataSocket Select URL'

We have two LV 7.1.1-built executables running on two different computers that are networked together.  Each executable starts the DataSocket Server on their own computer and then attempts to read from the other computer's DataSocket Server.  Everthing works well if both computers are running XP SP2 or SP3.
 
The problem occurs when one of the OS's is Windows 2000  SP3.  The executable on the XP computer can see the DataSocket items in the 'DataSocket Select URL' window on the Windows 2000 computer.  However, on the Windows 2000 computer, if you open the 'DataSocket Select URL' window, and try to browse the DataSocket items on the XP computer, one of the following dialogs appears:
 
NI Network Browser Error!
 
Cannot enumerate items in this hierarchy
Cannot open a network enumeration
0x000004b8
An extended error has ocurred.
 
OR
 
NI Network Browser Error!
 
Cannot enumerate items in this heirarchy
Cannot open a network enumeration
0x00000035
The volume path was not found
 
This is usually followed by a DataSocket Read error of 214701483 (this looks like a COM object error, but for once, Google didn't have anything to say about it).
 
There was a similar post to this one in which Manuel Wielander suggests setting the 'Authentication Level' to 'Connect' and the 'Impersonation Level' to 'Identify'.  He also suggested adding 'ole.AuthnLevel=1' to the executable's ini file.  None of these suggestions work.  I have also added every exception imaginable to the Windows XP firewall with no luck.
 
Anyone dare to step into the networking abyss with me on this one?  Much thanks in advance for any help or suggestions.

Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

0 Kudos
Message 1 of 6
(3,472 Views)

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

0 Kudos
Message 2 of 6
(3,463 Views)

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.


Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

0 Kudos
Message 3 of 6
(3,448 Views)
Lets try this one more time...

Chris_Mitchell
Product Development Engineer
Certified LabVIEW Architect

0 Kudos
Message 4 of 6
(3,446 Views)

Hello Archimedes,

I'll try and reproduce this issue on my computer. I'll let you know what I find out. Thanks!

Chris J

0 Kudos
Message 5 of 6
(3,426 Views)

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

0 Kudos
Message 6 of 6
(3,416 Views)