Troubleshoot OMI web client connection issues

If you have a problem starting or working with the OMI web client, following the steps below may help you find and resolve the issue.

1. Check Known Issues in the OMI web client. If your symptom is listed there, follow the recommended workaround.

2. On the System Management Server (SMS) host, start the Configurator and make sure the settings for the web client are correct:

   1. Under Common Platform, make sure there is a green checkmark next to System Management Server. If there isn't, select System Management Server and select the option to make this host the SMS.

   2. Select System Management Server, then select Advanced.

   3. Select the Ports tab, and make sure the HTTPS Port is set to 443. Select OK.

   4. Under AVEVA System Platform, there should be a green checkmark next to Identity Manager Registration. If there isn't:

      1. Select Identity Manager Registration.

      2. Select Configure.

      3. Select Close.

      Note: If the SMS was not already defined, after performing the steps above, go to the other nodes that have System Platform installed and use the Configurator to connect them to the SMS.

3. On the device that is having the problem, clear the browser cache (select the option to clear the cache for all time). Then close and re-open the browser and try to open the web client again.

4. On the platform that hosts the WebViewEngine, make sure that all five services that are supposed to be deployed and started when the WebViewEngine is deployed are running. These services are:

   • ArchestrA.Web.DataConnectivitySvc.exe

   • vcp.services.onprem.contentserver.exe

   • vcp.services.onprem.dataaccess.exe

   • vcp.services.onprem.frontdoor.exe

   • vcp.services.onprem..webserver.exe

   You can check for these services either on the Details tab of the Windows Task Manager or from the IDE by selecting Galaxy > Configure > System > Services. When you expand the tree view nodes on the Configure Services dialog box, each service name should show a green box to indicate that it is deployed and running. In this sample, the Galaxy name is MainPlant:

   

5. If the services are not all deployed, undeploy and redeploy the WebViewEngine. Then, repeat step 4 to confirm that the services have started.

If you cannot undeploy an OMI ViewApp

If you are unable to undeploy a ViewApp that is assigned to the WebViewEngine, follow these steps to fix the issue:

6. Follow the instructions in step 4, above, to see if the WebViewEngine services are deployed and running. If they are, go to the next step. If they aren't:

   1. If it isn't already open, open the Configure Services dialog box from the IDE by selecting Galaxy > Configure > System > Services.

   2. Expand the tree view nodes to see the service names, as shown in the image above.

   3. Undeploy and redeploy the five WebViewEngine services. (The ones that are expanded in the image.)

7. Check to see if you can now undeploy the ViewApp.

8. If you still can't undeploy the ViewApp, restart the node hosting the WebViewEngine.

9. If you still cannot undeploy a ViewApp, please contact AVEVA Global Customer Support.