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


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


Sometimes files get stuck in the Brisque 5.0 Queue Manager after shutdown


Product

 

Brisque® 5.0.61.6

Platform

 
  • 44P–170—Hammerhead
  • F50—Wildcat (2 and 4 CPUs)
  • 6F1—Condor (2, 4 and 6 CPUs)
  • 6E3
  • 6E4

Operating system

 

IBM® AIX® 5.2


Symptoms

 

After shutdown, when the Brisque 5 workstation restarts, files that were sent to the Queue Manager for RIP, proof or preview, get stuck in the running queue and the progress indicator doesn't appear. Performing a shutdown and reboot does not solve the problem.


Cause

 

A problem in the current Brisque 5 version 5.0.61.6.


Solution

 

Perform the following diagnostics procedure to check the status of the server ports.
Note:
All servers running in the multiserver process accept the following protocol.

  1. Type telnet <hostname> <port> where hostname is the Brisque host or IP, and port is one of the following:
    • 5990—Message Handler port
    • 5995—Progress Handler port
    • 5996—Preview Router port
    For example, to check the status of the Message Handler port, type: telnet brisque5 5990
  2. When the telnet connection is established, type 1 and press Enter.
  3. If the server does not return a string containing the session Id, this implies that the server is not functioning properly—go to step 4.
  4. Remove all *.reg files from the /scitex/version/config/ directory, and restart Brisque 5.
  5. If the server returns a string containing the session Id and then closes the connection, run brisque_check.sh in order to try to identify the problem.

Technical contact(s)
 

Lev Weissman

Submitted by
 

Lev Weissman

Date submitted
 

02 June 2004


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