[windows2000] Re: Printing not working....
- From: Ruud Bransen <rb@xxxxxxxxxxx>
- To: "'windows2000@xxxxxxxxxxxxx'" <windows2000@xxxxxxxxxxxxx>
- Date: Mon, 2 Dec 2002 10:57:48 +0100
Maybe this will help:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Event ID: 61=20
Source Print =20
Type Error =20
Description The document <document name> owned by <user name> failed to
print. Win32 error code returned by the print processor: <error code>
(<error code in hex>). =20
Peter Addor: Error Code 3003: I tried to print from the network PC =
named A
to the printer which is connected to the network PC named B after I
exchanged B by a new PC. On this new PC I had to reinstall also the =
printer.
After that I was no more able to print from B to the printer. I deleted =
the
printer on B and reinstalled it again. After this, I was able again to
print.
Mathias T=F6lken: From a newsgroup post, when events 45 and 61 are =
logged on
W2K print server:
What does this mean:=20
Document rendering was not successful. Rendering is that part of the =
spooler
process where jobs are passed to language and port monitors for =
processing.
All monitors are layered as defined within the
"HKLM\System\CurrentControlSet\Control\Print\Monitor" registry key.
Impact:
Once you see these events (45/61) pop-up, the job is deleted from the =
queue
and no print-out received by the printer. Sometimes this happens for =
every
3-4 prints made by anyone.
Solutions:
The Event 61 reveals more than the Event 45, because Event 61 logs also =
the
user, job and queue details of the job sent. Additionally a Win32 error =
code
is logged and reveals the actual reason why the OS has stopped
processing/rendering the job:
3003 A StartDocPrinter call was not issued (printer not reached on =
network)
63 Your file waiting to be printed was deleted (user deleted job)
129 The %1 application cannot be run in Win32 mode (???)
29 The system cannot write to the specified device (port error)
3003 and 63 should not trouble you, as these occur in quite normal
situations.
29 is related to a Port name that has become inactive/corrupt, normally
corrupted by the print driver =3D> wrong driver code. Restarting the =
spool
service will solve the problem, as well as creating a new port (with a =
new
name!), but this is temporarily. Enabling LPR Byte Count after =
stop-start
spooler proved to be a better solution.
129 were seen ''storming'' on multiple servers. In the end it appeared =
that
these servers were typically stressed (100% CPU; spoolsv.exe consuming =
800+
Mb; 500+ jobs left in spool folder) due to a running page heap debug =
process
(to detect corrupt driver code). After stopping page heap, the problems
disappeared and stayed away.
Did a bit more research on this issue as we do also get other error =
codes
occasionally. It looks like SP3 for W2k adds this error logging as =
standard
as we get it on numerous servers that have got print spoolers on since
applying that SP.
Found a great Java applett that returns the description of any Win32 =
error
code, see link below.
I typed in the errors that we received in our system and got following
results:=20
0 (0x0) The operation completed successfully.
5 (0x5) Access is denied.
63 (0x3f) Your file waiting to be printed was deleted.
259 (0x103) No more data is available.
3003 (0xbbb) A StartDocPrinter call was not issued.
Even easier, to return the description of any error message in W2K go =
to a
Command prompt and type: NET HELPMSG message# (e.g. "net helpmsg 63" =
returns
"Your file waiting to be printed was deleted."). =20
Links Win32 Error codes translated :
http://pages.istar.ca/~neutron/win32errors/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
Regards,
=20
Ruud Bransen
Databalk bv
www.databalk.nl
www.diskis.nl
=20
> -----Original Message-----
> From: Steve Rance [mailto:Steve.Rance@xxxxxxxxxxxxxxxxxxxxx]
> Sent: maandag 2 december 2002 10:42
> To: windows2000@xxxxxxxxxxxxx
> Subject: [windows2000] Printing not working....
>=20
>=20
>=20
> Hello,
>=20
> This morning we are having problems printing. =3D20
>=20
> All our network printers, with Jetdirect cards/boxes are setup on a =
=3D
> Windows 2000 Print server.
>=20
> When users print the job "errors" and the following is logged in the =
=3D
> System log on the print server.
>=20
> I have stopped and started the printer spooler to no effect.
>=20
> Event Type: Error
> Event Source: Print
> Event Category: None
> Event ID: 61
> Date: 02/12/2002
> Time: 09:33:13
> User: DALY\dalyadmin
> Computer: DALYPRT
> Description:
> The document Test Page owned by dalyadmin failed to print. Win32 =
error =3D
> code returned by the print processor: 3003 (0xbbb). =3D20
>=20
> Not all print jobs are failing only some, I am still working out if =
=3D
> there is a pattern.
>=20
> Any ideas?
>=20
> Thanks,
>=20
> Steve
>=20
>=20
>=20
>=20
>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> To Unsubscribe, set digest or vacation
> mode or view archives use the below link.
>=20
> http://thethin.net/win2000list.cfm
==================================
To Unsubscribe, set digest or vacation
mode or view archives use the below link.
http://thethin.net/win2000list.cfm
Other related posts:
