We've got a newer DV11.3 system being installed and I'm trying to connect it to the existing DV9.3 OPC Servers, I've got OPCWatchit working from W2K8 to W2K3 direction and callbacks are working (DeltaVAdmin accounts and OPC user accounts must have matching passwords). The problem is I can't repeat it from the other direction, 'access denied 70005'!
Both are domains and both have domain OPC user accounts with DV access privileges. UNC works both directions. OPC works to other DV9.3 systems.
My initial thoughts are group policy settings for the new domain, given that W2K8 is more stringent in its security, so what network access settings do I need to enable?
I'm thinking as I write this, I haven't defined a local OPC user on the new application station, so perhaps this might actually be the cause? Is there anything special with server 2008 to establish comms, or is it the same as server 2003 and I'm barking up the wrong tree?
Have you tried communicating from the 2003 server to the 2008 server OPC using the DeltaVAdmin account, or just the OPC user?
Have you checked the DCOMCFG?
I had to do this exact thing once, and resorted to running DeltaV's OPCRemote on the 9.3 application station.. which you shouldn't have to, and shouldn't do. I was de-commissioning the 9.3 side and didn't need the DeltaV application station, or DV OPC functionality on that server, I just needed the existing licensed Mirror to push data to the new 2008 server.
And you may be on to something with the local account....
Good luck,
Travis
In reply to Travis Neale:
You say you have OPC users as domain accounts. With Server 2008 across domains, I have had to establish reciprocal domain trusts in order to make this work, especially when one or more of the OPC servers are also domain controllers. When establishing the trusts, I've discovered that your OPC server must always be able to find the local domain controller, and the domain controllers must always be able to find each other.
In reply to Youssef.El-Bahtimy:
I would suggest you set up local user accounts on each server for the OPC authentication, set them with the same name and password. You then shouldn't need to set up the trusts. Make sure you create the DeltaV account to be valid for the local Windows Account.
Andre Dicaire
In reply to Andre Dicaire:
Another consideration, under whose authority are you opening OPCWatchit? If you are not launching OPCWatchit as DeltaVAdmin, the OPC user, or an account that exists with same password on both systems, you will be rejected. Many times, when trying to setup service-based OPC clients, developers will configure their service with the right logon; however they will test using an interactive client, negelecting to launch it under the right credentials.
In reply to AdrianOffield:
Great news. I hate to ask rudimentary questions, but I encounter a range of expertise in professionals I work with.
Regarding Xi, (.NET), sure we have a server to access that will eleviate dcom issues, but who has written clients? Matrikon Datamanager , Kepware Linkmaster, and OPC Mirror are not UA/.NET compatible, yet.
I posed this question to the forum a while back...see the following:
community.emerson.com/.../2269.aspx