Event ID 45 and 61 when Trying to Print


C

Charles

We have a NT4 Domain. A windows 2000 server acting as a print server.
There are 8 printers installed on the server.

It has been running as such for almost 8 months without any major
hiccups.

On 2/13/04, 6 of the 8 printers, all HP, stopped print for all users
logged on the domain as domain\users. We have 2 sharp copiers that are
still working without this problem.

When a domain user prints a document, the event viewer show 2 error
messages.

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 45
Date: 2/16/2004
Time: 3:39:57 PM
User:
Computer:
Description:
Document failed to print due to GDI/Driver error in rendering.

And

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 61
Date: 2/16/2004
Time: 3:39:57 PM
User:
Computer:
Description:
The document cit inv2-16.xls owned by failed to print. Win32 error
code returned by the print processor: 3003 (0xbbb).

The Print job makes it to the correct print queue. It sits there for a
while and comes back with a general error message. It stays in the
queue and must be manually removed.

We have searched "high and low" for the resolution on this one.

Any help is greatly appreciated
Charles
 
Ad

Advertisements

F

Felix Maxa [MSFT]

What SP and what QFEs do you have on the print server?

Error 3003 is generally logged when the print server cannot contact the
device. Are you using the Standard TCP/IP port monitor? Can you ping the
devices when you are logged on the the print server?

--
Felix Maxa
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
 
C

Charles

We are using SP4. SP4 has been installed on the machine for months. We
are up-to-date on the hotfixes as of yesterday.

We are not seeing error 3003. Domain Admins are able to print to these
devices.
We are able to ping the device from the print server. When a domain
user sends a print job, it makes it to the print queue for the device.
The job, however, "hangs". So it looks as if the device is being
contacted.

Being that these printers are all HP models, they are using the HP
Standar TCP/IP port. It is a little strange, the Sharp models, that
are still functioning properly, are using the Standard TCP/IP port.

Because the domain admins can print to all the printers, it looks to
us to be a permission issue. We have added the everyone group to the
%system%\spool and %system%\temp folders. The everyone group has been
given full control to those folder and sub folders. Still no joy.
 
C

Charles

Upon further review:
We are seeing this error in the eventviewer of the print server.

Event Type: Error
Event Source: Print
Event Category: None
Event ID: 33
Date: 2/16/2004
Time: 3:11:43 PM
User: NT AUTHORITY\SYSTEM
Computer:
Description:
The PrintQueue Container could not be found because the DNS Domain
name could not be retrieved. Error: 547
 
F

Felix Maxa [MSFT]

The error number is logged in hexadecimal. Here's the meaning:

C:\>net helpmsg 1351
Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied.

There could be some sort of security/authentication problem. So you're not
getting events 45 and 61 anymore? Do you still have queue where only the
administrators can print? What drivers do those queues use? Are they based
on UNIDRV? What happens if you change the port for such a queue to a local
port called "nul:"? Can regular users print? You can add a nul: port from
the print UI.


--
Felix Maxa
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
 
C

Charles

We are still seeing both 45 and 61. 33 is thrown first.
Yes we still have all of the symptoms only admins can print.
Looks like there is a pretty long list of driver files.
This particular model (which we have 2) (same symptoms) is a
HP Laser Jet 2300 Series PCL6 (60.5.12.2)
hpc23256.gpd
unidrv.dll
unidrvui.dll
unidrv.hlp
hp6mac05.gpd
hpbcfgre.dll
hpboid.exe
hpbiodps.dll
hpc23006.dll
hpc23206.dll
hpc2320c.ini
hpc23256.xml
hpc2325c.ini
hpcdmc32.dll
hpcevt05.dll
hpclix06.hlp
hpcsch05.dtd
hpcstr05.dll
hpcui05.dll
hpcxrd05.dll
hpjcmn20.dll
hpjipx1u.dll
hplj2300.cfg
hppapml0.dll
hppapts0.dll
hppasnm0.dll
hpprn05.dll
hpzinw12.exe
hpzipm12.exe
hpzipr12.dll
hpzipt12.dll
hpzisn12.dll
p6disp.gpd
pclxl.dll
pclxl.gpd
pjl.gpd
stdnames.gpd
unires.dll
hpbmmon.dll
hpdomon.dll
hpbhealr.dll
hpnra.exe
hpbnrac2.dll
hpbmini.dll
hpceac05.hpi
Yes the drivers are based on UNIDRV.
Adding a local port called nul provides worst results. The document
printed doesn't make it to a queue and is not printed at all.
 
Ad

Advertisements

F

Felix Maxa [MSFT]

Well, I should've mentioned that the nul: port is for troubleshooting
purposes only. It's actually the nul: device which discards anything sent to
it. The goal was to see if the job goes through (meaning it doesn't hang)
when using the nul: port. If that's the case, then the problem is with the
port monitor or the port or the device, but not with the rendering driver.

Do you have a queue with an inbox driver where only admins can print?

Did you try reinstalling unidrv? In print server properties, drivers tab,
select a unidrv based driver and click reinstall. This should be done for an
inbox driver. If you don't have one, you can install an inbox driver just
for troubleshooting. Then see if the queues work for non admins.

Sorry, I can't tell for sure what's going on, but I can provide help with
the investigation.

--
Felix Maxa
Microsoft Printing, Imaging and Fax Team
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
 
Ad

Advertisements

C

Charles

We added the Standard Ip Port for each HP printer. Changed to the
Standard IP port from the HP Standard IP Port.

That fixed it.

Don't really understand why the HP Standard IP port stopped working

But...........................

Thanks for the help
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top