Rockwell Automation FactoryTalk Historian SE 3.0 UniInt Interface User Guide - Manual (Page 76)

Interface Disconnected Startup
70
Troubleshooting
Interface Operation
Problem:
On restart, the interface is not loading all Historian Points with a fully configured cache file.
Solution:
1. Make sure the cache files have been previously configured during the initial interface
start using the disconnected startup configuration. This can be verified by reviewing
Historian point value history on the Historian Server using the appropriate Historian
client, such as DataLink and by reviewing the pipc.log file that contains the initial start
of the interface configured for disconnected startup. The Historian Points for the
interface should have been receiving data during the initial cache build process. The user
should see messages containing cache file information as described in the ―Messages‖
section of this document. If cache synching is enabled, there will be a message stating
the cache file synchronization is complete. There should also be a message containing
the number of points matching the point source for the interface. If no modifications to
the Historian Server database for Historian Points matching the interface point source
have been made since the cache files have been built, the number of points for the
interface starting from the cache file should be identical.
2. Restart the interface.
3. Confirm the number of points matching the point source is identical to the number of
points matching the point source on the Historian Server.
4. If the number of points loaded by the interface does not match the number of points on
the Historian Server, attempt additional restart. If a restart is not successful, rename or
delete the point caching files to allow the interface to create new files on the next restart.
5. Contact Rockwell Automation technical support if none of the above procedures results
in a successful disconnected startup configuration.
Deleting Cache Files
Rockwell Automation recommends renaming or moving the cache files to a backup
directory. Delete cache files only if absolutely necessary.
To delete the cache files created by the interface. The following procedure is recommended.
1. Stop the interface.
2. Verify the location and names of the cache files belonging to the interface. There are two
files: a point cache file and digital cache file. The location and exact name of these files
will be listed in the pipc.log file for the interface instance.