800xA 6.0.3 Redundant Connectivity Server
Hello,
I have a 800xA 6.0.3 with two redundant connectivity servers, one of them appear as System Stopped (SystemServices.jpg).
The services running on this server are "Undefined".
On Configuration wizard does not appear the "System Administration", "Start Server", "Stop Server" options (ConfigWizard.jpg), on ConfigurationWizardOnRunnin.jpg file is the same picture in a running server.
I tried to connect this server to another system and it appear as connected to a system with no name (see picture "Connectnode.jpg").
I will appreciate your help.
Regards.
I have a 800xA 6.0.3 with two redundant connectivity servers, one of them appear as System Stopped (SystemServices.jpg).
The services running on this server are "Undefined".
On Configuration wizard does not appear the "System Administration", "Start Server", "Stop Server" options (ConfigWizard.jpg), on ConfigurationWizardOnRunnin.jpg file is the same picture in a running server.
I tried to connect this server to another system and it appear as connected to a system with no name (see picture "Connectnode.jpg").
I will appreciate your help.
Regards.
Asked 10 months ago
Voted best answer
4
6.0.3 has been out for many years. What is the version / rollup of ABB 800xA Base 6.0.3-0? RU1 to RU6 is available.
Click "Show updates" to see the rollup info, or read the build number to give us explicit version information.
What happens when you click the Connect Node button at the Node Definition aspect of the problematic server in the Node Administration Structure from Plant Explorer of a functional server?
Typical problems:
- RNRP is not configured properly
(review the RNRP Monitor or RNRP Network Status tools, all remote 800xa client and server nodes must appear) - hosts file is containing offending information (can be refreshed from the RNRP Wizard)
- Windows Workgroup / Domain membership is corrupted
(try reading a remote share using DIR \\remotenode\C$ - it should work unless disabled) - Service Account is not successfully applied (re-run System Software User Settings from the classic Configuration Wizard)
- Network issues (e.g. incomplete change of IP-address)
Juggling an installed node between equivalent/"compatible systems" may have been possible in earlier versions, but is practically impossible to succeed with starting with version 6.0 and the introduction of the Automated System Installer.
Always keep a virgin image of the Windows operating system for each node of a system, ready to be reloaded when you need to "reinstall" a node.
The Replace Node feature of System Installer v6.0 and onwards is a very powerful and highly automated tool; but you must be able wind time back to before you deployed the node into the system. Manual uninstall/clean is not an option. A strict policy of where to keep the system media + subsequently installed rollups, addons is also highly recommended and a key for success with the System Installer.
If you can't sort this out, please submit a support case with your regional ABB Support Center.
Add new comment