Hello everyone.
I'm reaching you with hopes you can help me understand and solve this problem. I will try to explain as detailed as possible the issue, so please bear with me the long long text, and please do ask for any missing information you consider important.
Context:
I'm trying to connect a 3rd party PC to a deltav network in order to perform closed loop control of some other equipment irrelevant to this discussion.
The network configuration is as follows:
A DeltaV pro plus workstation (named LAB_PP) is connected to a operator workstation (named LAB_PWS01) using the DeltaV primary and DeltaV secondary ethernet connections
A third PC (named PC3) outside of the DeltaV network is connected to an ABB FTIR sensor (A.K.A. IR sensor) through a 8-port network switch using an ethernet connection named "FTIR". This sensor has an OPC server to which the PC3 connects and exchanges data (IR spectra)
An ethernet cable coming from LAB_PP or LAB_PWS01 (using the Plant LAN ethernet connection) is connected to the 8 port switch where the IR sensor and PC3 are plugged in, and a new ethernet cable is connected between PC3 and the switch (using an ethernet connection named "Ethernet") to establish the link between PC3 and LAB_PP or LAB_PWS01.
All machines are under the same work group "WORKGROUP"
LAB_PWS01 and LAB_PP run on windows 7 x86, PC3 runs on windows 10 x64; All of the actions mentioned were performed under "Administrator" account for all the machines involved, except if stated otherwise.
Previous steps
On PC3
https://www.isa.org/WorkArea/DownloadAsset.aspx?id=123312
https://www.automation.com/pdf_articles/Troubleshooting_OPC_and_DCOM.pdf
On LAB_PP
Eventually after messing a lot with the configuration, PC3 was able to connect with LAB_PP via OPC remote ping, OPC watchit and OPC expert, and for a very brief moment I was able to read data from some sensors online, but then all of it stopped working and never was able to reconnect. All I get now is a message telling "Failed to get OPC servers".
Many times, I restarted PC3, the LAB_PP, deleted DeltaVAdmin user account on PC3, reinstalled OPC remote on PC3, and kept messing with DCOM config for hours but never was able to get a connection.
Current status:
ProPlus DCOM configuration
I used OPC rescue to gather information; Attempting to connect to OPC.DeltaV.1 OPC server gave the following error
OPC rescue report:Connect tab:OPC Rescue could not establish a proper connection with "DeltaV OPC Server"
OPC server details:- Name: DeltaV OPC Server- ProgID: OPC.DeltaV.1- Clsid (GUID): {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F}
OPC Rescue was unable to connect to DeltaV OPC Server on INQU_LAB_PP (this computer).The error code was "0x80070005".Probable cause: INQU_LAB_PP (this computer) did not permit OPC Rescue (executing under the "Administrator" user account) to establish a connection.
Then OPC rescue lists some steps to fix the issue and says it attemprs to fix them by pressing the rescue button under the repair tab, but I don't want to mess with the pro plus DCOM user permissions at this level.
The OPC rescue reports for LAB_PP and PC3 can be found below. I also can provide the OPC expert logs if needed.
I thank you beforehand for taking the time to read this comprehensive post and I truly hope you can help me.
OPC Rescue Snapshot Report This OPC Snapshot report provides a list of all settings relevant for operation of OPC products on DESKTOP-H750JUT. ============================================================ 1. OPC configuration: 0 critical errors and 6 warnings Configuration warnings OPC configuration warnings may stop OPC applications from connecting. When you activate OPC Rescue, you will receive a detailed report of each warning and automatic repair capabilities. 2. Security audit score: 71% with 9 potential security vulnerabilities Overview: This OPC Security Audit report provides a list any concerns that could compromise the security of industrial information. This report includes the cause of the vulnerability, a description of vulnerability, and suggested action. Security Comment: Your security score is medium. OPC Rescue detected some security measures, but they do not provide adequate protection. Unauthorized personnel can still access (and possibly change) Automation data with relative ease. Check for full details in the "Security Audit" section. Note: The full security audit report contains more information about each of the above vulnerabilities. This information includes the cause, description, and suggested action. Activate this copy of OPC Rescue to receive the rest of this report. 3. General computer information Computer Name: DESKTOP-H750JUT Member of: The workgroup called "WORKGROUP" Interactive user: C.Velazquez Operating System Workstation (Edition: Enterprise) Version 6.2 Build 9200 .0 64-bit operating system Windows was started on 19 March 2019 at 14:22 (30 minutes ago) Miscellaneous settings "Simple File Sharing": Off "Accounts: Administrator account status": Enabled "Accounts: Guest account status": Disabled "Interactive logon: Do not display last user name": Disabled "Network access: Let Everyone permissions apply to anonymous users": Disabled "Network access: Sharing and security model for local accounts": Classic "DCOM: Machine Access Restrictions in SDDL syntax": Not defined "DCOM: Machine Launch Restrictions in SDDL syntax": Not defined Data execution prevention (DEP) Status: OPC Rescue cannot determine DEP settings for Application Exceptions: None 4. Windows firewall OPC Rescue does not support the firewall configuration for yet 5. Computer-wide DCOM settings General tab The settings in this tab are not relevant for OPC Options tab The settings in this tab are not relevant for OPC Default Properties tab Enable Distributed COM on this computer: Checked Enable COM Internet Services on this computer: Unchecked Default Authentication Level: Connect Default Impersonation Level: Identify Provide additional security for reference tracking: Unchecked Default Protocols tab Connection-Oriented TCP/IP (Specific port ranges are not defined) MSDTC tab The settings in this tab are not relevant for OPC COM Security tab Launch and Activation Permissions Edit Limits (computer-wide launch and activation permissions) Name: Everyone local launch allowed local activation allowed Name: APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES local launch allowed local activation allowed Name: APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Administrators (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: DESKTOP-H750JUT\DeltaVAdmin (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Performance Log Users (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Distributed COM Users (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Edit Default (default launch and activation permissions) Name: Everyone local launch allowed Name: NT AUTHORITY\SYSTEM (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Administrators (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: DESKTOP-H750JUT\DeltaVAdmin (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: NT AUTHORITY\INTERACTIVE (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Access Permissions Edit Limits (computer-wide access permissions) Name: Everyone (all permissions allowed) local access allowed remote access allowed Name: APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES local access allowed Name: APPLICATION PACKAGE AUTHORITY\ALL APPLICATION PACKAGES local access allowed Name: DESKTOP-H750JUT\DeltaVAdmin (all permissions allowed) local access allowed remote access allowed Name: BUILTIN\Performance Log Users (all permissions allowed) local access allowed remote access allowed Name: BUILTIN\Distributed COM Users (all permissions allowed) local access allowed remote access allowed Name: ANONYMOUS LOGON local access allowed Edit Default (default access permissions) Name: DESKTOP-H750JUT\DeltaVAdmin (all permissions allowed) local access allowed remote access allowed Name: Everyone local access allowed Name: NT AUTHORITY\SELF (all permissions allowed) local access allowed remote access allowed Name: NT AUTHORITY\SYSTEM local access allowed Name: BUILTIN\Administrators (all permissions allowed) local access allowed remote access allowed 6. OPC client applications installed on this computer OPC Rescue does not have a record of OPC client applications on this computer Inform OPC Rescue about additional OPC client applications Select the Repair tab Click the Secure button Navigate to the OPC Port Selection dialog Click the Add Applications button 7. OPC servers installed on this computer OpcEnum (also known as "Opc ServerList Class") General Tab Application Name: OpcEnum Application ID: {13486D44-4821-11D2-A494-3CB306C10000} Application Type: Local Server Authentication Level: None Local Path: "C:\WINDOWS\SysWOW64\opcenum.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions Name: Everyone (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Access Permissions Name: Everyone (all permissions allowed) local access allowed remote access allowed Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user OPCSniffer Class OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): Matrikon.OPC.Sniffer.1 ProgID (version independent): Matrikon.OPC.Sniffer This OPC server claims to support OPC Data Access Servers Version 1.0 OPC Data Access Servers Version 2.0 OPC Historical Data Access Servers Version 1.0 General Tab Application Name: OPCSniffer Class Application ID: {0FAAE42A-35AF-49d4-B7E5-D4D121F208F1} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: Warning! This registry key does not exist. This could cause OPC connectivity problems. Locations Tab Run application where data is located: Unchecked Run application on this computer: A registry entry for this OPC server is missing, which may cause connectivity problems. Possibly, the OPC server was uninstalled. You may have to reinstall this OPC server, or contact the vendor of this OPC server vendor to ask for the reason this setting is disabled. Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user DeltaV OPC Server OPC server overview Vendor: Emerson ProgID (version dependent): OPC.DeltaV.1 ProgID (version independent): See comment below This OPC server does not have a version independent program identifier (this is not an error) This OPC server claims to support OPC Data Access Servers Version 1.0 OPC Data Access Servers Version 2.0 General Tab Application Name: DeltaV OPC Server Application ID: {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} Application Type: Local Server Authentication Level: Connect Local Path: Warning! This registry key does not exist. This could cause OPC connectivity problems. Locations Tab Run application where data is located: Unchecked Run application on this computer: A registry entry for this OPC server is missing, which may cause connectivity problems. Possibly, the OPC server was uninstalled. You may have to reinstall this OPC server, or contact the vendor of this OPC server vendor to ask for the reason this setting is disabled. Run application on the following computer: INQU_LAB_PP Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user FTSW100 OPC DA Server OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): ABB.Bomem.Data.OPC.3 ProgID (version independent): ABB.Bomem.Data.OPC This OPC server claims to support OPC Data Access Servers Version 2.0 General Tab Application Name: FTSW100 OPC DA Server Application ID: {CA396CF6-7868-490D-BDF6-A9195CE05971} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: C:\Bomem\Enablir\dllreg\FtswOPC.exe Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user DeltaV OPCAE Server OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): DeltaV.OPCEventServer.1 ProgID (version independent): See comment below This OPC server does not have a version independent program identifier (this is not an error) This OPC server claims to support OPC Alarm & Event Servers Version 1.0 General Tab Application Name: DeltaV OPCAE Server Application ID: {DD99BFB8-3571-11D3-848E-00C04F99022F} Application Type: Local Server Authentication Level: Connect Local Path: Warning! This registry key does not exist. This could cause OPC connectivity problems. Locations Tab Run application where data is located: Unchecked Run application on this computer: A registry entry for this OPC server is missing, which may cause connectivity problems. Possibly, the OPC server was uninstalled. You may have to reinstall this OPC server, or contact the vendor of this OPC server vendor to ask for the reason this setting is disabled. Run application on the following computer: INQU_LAB_PP Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user 8. OPC Rescue information User information Name: Your name Company: Your company name Email: Your email address Phone: Your phone number Snapshot date: 19 March 2019 Snapshot time: 2:52:39 PM (SA Western Standard Time) Version 3.6.1303.7 Executable date is 26 November 2013 This copy of OPC Rescue has not been activated Download from www.OpcRescue.com ============================================================ End of OPC Snapshot report
OPC Rescue Snapshot Report This OPC Snapshot report provides a list of all settings relevant for operation of OPC products on INQU_LAB_PP. ============================================================ 1. OPC configuration: 1 critical error and 4 warnings Configuration errors OPC configuration errors stop OPC applications from connecting. When you activate OPC Rescue, you will receive a detailed report of each error and automatic repair capabilities. Configuration warnings OPC configuration warnings may stop OPC applications from connecting. When you activate OPC Rescue, you will receive a detailed report of each warning and automatic repair capabilities. 2. Security audit score: 65% with 9 potential security vulnerabilities Overview: This OPC Security Audit report provides a list any concerns that could compromise the security of industrial information. This report includes the cause of the vulnerability, a description of vulnerability, and suggested action. Security Comment: Your security score is very low. This could compromise Operations because too many people can access (and possibly change) Automation data. Take corrective action immediately. Check for full details in the "Security Audit" section. Note: The full security audit report contains more information about each of the above vulnerabilities. This information includes the cause, description, and suggested action. Activate this copy of OPC Rescue to receive the rest of this report. 3. General computer information Computer Name: INQU_LAB_PP Member of: The workgroup called "WORKGROUP" Interactive user: Administrator Operating System Windows 7 Workstation (Edition: Professional) Version 6.1 Build 7601 Service Pack 1.0 32-bit operating system Windows was started on 19 March 2019 at 10:03 (4 hours and 13 minutes ago) Miscellaneous settings "Simple File Sharing": Off "Accounts: Administrator account status": Enabled "Accounts: Guest account status": Disabled "Interactive logon: Do not display last user name": Disabled "Network access: Let Everyone permissions apply to anonymous users": Disabled "Network access: Sharing and security model for local accounts": Classic "DCOM: Machine Access Restrictions in SDDL syntax": Not defined "DCOM: Machine Launch Restrictions in SDDL syntax": Not defined Data execution prevention (DEP) Status: DEP is on for essential Windows programs and services only Application Exceptions: None 4. Windows firewall Profile: Public is active Firewall Status: Disabled 5. Computer-wide DCOM settings General tab The settings in this tab are not relevant for OPC Options tab The settings in this tab are not relevant for OPC Default Properties tab Enable Distributed COM on this computer: Checked Enable COM Internet Services on this computer: Unchecked Default Authentication Level: Connect Default Impersonation Level: Identify Provide additional security for reference tracking: Unchecked Default Protocols tab Connection-Oriented TCP/IP (Specific port ranges are not defined) MSDTC tab The settings in this tab are not relevant for OPC COM Security tab Launch and Activation Permissions Edit Limits (computer-wide launch and activation permissions) Name: Everyone (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: INQU_LAB_PP\DeltaV (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: INQU_LAB_PP\DVPEHAdmin (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: INQU_LAB_PP\DVPEHUser (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: INQU_LAB_PP\AMSDeviceManager (corruption warning!) This access control entry is corrupt. OPC Rescue will automatically repair this error when you click the Rescue button in the Repair tab. Name: BUILTIN\Administrators (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Performance Log Users (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Distributed COM Users (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Edit Default (default launch and activation permissions) Name: NT AUTHORITY\SYSTEM (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: BUILTIN\Administrators (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: Everyone (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Name: NT AUTHORITY\INTERACTIVE (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Access Permissions Edit Limits (computer-wide access permissions) Name: Everyone (all permissions allowed) local access allowed remote access allowed Name: INQU_LAB_PP\DeltaV (all permissions allowed) local access allowed remote access allowed Name: INQU_LAB_PP\DVPEHAdmin (all permissions allowed) local access allowed remote access allowed Name: INQU_LAB_PP\DVPEHUser (all permissions allowed) local access allowed remote access allowed Name: INQU_LAB_PP\AMSDeviceManager (corruption warning!) This access control entry is corrupt. OPC Rescue will automatically repair this error when you click the Rescue button in the Repair tab. Name: BUILTIN\Performance Log Users (all permissions allowed) local access allowed remote access allowed Name: BUILTIN\Distributed COM Users (all permissions allowed) local access allowed remote access allowed Name: ANONYMOUS LOGON (all permissions allowed) local access allowed remote access allowed Edit Default (default access permissions) Name: Everyone (all permissions allowed) local access allowed remote access allowed Name: NT AUTHORITY\SELF (all permissions allowed) local access allowed remote access allowed Name: NT AUTHORITY\SYSTEM local access allowed Name: BUILTIN\Administrators (all permissions allowed) local access allowed remote access allowed 6. OPC client applications installed on this computer OPC Rescue does not have a record of OPC client applications on this computer Inform OPC Rescue about additional OPC client applications Select the Repair tab Click the Secure button Navigate to the OPC Port Selection dialog Click the Add Applications button 7. OPC servers installed on this computer OpcEnum (also known as "Opc ServerList Class") General Tab Application Name: OpcEnum Application ID: {13486D44-4821-11D2-A494-3CB306C10000} Application Type: Local Service Authentication Level: None Service Name: OpcEnum (which is set to Automatic) Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions Name: Everyone (all permissions allowed) local launch allowed remote launch allowed local activation allowed remote activation allowed Access Permissions Name: Everyone (all permissions allowed) local access allowed remote access allowed Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The system account (services only) OPC Data Access 2.0 Server for iFix OPC server overview Vendor: Intellution Inc. ProgID (version dependent): Intellution.OPCiFIX.1 ProgID (version independent): Intellution.OPCiFIX This OPC server claims to support OPC Data Access Servers Version 2.0 General Tab Application Name: OPC20iFIX Application ID: {3C570292-EB8E-11D4-83A4-00105A984CBD} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: "C:\DELTAV\IFIX\OPC20iFIX.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The launching user AMS OPC Server OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): AMS.OPCServer.1 ProgID (version independent): AMS.OPCServer This OPC server claims to support OPC Data Access Servers Version 1.0 OPC Data Access Servers Version 2.0 General Tab Application Name: AMS OPC Server Application ID: {4C853380-83C4-11d2-9C40-006097BD9545} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: "C:\AMS\bin\Amsopc.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions Name: Everyone Access Permissions Name: Everyone Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: This user (see below) The user account is "AmsServiceUser" DeltaV OPC HDA Server OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): DeltaV.OPCHDAsvr.1 ProgID (version independent): DeltaV.OPCHDAsvr This OPC server claims to support OPC Historical Data Access Servers Version 1.0 General Tab Application Name: DeltaV OPC HDA Server Application ID: {8351A72D-A1D8-4C9D-B390-97DB17FCD6E6} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: "C:\DeltaV\bin\DOPCHDA1.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions This application uses the "default launch and activation permissions" as listed above, under: "Default launch and activation permissions" Access Permissions This application uses the "default access permissions" as listed above, under: "Default access permissions" Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: The interactive user DeltaV OPC Server OPC server overview Vendor: Fisher-Rosemount Systems Inc. ProgID (version dependent): OPC.DeltaV.1 ProgID (version independent): See comment below This OPC server does not have a version independent program identifier (this is not an error) This OPC server claims to support OPC Data Access Servers Version 1.0 OPC Data Access Servers Version 2.0 General Tab Application Name: FrsOpcDv Application ID: {C3B72AB1-6B33-11d0-9007-0020AFB6CF9F} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: "C:\DeltaV\bin\FrsOpcDv.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions Name: NT AUTHORITY\SYSTEM local activation allowed remote activation allowed Name: INQU_LAB_PP\DeltaV local activation allowed remote activation allowed Name: INQU_LAB_PP\DeltaV Admins local activation allowed remote activation allowed Access Permissions Name: NT AUTHORITY\SYSTEM Name: INQU_LAB_PP\DeltaV Name: INQU_LAB_PP\DeltaV Admins Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: This user (see below) The user account is "DeltaVAdmin" DeltaV OPC Alarms and Events Server OPC server overview Vendor: Vendor did not provide this information ProgID (version dependent): DeltaV.OPCEventServer.1 ProgID (version independent): DeltaV.OPCEventServer This OPC server claims to support OPC Alarm & Event Servers Version 1.0 General Tab Application Name: DvOPCAE Application ID: {DD99BFB8-3571-11D3-848E-00C04F99022F} Application Type: Local Server Authentication Level: Default (which is set to 'Connect') Local Path: "C:\DeltaV\bin\DvOPCAE.exe" Locations Tab Run application where data is located: Unchecked Run application on this computer: Checked Run application on the following computer: Unchecked Security Tab Launch and Activation Permissions Name: NT AUTHORITY\SYSTEM local activation allowed remote activation allowed Name: INQU_LAB_PP\DeltaV local activation allowed remote activation allowed Name: INQU_LAB_PP\DeltaV Admins local activation allowed remote activation allowed Access Permissions Name: NT AUTHORITY\SYSTEM Name: INQU_LAB_PP\DeltaV Name: INQU_LAB_PP\DeltaV Admins Endpoints tab This application uses the default system protocols. See above in "DCOM Default Protocols" Identity Tab Identity is set to: This user (see below) The user account is "DeltaVAdmin" 8. OPC Rescue information User information Name: Your name Company: Your company name Email: Your email address Phone: Your phone number Snapshot date: 19 March 2019 Snapshot time: 2:16:32 PM (SA Western Standard Time) Version 3.6.1303.7 Executable date is 26 November 2013 This copy of OPC Rescue has not been activated Download from www.OpcRescue.com ============================================================ End of OPC Snapshot report
In reply to harnettw:
Bob Lenich
In reply to Bob Lenich:
In reply to Brian Hrankowsky:
Hello Brian I think you might have referred to me instead of harnettw when asking about the two network cables. The reason for that is the connection from PC3 to the sensor.: I use a network adapter in PC3 to connect to the FTIR sensor and the other adapter to (try to) communicate with deltav. The overall goal is to close the moisture control loop using the FTIR and deltav, and for that is needed the PC3 in order to predict the %H2O with simca online. I hope this answers your question
Edit:
I forgot to comment about the authenitcation levels: According to deltav help, i understand the configuration should be left at "defalult" or "connect" in the DCOM config. Right now I can't remember exactly where i read that but i'm certain it was the recommended set up. Nevertheless, I'll try to change it to ses what happens.
Also, the 8 port switch is simply for convenience and cable management reasons.
In reply to Julian Navas:
In reply to Youssef.El-Bahtimy:
Julian, I'm thinking about having momentary connection, which you stated. It's as if you had connection and then it was blocked by some security or network software. Switches often use Spanning Tree Protocol to prevent duplicate IP addresses. Windows 10 may also utilizes some security process that potentially catches communication it deems inappropriate. I like Brian Hrankowsky am targeting the use of two network cables going to the same switch. Have you tried using two different switches or separating the two ports with a VLAN? I agree this shouldn't be necessary, but given you had a connection and lost it, something is up.
Another idea, I encountered is connecting a non-DeltaV machine to a DeltaV machine. Let me explain what I mean by an instance. I installed AMS Client on a non-DeltaV machine. I connected it to the AMS Server Plus (the ProPlus on the DeltaV domain) through the Plant LAN. I could not see DeltaV IO data (HART IO) from the AMS CLient machine. I found out that the non-DeltaV machine needed to be on a domain and a domain trust set up between the two before communications could work. I elected to make the non-DeltaV machine a maintenance station and join it to the DeltaV domain, issue solved. So here is how I see it apply here. Your non-DeltaV machine Win 10 is talking to a DeltaV machine Win 7, already concerning, so DeltaV may not like the relationship, i.e. not "trusted". An OPC Tunneller may overcome this issue. But I would see if installing the PC3 software on your LAB_PWS01 workstation and having it connect to the ABB FTIR sensor "magically" fixes the problem.
Sal Salamone
Andre Dicaire