PCo - Error starting the agent instance

[Former Member]

Hi,

I have 2 agent instances pointing to the same OPC server. One of them starts fine but the other one throws an error 'Error starting the agent instance as a service'. Can somebody explain whats going on?

Chanti.

[Former Member · Accepted solution]

Chanti,

Can you check the port numbers are same for the two instances.If they are same then it will throw an error.Another possibility is that how many connections licence OPC server has.Can you post the messages available in the Event Viewer available in ControlPanel---Administratavi Tools.Also post the error messages in the Pco log file.

One thing I'm not clear here that why do you want to use two instances for the same OPC server.May I know the purpose for it.

-Suresh

[Former Member · Accepted solution]

Actually, I have not 2 but 3 agent instances pointing to the same OPC server. Only 1 of those gives the error; the other 2 work fine. Any thoughts?

Chanti.

[Former Member]

I am also facing an error starting the agent instance as a service, getting the following:

failed to create ConnectivityAgentProxy : This request operation sent to net.tcp://localhost/ConnectivityAgent/test did not receive a reply within the configured timeout (00:05:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

I'm able to connect and browse the tags via the Subscription Items tab in the agent configuration.

[Former Member]

Try to end the existing process for your OPC Server 'KEPWare' in the task manager. You can then try to subscribe to the tag from PCo Agent Instance. It should work. I believe there is a limit of 2 hours on each KEPware instance. Let me know how it goes.

Regards,

Chanti.

[khaleelurrehman_badeghar]

Hi,

Check by stopping and restarting the UDS instance.

BTW also delete and reconfigure the instance.

Regards

Khaleel