Troubleshoot

If you are unable to resolve issues with the adapter or need additional guidance, contact AVEVA Technical Support through the Customer Portal.

Check configurations

Incorrect configurations can interrupt data flow and cause errors in values and ranges. Perform the following steps to confirm correct configuration for your adapter.

1. Navigate to Data source and verify the following for each configured data source item below:

   • ConnectString - All properties in the ConnectString are correct. If properties are incorrect, the adapter cannot connect to the data source.

   • UTC - Set to true if the timestamps on the data source are UTC timestamps, or false if the timestamps on the data source are in the same timezone as the adapter. If this is incorrect, the adapter might not read any data at all, depending on the timestamps in the query.

   • DataProvider - The value of this property is SQLServer if the data source is a Microsoft SQL Server, otherwise the value is ODBC. If using ODBC, verify that an appropriate ODBC driver is installed and working properly on the machine your adapter is running on.

   • WindowsUser and WindowsPassword - If the data source supports Windows authentication, make sure these values are correct and that the account has read access to the database.

2. Navigate to Data selection and verify the following for each configured data selection item below:

   • ValueColumn - The column exists in the database table and contains the desired data values.

   • IndexColumn - The column exists in the database table and contains the desired DateTime formatted timestamps.

   • SelectColumn - The column exists in the database table and contains the values specified in the SelectValue property for each of the selection items.

   • SelectValue - The value exists in the SelectColumn in the database and is in the row that contains the data for this selection item.

   • QueryId - The query exists and is correct for the columns specified.

   • ScheduleId - The referenced schedule exists.

     A non-existent referenced schedule uses a default schedule instead.

   • DataFilterId - If configured, the referenced data filter exists.

     A non-existent or incorrect DataFilterId means that data filtering is not active.

3. Navigate to Configure queries and verify that the query is correct and retrieves the desired results.

4. Navigate to Egress endpoints. For each configured endpoint, verify that the Endpoint and authentication properties are correct.

   • For a AVEVA PI Server endpoint, verify UserName and Password.

   • For an CONNECT data services endpoint, verify ClientId and ClientSecret.

Check connectivity

Perform the following steps to verify active connections to the data source and egress endpoints.

5. Start PI Web API and verify that the PI point values are updating or start CONNECT data services and verify that the stream values are updating.

6. If configured, use a health endpoint to determine the status of the adapter.

   For more information, see Health and Diagnostics.

Check logs

Perform the following steps to view the adapter and endpoint logs to isolate issues for resolution.

7. Navigate to the logs directory:

   Windows: %ProgramData%\osisoft\Adapters\RDBMS\Logs

   Linux: /usr/share/osisoft/Adapters/RDBMS/Logs.

8. Optional: Change the log level of the adapter to receive more information and context.

   For more information, see Logging.