Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy 1.1 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
When Prinergy is running, the server beeps once every 30 seconds. This is not a UPS or RAID controller problem. No errors are reported in Event Viewer or in Araxi logs. The customer notices that some or all PPF files sent by FTP to a Heidelberg Prepress Gateway (or other) are failing. The customer will notice that after a restart of Prinergy, the server may beep continuously for a few minutes, then resume beeping every 30 seconds. |
|
|
|
||
Cause |
The FileTransmitter daemon has a retry queue that is set in the registry (FileTransmitter\MaxRetries), and it will retry every 30 seconds until this value is reached. Also, unless specified otherwise in the registry, there are two files located in the same folder as FileTransmitter. One is called Process.queue and the other is called Retry.queue. These are files that keep track of the path to the file that should transmit. If there are a lot of files that failed to delete because they failed to transmit, these files will be large and probably corrupted, which accounts for all the beeps at startup. Unfortunately, error logging from the FileTransmitter daemon has been disabled, because it was found that logging caused other problems with the software. In addition, FileTransmitter runs in "headless" mode, that is, without displaying a console window. The only way to view the activity of FileTransmitter Daemon is to edit ARAXI.INF and comment out the line that starts the FileTransmitter: # FTP Daemon "FileTransmitter" /unique "FileTransmitter" /NORMAL /Title "FTP Daemon". Then launch FileTransmitter from the command prompt. The window will open and you will be able to see and capture any activity that takes place. | |
|
|
||
Solution |
In systems exhibiting this problem, the only workaround is to run FileTransmitter as an application. Create a shortcut to FileTransmitter.exe (it should be in %Araxihome%\Prinergy\AdobeExtreme\bin) and place it on the desktop. If it is determined that there are files that fail to transmit, it is possible the files themselves are corrupted. Delete the files Process.queue and Retry.queue; they will be recreated by the FileTransmitter. Then delete all the PPF files that failed to send. The location of these files is specified in the process plan. Instruct the customer to launch FileTransmitter from the new desktop shortcut, after Prinergy has started. Prinergy 2.0 bundles FTP functionality within Printlink, and does not rely on the FileTransmitter daemon. Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
CIP3 (or PrintLink) |
|
|
|
||
Technical contact(s) |
Simon Chen |
|
Submitted by |
||
Date submitted |
||