Hi,
I am trying to run a test of the Redundant OPC DA Server to see if the OPC client-server connection is working. I am running 3 VMs in a WORKGROUP (Proplus and a redundant APP node (APP001) with OPC DA Server and OPC Mirror enabled). My host machine is a non-deltaV machine and I installed the OPCremote (from DeltaV disk #1).
I followed the BOL and the OPCWatchIt is working from the APP node and/or from the ProplusNode.TCP/IP ping is working between the APP node and host machine.
However, OPCping is not working when i select ROPC.APP001.1 on the localhost (host machine). I get a Connection Fail. HRESULT=80070005. General Access denied error.
Now I did create an "opcuser" account which is both windows and deltav database account. The same user is on the host machine.Also, my DeltaVAdmin password is the same across all machines. DCOM is enabled and setting for DeltaVOPC Server in DCOM Is :
- run application on the following computer (APP001)
I am assuming there is some DCOM permission missing. Any ideas what can be the reason?I also have Matricon OPC Explorer installed but I am assuming that should not be the problem (I am getting the same message when i try to browse through Matrikon)
I appreciate any advice.
Regards,MARKO
Hi Marko,
When you state your host machine is non-deltav, are you refeing to the VM host or the thrid party OPC server host -TPV Host? I'm assuming the latter.
So OPCWatchit works from PRO+ to APP, and vice versa, what about from the TPV host, does OPCWatchit allow you to browse OPC items locally?
In reply to AdrianOffield:
Hi Adrian,
No it is the first. I am trying to run an OPC Client (in this case just OPCWatchit) on the VM host machine.
What do you mean by TPV Host? I am unfamiliar with this.
My OPC Server is the DeltaV APP (Application Station) so I am just trying to set up a client on a non deltav machine.
In reply to marko.dragojevic:
What user are you using on the VMware host (the current logged in user)? If that user doesn't exist both in DeltaV and in Windows on the OPC Server computer then your "interactive" session will get the access denied. DeltaV puts an extra layer of security even on OPC so that the username used in the connection must have a DeltaV account to have read access and be assigned access to the proper areas to have write access.
OK, some more questions in that case!
What VM solution are you running, HyperV, VMware, Virtual PC?
Initally I assumed you had another PC on the same network as your VMs, and this was a third party vendor OPC machine (TPV Host), obviosuly this is not the case.
If I understand your configuration correctly, you've installed OPC Remote on the VM host, and from here OPCPing is not working? What about OPCWatchit (from VM Host) do you get the same 70005 error?
In reply to Scott Thompson:
I am using a "opcuser" account which i have created both in DeltaV (windows and deltaV accout) and on the host machine.
I am running this in VMWare and yes, I am getting the 70005 error when i run OPCwatchit from the host.
OK, so during the install of OPCRemote, you configured the remote OPC server, and used the default password for deltavadmin.
From OPCwatchit can you see a list of OPC servers, if you try to "Change Server" | "Browse"?
Have you tried connecting a UNC path to the APP station from VM Host? Can you access the shares on the APP station?
Adrian,
I found a mistake. My APP001 did not have a windows "opcuser" account password correct. I discovered that when i connected to the UNC path from VM Host. Now, when i put the re-set the password it is working fine. Thanks a lot.
One more question. Does my "opcuser" account under which I am running a client has to be a member of Admininistartors and DeltaVAdmin ?
I appreciate all the help. It is ususlly a simple fix but i was breaking my heasd with dcom and overlooked this :)
On the VM Host side, technically it shouldn't matter as it is the DeltaV end that determiens connectivity, "opcuser" only needs to be a memebr of DeltaV Access (within DeltaV Security). But I seem to have better results making "opcuser" part of DeltaVAdmin group on the VM Host.
Good luck.