Error codes and troubleshooting
- Last UpdatedMar 04, 2025
- 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 data services. 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 IdentityProviderURL is stated correctly in the config file. |
|
Status 404 Not Found |
Verify that the BaseObject 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/HostName in the config file, make sure the http communication works. |
Check the PI_UFL and the local PI Message logs
The PI_UFL log-file, referenced through the /OUTPUT start-up parameter, starting with debug level one, contains OMF messages on the status of the OMF health channel. For troubleshooting, search for the string pattern OMF.
In addition, all messages generated by the PI_UFL interface instance are also stored in the local PI Message Log. The PI Message Log is the recommended troubleshooting place when the interface runs under the NT Service\PI_UFLn account, because then the /OUTPUT file is not created.