What can cause the ABB System Manager Service to be stopped in Win Svr 2016, and System Status icon going RED
We have three 800xA DCS's running. One of the 3 DCS's is due for upgrade so we are configuring a 4th DCS using ver6.1. Some MMS data is is sent between DCS's on the control network. To enable this, on the running 3x DCS's we bridge their CONTROL NETWORKs through a "Gateway" Server with basic Windows Server 2008, which has RNRP installed, no other 800xA software. The Gateway Server has Primary and Secondary Control Network NICs for each DCS. Each DCS has its own different IP-Address range and different VLANs. For redundancy we have two identical Gateway servers running, both connected to all networks at all times. This setup has worked faultlessly for 5+ years and is still working.
Now after we created a new ver6.1 DCS with Server2016, as soon as we connect the new DCS Control Network to the Gateway server (using 2x new NICs) the new DCS ABB System Status ICON turns from Green to Red within a few seconds (System Status Icon in bottom RHS of the monitor next to the Clock). Windows Event log tells us that the the "ABB System Manager Service" in "Windows Services" goes to the STOPPED State, and will not restart. This happens to all nodes in the new DCS. There is no impact on the three older DCS's. To correct it, we have to remove the Control network connections of the new DCS, and then restart every node in that DCS to make its icon go Green again, and the ABB Service Manager returns to the RUNNING state. In Node Administration Structure, all services remain green despite the Status ICON going RED. When the System Status ICON is RED, no new Operator Workplace can be opened or new Plant Explorer Application can be opened on any node. Any Operator Workplace or Plant Explorer Workplace that WAS ALREADY OPEN seems to behave as normal, unaffected by the RED status. Does anyone have any clues why this is happening and how to fix it?
Now after we created a new ver6.1 DCS with Server2016, as soon as we connect the new DCS Control Network to the Gateway server (using 2x new NICs) the new DCS ABB System Status ICON turns from Green to Red within a few seconds (System Status Icon in bottom RHS of the monitor next to the Clock). Windows Event log tells us that the the "ABB System Manager Service" in "Windows Services" goes to the STOPPED State, and will not restart. This happens to all nodes in the new DCS. There is no impact on the three older DCS's. To correct it, we have to remove the Control network connections of the new DCS, and then restart every node in that DCS to make its icon go Green again, and the ABB Service Manager returns to the RUNNING state. In Node Administration Structure, all services remain green despite the Status ICON going RED. When the System Status ICON is RED, no new Operator Workplace can be opened or new Plant Explorer Application can be opened on any node. Any Operator Workplace or Plant Explorer Workplace that WAS ALREADY OPEN seems to behave as normal, unaffected by the RED status. Does anyone have any clues why this is happening and how to fix it?
Asked 1 year ago
Answers
0
Very likely solved in 800xA Base 6.1 Rollup 1. Please see release notes (on ABB Library).
Please contact your ABB support center, or download the rollup from ABB Library (subscription required).
Please contact your ABB support center, or download the rollup from ABB Library (subscription required).
by backdraft
Is it possible this new system was created as upgrade from a backup of another one of the systems?
by Bimal.Gurunand Rank: 3557 on 8/22/2019 1:01:16 AM | Like (0) | Report
Hi. We loaded ver6.1 base and related software from ABB Installation USB HDD as supplied to us by our local ABB. We followed the ver6.1 installation manual. We then took afw's from our existing DCS for all projects (one-by-one) for Control Structure and also for Functional Structure and Workplace Structure. We then imported these into the new DCS. All such (new imports) work 100%, we were able to download code to controllers and go online and also mimics and workplaces work fine. We've done quite a few 800xA upgrades in the past and they all worked fine, so we are quite surprised to encounter THIS fault. Thank you.
Add new comment