OSI PI Collector Troubleshooting
Tracing Operational Issues with OSI PI Collector Log Files
The OSI PI Collector generates logs during initialization, configuration, and general operation. These can be found in the general logging folder ([Historian Data folder]\LogFiles). Log files for the OSI PI Collector begin with PICollector and have a sequence number for each collector restart.
- Configuration of the collector.
- Initialization and connection to the OSI PI server.
- Addition and removal of tags.
- Reconnection and recovery of data.
OSI PI tags cannot be browsed, collector logs indicate SDK connection issues
The OSI PI server used must be an entry in the About-PI SDK utility. If there is an issue with collecting tag information and/or enumeration information, please confirm that the OSI PI server that is set in the collector configuration has an entry in the About PI-SDK, and that it is accessible from the About PI-SDK utility.
OSI PI Collector overrun problems - missing blocks of values, or is missing values
If the OSI PI Collector is unable to maintain updates from the OSI PI archiver and therefore is missing values, you may experience overrun problems. An overrun occurs when the data source is changing tag values faster than the collector collecting values, which causes it to consistently remain behind the archiver updates. If this is the case then the collector is running against the hardware and/or network limits and you may consider partitioning the tags into two or more sets, each with independent collectors.
Startup issue when data source is Snapshot
Historian OSI PI Collector fails to start as a service when you enter Snapshot as the Data Source in the Configuration tab of the collector.
- Open command prompt as Administrator.
- Navigate to the location where Historian installed.
- Navigate to the path
Program Files (x86)\GE Digital\Historian OSI Pi Collector\Server - Enter the following command:
ihPiCollector.exe noservice
The Collector starts from the CLI interface.