Home | Contact Us | Submit Troubleshooting Info | Search | Help


    Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS


System behaves erratically and files fail to process


Product

  Prinergy 1.1; Prinergy Connect 2.0

Platform

 

Operating system

 


Error

 


Symptoms

 

Prinergy seems to be consuming a lot of disk space on the system drive. This is causing the system to behave erratically when it runs out of disk space.-

Files fail to process (RIP, Normalize).


Cause

 

Solution

 

There are several things that can be done:

(1) Reduce the number of entries that are maintained in the '%ARAXIHOME%\CreoAraxi\data\TaskServerData" directory. This directory contains information related to every task (refining, output, archiving) that has taken place on the system. The default behaviour is for Prinergy to automatically delete task data that is older than 3 days. For some sites that process a lot of data (i.e. create a lot of tasks), this directory may contain a lot of information. The registry is used to configure the length of time information is kept in this directory. The setting is in "HKEY_LOCAL_MACHINE\Software\Creo\Araxi\Default\1.0.12.BLD69\TAKS\CleanupTaskDirLifetimeInSeconds"; a good value would be to set this to 6 hours, which is 21600 seconds (you should enter 21600 since this value is in SECONDS).

(2) Change the Printer Spooling directory to the TEMP drive (usually E: but specified by the TEMP system variable). There is another entry in the Tech Library (and also in the Prinergy Installation Guide) that explains how to do this.

(3) Review the WinNT pagefile configuration. The general rule is to put as much of the page file on the C:\ drive (this is the boot drive) and then put the rest on the D:\ drive (which has WinNT and Prinergy installed). It is NOT a good idea to put any of the pagefile on the E:\ (TEMP) or RAID as these drives already are involved in a lot of I/O (Prinergy paging and data access).

(4) Make sure that a MEMORY.DMP file does not exist on the system drive. If there was a BSOD crash, NT can be configured to dump the contents of RAM to disk (in the MEMORY.DMP file). If this file is on the system drive, either move it to a disk that has more space (RAID, TEMP drive, other server), back it up to tape or else delete (only delete if you don't need the information any more).

Permanent fix:


See also

 


Keywords

 

administrator


Technical contact(s)
 

Simon Chen

Submitted by
 

Date submitted
 


    Copyright © 2005 Creo Inc. All rights reserved. Confidential. Back to top.