Some possibly wild ideas:

Check the user account the server is running, or perhaps use a different one.

Allow the service to interact with the desktop - it may be trying to do some UI but cannot - there is a checkbox for it.

You are correct, this is a problem with the target OPC server. I was able to establish a connection to a different OPC server indicating there is no problem with the OPCLabs driver or installation, and I reproduced the same behavior from a different OPC Client.

I realize that OPCLbas therefore is not at fault in this issue, but we are at a loss as to how to troubleshoot, so I would appreciate any further input you have.

I am able to talk to the malfunctioning OPC Server using the OPCLabs driver running in a process on that machine (and this process is 64-bit whereas RSLinx is 32-bit which, from our discussions before, means that it is in essence establishing a 'remote' connection if I understood correctly).

Do you have any suggestions? (I take it running the connection through OPC Analyzer wouldn't work since OPC Analyzer is unlikely to be able to establish a connection to the malfunctioning OPC Server either).

Thanks,

Shea

Yes it does. Most likely you will get the same error in any other OPC client. Unfortunately it is difficult to tell what is the reason for it, because it's server-specific.

The error is reported reported a notification (ItemChanged). Does this indicate a problem with the target OPC server?

Thanks,

Shea

Is it your service, using QuickOPC, that does not start?

Or is it an error from a target OPC server, reported through a notification (ItemChanged?)

I am getting the exception "the service did not respond to the start or control request in a timely fashion" when trying to subscribe to tags.

I don't believe this is a problem with QuickOPC as everything was working correctly prior to the server being rebooted. However, I am at a loss as to how to go about troubleshooting this.

Do you have any suggestions?

Thanks,

Shea