Have you tried postscript drivers instead of pcl drivers?

On Tue, Jan 13, 2009 at 10:28 AM, Chinnery, Paul <[email protected]> wrote:
> We have about 80 printers (majority are HP's, various models, with about 10
> Ricohs) that are on our network.  We use a print server for them so anybody
> that needs a printer simply browses to the print server and connects.
>
> We have had 2 occurrences, recently, that when a new printer is added (in
> this last occurrence a Canon) some of the HP's won't print until the print
> driver is reinstalled.
>
> Here's an example:
>
> A report within our HCIS is automatically generated.  The background job
> server (which has a job running that listens to see if this report is
> generated) is supposed to print the report.  However, since the Canon was
> added to the print server, the printer to which the bg server was to print
> the report doesn't print it.  An error is generated similar to this (from
> Evt Log on the BG server; print server has no errors):
>
> Source: dmRenderClasses
> Destination: The description for Event ID ( 0 ) in Source ( DMRenderClasses
> ) cannot be found. The local computer may not have the necessary registry
> information or message DLL files to display messages from a remote computer.
> You may be able to use the /AUXSOURCE= flag to retrieve this description;
> see Help and Support for details. The following information is part of the
> event:
>
> Unable to print report: ' Document Manager
> Destination: \\DIET\DIETITIAN
>
> So far, the only solution has been to reinstall the printers which really
> isn't a solution at all but just a fix.
>
> Paul Chinnery
> Network Administrator
> Memorial Medical Center
> 231-845-2319
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to