Troubleshooting Steps for Web-based Clients

Issue Workaround
The WhereTo screen is displayed when you logout and login to WebAdmin without closing tab or browser. Logout and close the tab or browser and reopen it.
Internet Explorer is not supported for the latest web-based clients. There may be some formatting issues in the text. Use Google Chrome for better viewing experience.
This Site Can ?t be reached issue is encountered.

User should start the GE Operations Hub Httpd Reverse Proxy Service
Unable to login due to some certificate issues. Follow the steps provided under Connecting to External UAA section.
After logging in to web-based clients, the web-based clients are not connected successfully to the Historian server.
  • Ensure that the Enforce Strict Client Authentication and Enforce Strict Collector Authentication options are disabled in the Data Stores Security section in Historian Administrator.
  • Make sure you have given a valid UAA URL while installing the Historian Server.
Clients or users are not created because the required services were not running during the installation of web-based clients.
  • An error message appears when you access web-based clients or Trend Client.
  • The visualization client is not found. The following error message appears: No client with requested id: historian_visualization
  • When you attempt to log in to Historian UAA, a message appears, stating that the credentials are incorrect.
 Use the Provisioning tool, which is installed automatically when you install web-based clients.
  1. Access the following folder: <Installation drive of Historian>\Program Files\GE Digital\Historian Config.
  2. Run the following command: uaa_provisioner_tool.exe "UAA client secret", where UAA client secret is the value you have provided while installing web-based clients.
Note:
  • When you run the Provisioning tool, error messages may appear, stating that creating a client has failed (for example, Creating UAA historian_rest_api client failed). Ignore these messages.
  • We recommend not to modify the provisioning.txt file, which is provided along with the Provisioning tool. It contains the parameters required to run the Provisioning tool.