Thanks for the reply. When updates are released for the COM object, how can we keep in contact to be notified?

Right now I have a Kepware OPC Server setup with 7 simulator tags. Each subscribes to a unique simulator tag. So they are subscribing to different tags, so I don't know if this is the same issue.

I'm going to continue to debug and will update the thread if I discover anything additional.

Hey Guys,

I'm currently in the process of writing multiple services that connect to a PLC and subscribe to 2 items on each service. Right now there are 7 services. They are each unique to control unique logic themselves. Anyway...

Once I start about the fifth service, the EasyOPC service seems to crap out. The 4 connected services then disconnect from the PLC and output this exception message:
Source: OPCLabs.EasyDAClient.5.2
Description: Write not completed. This error indicates that it could not be verified that the requested write operation was completed during the timeout period. It is possible that the write operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled).

I think it's obvious I'm overloading the service, but I don't know why or how. The items I'm subscribed to are only float values at change roughly every 5 seconds. Anyone know how I could further diagnose what is going on here and/or why easyopc is getting bogged down to the point that I need to restart it to get it to reconnect.

Thanks for any help!!!