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; Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
||
|
|
||
Symptoms |
Prinergy is started and DiagView does not show the usual startup messages. All DiagView shows is it has connected to port 49998, and the last line in DiagView is "socket connected" The Araxi logs in the %AraxiHome%\CreoAraxi\System\Log folder contain AraxiXXX.log files with date/time stamps newer than the current date/time on the system. The currently active Araxi log file indicated by AraxiCurrentIs.XXX file contains no new information. I.E. Prinergy is not logging any messages to the file. Someone has changed the system date/time to the future, started Prinergy then set the date/time back. |
|
|
|
||
Cause |
The Diagnostics daemon uses the date/time stamp of the diagnostic log files to determine which is the most recent file. The problem could arise if a diagnostics log file with a newer timestamp than the current system date/time exists in the %AraxiHome%\CreoAraxi\System\Log folder. |
|
|
|
||
Solution |
Remove all log files that have a timestamp newer than the current date/time of the system. Permanent fix: |
|
|
|
||
See also |
||
|
|
||
Keywords |
diagview |
|
|
|
||
Technical contact(s) |
Stan Yoshida |
|
Submitted by |
Stan Yoshida |
|
Date submitted |
Jan 10/02 |
|