When a publishing job runs, it will download documents to a local workspace on a disk of the Publisher node. The local workspace will grow as more documents are published and, by default, because publishing runs as a service, the local workspace is not automatically cleaned of old files the same as it would be for an interactive user. This can lead to publishing jobs not completing and insufficient disk space errors.
To avoid this, we recommend that you regularly clean the local workspace on the Publisher node using the following command line with the Enterprise Server service account:
C:\Program Files\BC-Meridian\Program\AMHookTrayU.exe -sync –exit
If a 64-bit client setup program is used, the executable name is AMHookTray.exe.
This command can be run as a scheduled task (for example, once a week). The frequency should be adjusted for the amount of disk space configured for the local workspace, how often publishing occurs, the size of the source documents, and how many documents are published.
Learn more about configuring and administering local workspaces.
