• Not Answered

3rd Party OPC Server, connecting from Application Station via OPC Mirror

I have all the relevant user accounts created (CPX_OPC which is used for running OPCMirror on DV, CIMUSER as the 3rd party OPC Server runas account)  in both the remote OPC Server (Cimplicity and a workgroup) and DV app station (domain), but I can't get the unsolicited callbacks to work, I get an advise fail, and event logs (at the DV application station) lists a failed logon (cimuser).

UNC works both ways and I can read/browse OPC points from the Cimplicity OPC server using OPCWatchit, but I do receive an advise fail error.  OPC Mirror reports the pipe as active, but monitoring the pipe items gives stale data.

Obviously this is related to the failing logon from the remote OPC server, preventing the OPC group advise from working.

SID and anonymous account translation is enabled in group policy, but still I get failed logons.

What am I missingTongue Tied

2 Replies

  • Adrian, is the CIMUSER account on the DeltaV app station a local or domain account?  I would actually try setting up BOTH a local and domain CIMUSER on the DV App station with matching passwords. Use OPCWatchit to test whether local\CIMUSER and domain\CIMUSER on DV App station gets the callbacks.

    Thats the first leg of the journey.

    Next, through OPCWatchit, see if local\CIMUSER and domain\CIMUSER can write to DeltaV OPC server tags. If you hav set up CIMUSER in DeltaV Usermanager as a domain account, only domain\CIMUSER will suceed.  IF you set up CIMUSER as a local account in User Manager (no domain or app station as domain) then only local\CIMUSER will succeed.  I have had more luck with the former, but bottom line was both the local and domain accounts needed to exist.

    Thats the second leg of the journey.

    Next, I would set up OPC Mirror to run as domain\CIMUSER.   You can also try local\CIMUSER.  

  • It was the wrong password configured in the local OPC user account!
     
    OPC callbacks resolved, I now have an issue with Cimplicty OPC server providing stale data with invalid timestamps.  Anyone had dealings with Cimplicty?
     
    From: Youssef.El-Bahtimy [mailto:bounce-YoussefEl-Bahtimy@community.emerson.com]
    Sent: Thursday, August 28, 2014 4:42 PM
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] 3rd Party OPC Server, connecting from Application Station via OPC Mirror
     

    Adrian, is the CIMUSER account on the DeltaV app station a local or domain account?  I would actually try setting up BOTH a local and domain CIMUSER on the DV App station with matching passwords. Use OPCWatchit to test whether local\CIMUSER and domain\CIMUSER on DV App station gets the callbacks.

    Thats the first leg of the journey.

    Next, through OPCWatchit, see if local\CIMUSER and domain\CIMUSER can write to DeltaV OPC server tags. If you hav set up CIMUSER in DeltaV Usermanager as a domain account, only domain\CIMUSER will suceed.  IF you set up CIMUSER as a local account in User Manager (no domain or app station as domain) then only local\CIMUSER will succeed.  I have had more luck with the latter, but bottom line was both the local and domain accounts needed to exist.

    Thats the second leg of the journey.

    Next, I would set up OPC Mirror to run as domain\CIMUSER.   You can also try local\CIMUSER.