Error codes and troubleshooting
- Last UpdatedNov 05, 2024
- 1 minute read
The Microsoft support site lists statuses and error messages sometimes encountered in configuring applications such as OMF health messaging that are implemented using the https protocol.
Verify the status of configured endpoints
If troubleshooting, it is recommended that you verify the status of the configured end points on the configured servers; that is, PIWebAPI and/or CONNECT. Check their logs and overall health.
The following table provides examples of the most commonly encountered error codes and the steps to take to resolve them.
Most common http error messages and statuses
|
Error / Status |
Solution |
|---|---|
|
Status 401 Unauthorized |
Verify the credentials, verify the TokenEndPoint is stated correctly in the config file. |
|
Status 404 Not Found |
Verify that the EndPoint is stated correctly in the config file. |
|
Status 500 Internal Server Error |
OMF EndPoint related problem. Consider restarting the PI Web API server. Verify the corresponding OMF AF database is in a healthy state. |
|
Error 12007 The Server name cannot be resolved |
Verify the URL/EndPoint in the config file, make sure the http communication works. |
Search the string pattern
For troubleshooting, search for the string pattern OMF.