SCC History installation - Clients "needs redeploy" but nothing will be deployed
I'm currently installing 800xA History on an existing 800xA 6.0.3 System.
In SCC I have added the system function 800xA History.
Then I deployed only EWS (Engineering Client) to see if it impacts the running system. Unfortunately it only deployed history function on EWS and automatically on ASCS01.
Then I added node function "Non Redundant History Server" to HS0001 and deployed.
Now EWS, ASCS01 and HS0001 showing "Deployed" state, all other clients "needs redeploy"
Also the system function "800xA History" says "needs redeploy" but nothing will be deployed.
Executing "Deploy System" will open the window with nothing to deploy. When hitting deploy it says "The installation completed successfully" but my clients still remain "needs redeploy"
Why do the clients needs deploy when installing History, in my opinion there is nothing on the clients regarding history?
How can I retrigger correct deploy on all the clients? For future upgrades I need a proper deployed system.
In SCC I have added the system function 800xA History.
Then I deployed only EWS (Engineering Client) to see if it impacts the running system. Unfortunately it only deployed history function on EWS and automatically on ASCS01.
Then I added node function "Non Redundant History Server" to HS0001 and deployed.
Now EWS, ASCS01 and HS0001 showing "Deployed" state, all other clients "needs redeploy"
Also the system function "800xA History" says "needs redeploy" but nothing will be deployed.
Executing "Deploy System" will open the window with nothing to deploy. When hitting deploy it says "The installation completed successfully" but my clients still remain "needs redeploy"
Why do the clients needs deploy when installing History, in my opinion there is nothing on the clients regarding history?
How can I retrigger correct deploy on all the clients? For future upgrades I need a proper deployed system.
Asked 8 months ago
Answers
This question has not yet been answered.
by Stefan Stromqvist
I'm not sure a stepwise deploy is possible (did you use "Exclude Node" to perform the individual steps)?
If I were you I would load the disk images you took before deploy and start over with 800xA History, all nodes in one sweep.
Your regional ABB support center should be able to assist you, please attach the diagnostic logs you can collect in the SCC > Configure System task.
by Jan.Sommer Rank: 1193 on 11/13/2020 1:16:45 AM | Like (0) | Report
I actually retried with deploy the whole system including history server and data collector.
Unfortunately again something went wrong. Errors during configuring of service provider. I tried to manually resolve, ok there is anyhow no way back in SCC at this point.
under C:\Program Files (x86)\ABB 800xA\Base\bin as a 800xAservice
AfwConfigure.exe -AddProvider -serviceId "{90A2781C-E57F-4A4A-B778-8C278D1063BF}" -name "HSEventCol_ASCS01" -group "HistoryEventCollector"
AfwConfigure.exe -AddProvider -serviceId "{93262E4E-C4B1-43F8-8AFF-91775682E9E5}" -name "HSEventServ_ASCS01" -group "HistoryEventServer"
AfwConfigure.exe -AddProvider -serviceId "{4ECE09D4-F6ED-4D77-B1C0-58AB47183341}" -name "HSSyncServ_ASCS01" -group "HistorySyncService"
Is it possible that the problem is that 800xaService and 800xaInstaller must be peresent as a local user (not domain user)?
Next problem is that it is a runng onine system and i can not jump backwards to backups that easily.
My suggestion is to manually try to reinstall the 800xA service providers, but how?
by Stefan Stromqvist
Please have a support case filed to obtain professional support from ABB.
The creation of service providers should be an easily accomplished manual task since it in practice means, do as you have done in the past (pre 6.0) when creating a service group and provider (Create New Object, select name, select node, fill out Special Configuration tab if required).
One of the things to keep in mind with the System Installer is that there is practically no way back out of a failed deploy (unless you can accept and carry out a manual deletion and survive without the feature you just had an issue with adding).
Removal of software with the intention of putting it back in the next moment is not tested. In fact, no removal is tested.
"Backup often, backup early" is a strong recommendation and enables you to make new attempts on "virgin" computers.
Add new comment