OPC Server returns error 80010105 when trying to connect with remote client

I'm trying to connect a PI-OPC interface to an DeltaV OPC Server running on my application station.  When I use OPCWatchIt to connect remotely, I can view data from the OPC Server.  However, if I try using PI's OPC client to do read data, I get the error: "The server threw an exception. (80010105)."  Looks like it's a server error, but why does one tool work and not the other.

My application station is running Windows Server 2008 Standard and DeltaV 11.3.1.

Randy

• 9 Jun 2013 7:45 PM
• Cancel

3 Replies

• Youssef.El-Bahtimy

  

  • 10 Jun 2013 5:39 PM

  Can you describe your environment?  

  Client Computer (DeltaV or Not).  If not DeltaV, did you install OPCRemote?

  If Client is DeltaV or has OPCRemote installed, does the DeltaVAdmin password on the client match that on the rest of the DeltaV system?

  What account is launching the PI-OPC interface (as a service?) and PI-OPC Client?

  I would take a look in the Windows Application and System logs of both the client and server to see if any more verbose error messages have been logged.  Additionally, Security failure auditing may need to be enabled on the systems to allow access failures to be logged to the windows security logs of the systems.

  • Cancel
• Randy

  

  • 10 Jun 2013 5:59 PM

  In reply to Youssef.El-Bahtimy:

  1. Client Computer - Non-DeltaV with OPCRemote installed

  2. The DeltaVAdmin password is set to default everywhere on the system and the PI-OPC client.

  3. I am currently running the PI-OPC Client and PI-OPC Tool interactively on the client computer.

  • Cancel
• Randy

  

  • 10 Jun 2013 8:34 PM

  In reply to Randy:

  I have enabled security failure auditing on both my client and server, and I have rebooted both machines.  However, when I try to connect to the OPC server, it still fails and there are no failure entries in the event viewer under System, Security, and Application.  The steps I took to enable failure auditing are as follows:

  1. Under local policies, I enabled audit Success and Failure for Audit account logon events, Audit logon events, and Audit object access.

  2. Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole in the registry, I added three entries (i.e., ActivationFailureLoggingLevel, CallFailureLoggingLevel, InvalidSecurityDescriptorLoggingLevel).

  What should I be looking for?

  • Cancel