![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.1 ; Prinergy Direct 2.1 ; Prinergy Access 2.1 ; 3.0 | |
Platform |
Intel |
|
Operating system |
Windows 2000 |
|
|
|
||
Error |
-------------------------------------------------------------------------------- Wed Oct 12 22:00:00 2005 AraxiFileReplicator is starting. AraxiFileReplicatorService: Log file name: D:\Prinergy2.0.4\creoaraxi\system\log\araxifilereplicator\AraxiFileReplicator.log AraxiFileReplicatorService: Log file max size: 1048576 Wed Oct 12 22:00:00 2005 Run service: Calling doRealWork to start replication Wed Oct 12 22:00:00 2005 doRealWork: about to call PReplicateD functionality Thu Oct 13 13:08:19 2005 doRealWork: just returned from calling PReplicateD functionality Thu Oct 13 13:08:20 2005 Run service: Returned from doRealWork Thu Oct 13 13:08:20 2005 Run service: AraxiFileReplicator has finished. StartAraxiFileReplicator: Thu Oct 13 22:00:00 2005 StartAraxiFileReplicator: Attempting to start the araxifilereplicator service |
|
|
|
||
Symptoms |
The AraxiFileReplictor which normally runs at 22:00 every night is taking a long time to complete. In the sample AraxiFileReplicator log, the AraxiFileReplicator took 15 hours to complete. |
|
|
|
||
Cause |
The AraxiFileReplicator is replicating the temporary process plans and over a period of time, a very large number of temporary process plans are accumulating in the EPM or EPM+ server. | |
|
|
||
Solution |
Remove the temporary process plans on the EPM or EPM+ server. This has been fixed in Prinergy 3.0.3.0. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
EPM, Emergency Platemaking (EPM), Hot Standby |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
17 Oct 2005 |
|