Why the list of tags do not show up in OPC quick client window under National Instruments.NIOPCServers?

[ProVG]

I have OPC server installed on two different operating systems (i.e. windows server 2003 (32-bit) and windows 7). Under windows 7, once I open simdemo.opf example, after selecting Tools>OPC Quick Client, I can see the list of tags created for specified channels. But under windows server 2003, nothing is listed under National Instruments.NIOPCServers in the OPC Quick Client window. The version of OPC servers are the same.

Any help or guidance would be greatly appreciated.

Thanks,

[charris]

ProVG:

If you're seeing the issue on a server edition of Windows, I'm guessing it has to do with the firewall and/or DCOM settings on the machine.

Check this guide on the OPC Foundation site for more information on the DCOM and network settings required. It should give you an overview of the required firewall and DCOM settings.

Hope that helps!

[ProVG]

Hi Caleb,

Thanks for providing me with this document.

I reviewed this document along with a few other documents that I could find online regarding DCOM settings. It looks like on the system that I'm working on, all the permissions, firewall exemptions, and ports are open. But I still cannot monitor the tags on OPC quick client.

I also looked into the following resources:

http://www.automatedsolutions.com/technotes/opcserverconnectivity/Default.asp

http://digital.ni.com/public.nsf/allkb/9D1690C5B1CE1D25862572FA0053150D

but no resolution yet. I was wondering if you had any other thoughts regarding this.

Thanks,

ProVG

[charris]

ProVG:

Are you trying to access the OPC server on the local machine, or over the network? I can't figure out if the two operating systems are on the same computer

Do you have the Shared Variable engine installed on that computer (it's the NI Variable Engine in the Windows services manager)? If so, can you see its OPC server?

Can you see any other OPC servers on the system? If so, then it's likely an issue with NI OPC Servers. Otherwise, we probably still have a communications/network issue to track down.