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


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

DASS crash when Prinergy is unable to connect to the registry on a secondary machine

Product

   Prinergy Connect 2.0

Platform

  

x86

Operating system

  

Windows 2000 Server

Error

  

Prinergy Primary will not start when one or more of the secondary machines (including Renderstations) is powered off or otherwise not available on the network.

Symptoms

  

- Orbix error 10085 appears in Diag logs

- Primary will get to the point of "Starting JTP's...", hang for a minute or so, and then Prinergy will shut down.

Cause

   Problem was introduced by a DASS modification in 2.0.7.10. DASS tries to connect to the registry on each secondary machine. If it is unsuccessful (ie the machine is not available on the network), DASS does not react well and terminates. This in turn causes a cascading failure of processes until Prinergy ends up shut down again.

Solution

  

The offending secondary can be temporarily removed from Prinergy Administrator (UADM):

1. Remove server from system via Configure System

- JTP's are still shown in UADM and in the registry (DASS/Services)

2. Restart Prinergy on Primary server

- JTP's for removed server are no longer in UADM (neither the JTP's or the listing in the pool)

- JTP's ARE still in the registry (DASS/Services) with no modification to the settings.

3. When the secondary is brought back on-line, simply re-add the secondary to the Prinergy system using UADM. The previous feature settings and licenses will be retained.

Permanent fix:

See also

  

Keywords

  

DASS, JTP, networking, orbix, registry, Windows 2000
Technical contact(s)
  

Robyn Lundstrom, Miriam Bailey
Submitted by
  

Robyn Lundstrom
Date submitted
  

13 Mar 2002

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