General troubleshooting

The first step in troubleshooting is to determine whether the PI Web API service or the client application is responsible for the problem. One effective way to do this is to emulate the failing request in a basic HTTP/REST client, such as the Postman REST client for Chrome. It can also be helpful to view the raw request and response data using the browser’s developer console or a traffic inspector like Fiddler. These tools remove much of the browser- and client application-specific configuration that can affect the service’s behavior.

After the source of problem is determined to be the service, additional information may be available in the service application’s logs. For more information, see Log collections.