PCo - COM exception

[former_member192939]

Hi,

Background:

PCo connected to Matrikon OPC DA successfully (DA 2.05A).

Issue:

I am trying to connect PCo to SV OPC DA server (DA 2.05A).

PCo has similar configurations for SC OPC as Matrikon OPC.

Error obtained: COM Exception [HRESULT = -2146959355] from LegacyOpcWrapper

More Info:

PCo V 2.0.1.8

Able to browse subscription Items

successfully connected to SV OPC DA with Matrikon Explorer.

Need help to overcome the issue, thank you for your time

- Ajay

[former_member196557 · Accepted solution]

The reported error is the Microsoft COM "Permission Denied" error.

1. Are the OPC Server and PCo installed on the same server?

2. Are the Matrikon Explorer and SV OPC Server installed on the same server?

3. What is the workgroup/domain configuration for the servers if PCo and OPC servers are installed on separate servers?

4. Can you find the SV server in the list of available servers in the OPC Source Agent configuration?

This error is usually caused by DCOM configuration issues between OPC Servers and clients installed on separate PC's.

- Steve

[former_member192939 · Accepted solution]

Thanks Steve for the quick response

1. Are the OPC Server and PCo installed on the same server?

Yes

2. Are the Matrikon Explorer and SV OPC Server installed on the same server?

Yes

4. Can you find the SV server in the list of available servers in the OPC Source Agent configuration?

Yes

[former_member196557 · Accepted solution]

OK, it is not a DCOM error since all the servers and clients are on the same PC.

Where is the error being thrown, on agent instance start or on on an instance notification event?

Place the debug level of the agent instance into Verbose and see if there are any additional messages in the log that could indicate the issue.

It sounds like either the SV server is not completely 2.05 compliant.

Are you running both a 2.05 DA agent connection (SV) AND a 3.0 DA agent connection (Matrikon) within the same OPC source agent? If so, try to create a new source agent for just the SV OPC server and try starting it without starting the Matrikon-connected OPC Source agent.

What is the full name of the OPC Server, and a web site link?

- Steve

[former_member192939 · Accepted solution]

Where is the error being thrown, on agent instance start or on on an instance notification event?

- Agent Instance Start

Place the debug level of the agent instance into Verbose and see if there are any additional messages in the log that could indicate the issue.

- Error happens when establishing a connection

Are you running both a 2.05 DA agent connection (SV) AND a 3.0 DA agent connection (Matrikon) within the same OPC source agent? If so, try to create a new source agent for just the SV OPC server and try starting it without starting the Matrikon-connected OPC Source agent.

- I have been trying the same for a while, no luck

What is the full name of the OPC Server, and a web site link?

- http://www.opcfoundation.org/Products/ProductDetails.aspx?CM=1&RI=8907&CU=1

In the DCOM Config ... what i have noticed is the application starts as current user, instead of that if it can be setup as service it might work, I will talk to the SCADA team and post an update.

Thanks Steve,

- Ajay

[Former Member · Accepted solution]

Ajay,

Do the server logs give any more clues than the PCo logs as to what could be the cause? Sometimes the PCo logs have less information than the logs in the event viewer. Just a thought...

Kevin

[former_member192939 · Accepted solution]

After the upgrade of OPC .. Selected the check box run as application and is now connected!

Thank you for all the replys.

- Ajay.