OPC connection failure

[wdmarner]

I'm continue to troubleshoot OPC connectivity via Shared Vairables. I've attached the error log output by LabView. Any ideas on the proper fix for this? I'm assuming it's making the proper registry entries, but I'm not sure where to begin. The errors are "Class not registered" problems. Everything is running on the local machine, and I can get standard OPC clients to connect, but not the Shared Variables. 

The relevant errors are at the top of the log.  

[Andrew_E]

Hi, is this the same topic as this. If it is we should stick to the older thread. However, for the time being, have you checked your dcom settings?

In order to successfully communicate to the OPC server, you need to allow the proper exceptions in the Windows Firewall.  Open up the Windows Firewall from the Control Panel, and select the Exceptions tab.  Click on Add Program... and add the following:  

1. All OPC Clients and Servers
2. Microsoft Management Console
3. OPC utility OPCEnum.exe found in the Windows\System32 directory
4. Next, In the Exceptions tab of the Windows Firewall, click on Add Port...
5. In the Add a Port dialog, fill out the fields as follows: (Name: DCOM) (Port Number: 135) and check tcp

[wdmarner]

Your link led to this post, but you may be referring to my previous posting on this problem. We can keep on that thread. 

My windows firewall is turned off, and I"ve check all the DCOM settings...everything looks okay, including the permissions and local security settings. Also, both my server and client reside on the same computer. 

Thanks for looking at this,

Wes

[Andrew_E]

Hi wdmarner,

Can you go ahead and change the identity property of the Shared Variable Engine Service.  You would do this by:

1. Go to Control Panel » Administrative Tools » Services to open the Services Manager.
2. Right click on the National Instruments Variable Engine service and select Properties.
3. In the properties dialog box, select the Log On tab.
4. Change the Log on account to be Administrator, then click OK.
5. Restart the SVE service to put the above changes into effect.