Win2K Terminal Server Printing Difficulties

[Euan Holton]

Good morning one and all

I'm having problems with some printers installed on the
Terminal Services (with Citrix MetaFrame) boxes we have
here.

Some printers (an HP5550, Minolta Magicolor 2300 and a HP
930C) "lose" print jobs sent to them - a users
clicks "Print", the job goes into the queue and disappears.

I set up print logging on one of the affected servers and
this is an event that came up for one the printers (the
930C).

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 61
Date: 17/05/2004
Time: 09:51:18
User: *user*
Computer: *computer*
Description:
The document Microsoft Word - *document name* owned by
*user* failed to print. Win32 error code returned by the
print processor: 5 (0x5).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. (which doesn't
actually tell me anything).

I've looked at the printer objects, and the permissions
look fine for the users involved - I've even elevated them
to manage printers for the affected printer objects; and
I've made sure that the basic minimum permissions for the
spool directory are in places (as per the relevant KB
article). Any suggestions as to other things to try?

Euan Holton
Network Support Technician
Senior Aerospace BWT
Unmask me for email address.

 

[Greg Evensen]

Good morning one and all

I'm having problems with some printers installed on the
Terminal Services (with Citrix MetaFrame) boxes we have
here.

Some printers (an HP5550, Minolta Magicolor 2300 and a HP
930C) "lose" print jobs sent to them - a users
clicks "Print", the job goes into the queue and disappears.

I set up print logging on one of the affected servers and
this is an event that came up for one the printers (the
930C).

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 61
Date: 17/05/2004
Time: 09:51:18
User: *user*
Computer: *computer*
Description:
The document Microsoft Word - *document name* owned by
*user* failed to print. Win32 error code returned by the
print processor: 5 (0x5).

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. (which doesn't
actually tell me anything).

I've looked at the printer objects, and the permissions
look fine for the users involved - I've even elevated them
to manage printers for the affected printer objects; and
I've made sure that the basic minimum permissions for the
spool directory are in places (as per the relevant KB
article). Any suggestions as to other things to try?

Euan Holton
Network Support Technician
Senior Aerospace BWT
Unmask me for email address.

Error 5 - Access denied. The print processor is writing temp files
using a security token for the submitting user. Writing where? Who
knows. It may be the temp folder, but possibly it's hardcoded into
the registry or the software.

Greg

 

[Euan Holton]

-----Original Message-----
"Euan Holton" <[email protected]> wrote in

Error 5 - Access denied. The print processor is writing temp files
using a security token for the submitting user. Writing where? Who
knows. It may be the temp folder, but possibly it's hardcoded into
the registry or the software.

Thank you for that information. Any thoughts where might
be a good idea to look?

Also, I've found that a different printer comes up with
roughly the same entry in the log file, except the Win32
error code is 0x0 rather than 0x5. Any idea what that
could be?

Euan Holton
Network Support Technician
Senior Aerospace BWT
Unmask me for mail replies.

 

[Greg Evensen]

Thank you for that information. Any thoughts where might
be a good idea to look?

Also, I've found that a different printer comes up with
roughly the same entry in the log file, except the Win32
error code is 0x0 rather than 0x5. Any idea what that
could be?

Euan Holton
Network Support Technician
Senior Aerospace BWT
Unmask me for mail replies.

The print processor is registered here:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows
NT x86\Print Processors

You could try moving the default spool directory to a place
outside the Windows directory and give Everyone full control
as a test to see if things clear up. Do this in the printers
folder under File / Server Properties.

As far as the 0x0 errors, it's possible that a call
to the print processor is returning False, without setting
the error code properly.

 

[Jim_Wright]

We were having the same problem. What I did as a work around was t
stop sharing the printer from the print server and re-install th
drivers. I also made sure that the printer was setup as an LPR por
and not RAW


-
Jim_Wrigh

 

[Jim_Wright]

We were having the same problem. What I did as a work around was t
stop sharing the printer from the print server and re-install th
drivers. I also made sure that the printer was setup as an LPR por
and not RAW


-
Jim_Wrigh