Problems after 800xA 6.0 RU1 TC3
Had a good system 6.0.0-0, just a few days ago installed the certified PM865 HI firmware via AC800M HI Extension maintenance.
Wanted to get rid of a problem with date formatting which is solved by RU1 TC3, but after installing and restarting and lastly using System Extension Maintenance the system behaved strange (not sure exactly when the behaviour started though):
The system is not automatically starting anymore, I have to start the servers manually (afwConfigWizard) and then start the system, then it seemingly works ok, but notification tray indicates a disabled system (workplaces looks like working ok though, cannot verify due to lack of physical controllers so OPC server is of course not happy).
Another restart of the PC's does not help, manual start of servers and system is still neccessary, system tray indicates disabled and the most peculiar of all: System Configuration Console/System Setup shows 2 clickable Configure System controls, earlier there was only one.
Like I said, I don't know for sure if TC3 is the source of problem, but all was fine before (I just didn't restart the system just prior to TC3 so I do not know if there could be something else potensially leading to this problem.
Possibly I installed the TC3 on the secondary server with a login without admin rights, but the system didn't complain at all (some way to re-do this step ?).
(Mention this because a log entry indicates this, but I believe it was done with 800xAInstaller (admin group).
Furthermore, I do not have access to physical controllers currently and haven't tried simulation with softcontrollers yest (but I didn't have physical controllers prior to the TC3 neither, so I assume this has nothing to do with it).
Any hint ?
Unless it has changed in 6.0, the difference between an automatically starting system and one that need manual start is the startup mode of the ABB Service Manager Service (a Windows Service, i.e. you can use services.msc tool to check). For automatic start, it should be set to "AUTOMATIC". If set to MANUAL, the system will need a "kick" (in each machine) to startup.
A few months ago I was discussing with R&D about the benefit of setting a system to MANUAL during an installation/upgrade phase to prevent a reboot (expected or unexpected) starting up the system midway in the upgrade. Maybe it was set to MANUAL by installer, but never restored back to AUTOMATIC for some reason, I can not tell.
Two icons sounds like a bug someone mentioned to me.
I believe you should file a regular support case to get this sorted out...