User Control - Archive Audit Logs – GGP Systems Help Center

📝 Overview

Tools are available from User Control Maintenance to view and manage GGP activity log files. While these logs are typically not needed daily, they may be required by GGP Support for troubleshooting and auditing purposes.

📂 Location of Audit Logs

Certain files used to control and audit user access are located in the LOCK folder.

For details on the specific log filenames, see the Filenames documentation.
For information on application log files and deleting old files, see Log Files.

🧹 Archiving the Audit Logs

Over time, audit log files can grow large and may negatively impact performance, especially slowing record locking/unlocking operations in GGP. To maintain optimal performance, Corporate Administrators should perform regular housekeeping by archiving these logs.

⚠️ Important Notes Before Archiving

Make sure no other users are logged into any GGP application.
Close all GGP applications before starting the archive process.
If you encounter errors indicating files are in use, check Windows Computer Management > System Tools > Shared Folders to clear any open sessions or files.

📈 Managing Logfile Size Limit

When the GGPLOCKS.LOG file reaches a maximum defined size, a popup message will alert you when you next click the Users button in the Applications Launcher, indicating that the log requires archiving.

This maximum file size limit can be customized by adding the following key to the [General] section of the LOCK.INI file:

[General]
LogfileArchiveSize=21.5

The above example sets the limit to 21.5 MB. Adjust as needed for your environment.

📂 How Archiving Works

Selecting Tools | Archive Audit Logs performs the following actions:

Archives the Overlay Record Locking Log (\Lock\GGPLOCKS.LOG)
Archives the User Account Log (\Lock\Log.csv)

Both files are moved to a separate folder:
\Lock\Audit File Archive

This process appends data to existing files in the archive folder and truncates the original logs back to zero length, preventing performance degradation in GGP.

⚙️ Optional Corporate Action

If network performance is poor, consider disabling logging by making the GGPLocks.log file read-only. This can help reduce network load but will stop audit logging.