Troubleshooting the OPC UA Extractor

Use a yml Lint site to validate your yml file.

It is recommended to run the extractor from the command line rather than as a service if you are facing problems. By running the extractor on the command line, you'll see better error messages, than trying to get them via the windows service log file.

Ensure that the extractor is called config.yml and it is inside the config directory or - if you're passing the config directory, you are using the correct path.

Look at the log file in the logging folder (as configured in the configuration file) for any error messages. If the location of the log file is not specified in the config file, look under C:\Cognite\OPCUAExtractor\logs

Double-check that OPC UA endpoint URL is correct and, if required, the username and password. You may need quotes around username, password, and server name.

Double-check that all references to the dataset and pipeline IDs are correct.

Double-check that the client ID and secret in the on-prem configuration file are correct.

If you start the extractor but the dataset remains empty (no linked timeseries), this may be because the timeseries already existed before the extractor ran successfully and those timeseries are not linked to the dataset. Try one of the following: