Setup S+ Engineering 2.2 \Operation V2.2 in same node
I hope you are fine .
I have install S+ operation V3.2 and S+ Engineering V2.2 in the same workstation according to ABB installation manual .
the problem is S+ operation not open at all as still coming the message "Waiting for data processor startup (0%)
the system Icon (SDK status viewer) show no cconnection open with non healthy colors (yellow and black) , in server list there is no server name , and messgae says can't connect to S+ operation
any advice what to do ?
Did you a first Full Deploy?
The service scheduler database must be loaded on the Operations node. I have done this installation without problem. You have to do an import all the first time.
Please check the license configuration in the node database too.
If you did the first full deploy, can you check the ApmsScheduler log.
Let ne know the results.
If i understand correctly, the deployment is getting skipped due to the database information is not available as part of S+ Operations database.
Hope you have checked that the Composer Operations service (in services.msc) is configured with the logged in windows user. The APMSNETSERVER.exe from bin folder is triggered manually as per the post installation steps in installation user manual. S+ Engineering server name in registry (regedit) under Local machine\...\ABB Symphony Plus\...\clientServer is configured manually.
So follow the below steps:
1. Hopefully, PC might have restarted and PGPpostinstallation ran successfully. Just to ensure you can run\trigger this exe from S+ Operations\..\ bin folder. (You can use win search or refer to manual). Just Double click with administrator privileged user account or right click and run as administrator or login into Windows Built in Administrator account and double click it..
2. Ensure you have updated the license information under every item in node database under License tab in Operations Engineering.
3. Ensure Test connection is working fine by right clicking on the node from Node List in Operations Engineering.
4. Share the deploy log with error details to be more precise.