PI message logs

The location of the message log depends upon the platform on which the interface is running.

Messages are written to the log file at the following times:

• When the interface starts, many informational messages are written to the log. These messages include the version of the interface, the version of UniInt, the command-line parameters used, and the number of points.

• As the interface loads points, messages are sent to the log if there are any problems with the configuration of the points.

• If the UniInt /dbUniInt parameter is found in the command-line, then various informational messages are written to the log file.

• If the interface detects a time differential, or clock drift, between itself and either the source or destination server, a message is sent to the log to inform you to check the clock. If the clock is incorrect, you must adjust the time accordingly.

  When the clock drift is greater than 10 minutes but less than 15 minutes, the following message is sent:

  WARNING: Time offset greater than 10 minutes detected!!
  Please check the time on <machine_ip/name>

  When the clock drift is greater than 15 minutes, the following message is sent:

  WARNING: Time offset greater than 15 minutes detected!!
  This could result in incorrect timestamps in the destination data archive. Please check the time on <machine_ip/name>

For more information about logs for interfaces running on Windows, see REF UniIntMessageLogging \* MERGEFORMAT UniInt Interface Message Logging for UniInt 4.5.0.x and later Interfaces or on the AVEVA technical support web site: KB00401 - How to read new UniInt 4.5.0.x and later Interface message logs (now in PI Message Log, not PIPC.log).