1/8/2025 3:34 PM | |
Joined: 12/9/2024 Last visit: 8/12/2025 Posts: 6 Rating:
|
I'm having this issue on a 840dsl with an IPC. Been running around for a solution. Any more info needed? Win10, OPC UA licensed... just giving "FindServers_CB: bad status (0x80050000) JAN UPDATE: Working with technical support. Have tried various troubleshooting methods like resetting OPC UA server settings to default, disabling dhcp in systems network and confirming that a static ip is used for both the systems and company network, and have sent in screenshots of config for a fresh set of eyes to identify potential errors/differences from the commissioning manual. Nothing has worked yet. FEB UPDATE: Siemens came to site. The following all failed to resolve the issue: 1. All troubleshooting recommendations from the OPC UA commissioning manual. 2. Tried reconfiguring firewall port forwarding rules. 3. Activating OPC UA server from HMI embedded. 4. Modifying basesys.ini for HMI firewall rule (dialog was not available for this setting in Operate) 5. Changing OPC UA service on IPC to automatic trigger instead of manually triggered service. Will provide more updates to the saga. We hypothesize a compatibility issue between OPC UA server version 3.00.02.03 and pcu version 4.08.06.04. MAR 5 UPDATE: Siemens came back to site. We finally removed the error; however, I still need to test to discover the actual solution so not marking as answer. What we did to resolve this: 1. Create backups of the IPC with Ghost. 2. Create backups of the NCU. 3. Create backups of the CF card. 4. Install latest version of OPC UA server (I think 3.04, will update with accurate version later) for pcu version 4.08. 5. After successful installation, the error persisted. We did three things, and the error disappeared afterward. Something here is the solution in combination with the server version upgrade: A. New feature that was added with the version upgrade was a button that is referenced in the troubleshooting manual that says, "Reset to factory defaults/settings". We toggled this. B. Renewal of the active certificate for additional 5 years. C. Trusted all the rejected certificates. Even though there were none listed in this menu. After the IPC restart, the error status was gone. Had to change the password and restart one last time and we were finally connected. ------------------------------------------------------------------------------------------ |
Last edited by: Moderator_Lan at: 01/08/2025 22:00:36New subject after splitting Last edited by: AutoGen_4288445 at: 01/22/2025 19:02:17Last edited by: AutoGen_4288445 at: 01/22/2025 19:17:58Last edited by: AutoGen_4288445 at: 02/26/2025 21:27:14Last edited by: AutoGen_4288445 at: 03/05/2025 17:19:30 |
|
This contribution was helpful to
1 thankful Users |
Follow us on