Urgent Print Error 61 Hotfix needed

A

Ajit

I receive this error in my server and the printer does not
print. Understand there is a hotfix available to fix this.
Pls advise where to download it.

Event Type: Error
Event Source: Print Event Category: None
Event ID: 61
Date: 19-7-2004
Time: 9:22
User: domain\ajit
Computer: PRINTSERVER
Description: The document ajit.xls owned by USER25 failed
to print. Win32 error code returned by the print
processor: 3003 (0xbbb)

Thanks,
Ajit
 
S

Shilpa Sinha [MSFT]

Hi

Maybe this will help:

The System Event Log Contains Many Event 61 Entries

SYMPTOMS
===============
After you install Windows 2000 Service Pack 3 (SP3) , you may see many
error event 61 entries in the System event log:
Event ID: 61
Event Type: Error
Event Source: Print
Description: The document document_name owned by username failed to print.
Win32 error code returned by the print processor: 63(0x3f)

CAUSE
=====
Starting with SP3, every status other than 0 that is returned by the print
processor is logged as error event 61. However, some status codes are not
really errors. You must also evaluate the Win32 error code. For example,
for status code 63 (0x3f), type the following line at a command prompt:

net helpmsg 63

This returns a "Your file waiting to be printed was deleted" message. This
means that the user canceled the print job intentionally. This is already
logged as informational event 13.

After you install the hotfix that is described in this article, event 61 is
not logged for Win32 status 63 (0x3f).

RESOLUTION
=========
Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft
Windows 2000. For additional information, click the following article
number to view the article in the Microsoft Knowledge Base:
260910 - How to Obtain the Latest Windows 2000 Service Pack
http://support.microsoft.com/default.aspx?scid=kb;EN-US;260910
Hotfix Information

A supported fix is now available from Microsoft, but it is only intended to
correct the problem that is described in this article. Apply it only to
computers that are experiencing this specific problem. This fix may receive
additional testing. Therefore, if you are not severely affected by this
problem, Microsoft recommends that you wait for the next Windows 2000
service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the fix. For a complete list of Microsoft Product
Support Services phone numbers and information about support costs, visit
the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support
calls may be canceled if a Microsoft Support Professional determines that a
specific update will resolve your problem. The typical support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.

The English version of this fix has the file attributes (or later) that are
listed in the following table. The dates and times for these files are
listed in coordinated universal time (UTC). When you view the file
information, it is converted to local time. To find the difference between
UTC and local time, use the Time Zone tab in the Date and Time tool in
Control Panel.

Date Time Version Size File name
--------------------------------------------------------
04-Dec-2002 16:54 5.0.2195.6154 250,640 Localspl.dll
04-Dec-2002 16:54 5.0.2195.6047 79,632 Spoolss.dll
04-Dec-2002 16:54 5.0.2195.6044 84,752 Win32spl.dll

STATUS
==========
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed at the beginning of this article. This problem was first
corrected in Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION
===========================
For additional information about how to obtain a hotfix for Windows 2000
Datacenter Server, click the article number below to view the article in
the Microsoft Knowledge Base:

265173 - The Datacenter Program and Windows 2000 Datacenter Server
Product
http://support.microsoft.com/default.aspx?scid=kb;EN-US;265173
The information in this article applies to:
o Microsoft Windows 2000 Advanced Server SP3
o Microsoft Windows 2000 Server SP3
o Microsoft Windows 2000 Professional SP3


Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
A

Ajit

Please help me on the followings urgently.

I can't understand why Microsoft says it has a problem and
also a patch is available, but does not give the download
link for the patch. Its rediculous.
 
S

Shilpa Sinha [MSFT]

Hi

We have to track the usage of hot fixes and that is why it has to be done
this way

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the fix for free. For a complete list of Microsoft
Product Support Services phone numbers and information about support costs,
visit the following Microsoft Web site:


http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Alternatively,

Send me your information in email, your correct email address, first and
last name, contact number and the exact issue that you want the hotfix for
(mention the reference KB article if possible) then it can be mailed to you.

Note:: A hot fix is for the issue described only and if you dont have
exactly that issue then you may not want to install the hotfix

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
G

gnolmat

Ajit said:
*I receive this error in my server and the printer does not
print. Understand there is a hotfix available to fix this.
Pls advise where to download it.

Event Type: Error
Event Source: Print Event Category: None
Event ID: 61
Date: 19-7-2004
Time: 9:22
User: domain\ajit
Computer: PRINTSERVER
Description: The document ajit.xls owned by USER25 failed
to print. Win32 error code returned by the print
processor: 3003 (0xbbb)

Thanks,
Ajit *

Hi Ajit,
there is an easy solution by using an LPR port instead of a standard
TCP/IP port.

Tom
 
M

Microsoft

You can call Microsoft and ask for Hotfix in KB 824339. They won’t charge
you for that.

The Hotfix does not fix problems causing Event 61 - but it can be used to
log additional information surrounding errors causing event 61. For
example, the event data will now contain the data type of the Print job, the
driver name, amount of bytes spooled and a few additional bits. No further
information about the root cause is added, but it allows gathering
statistical information like the printer driver that is most often involved,
etc. It’s definitely one of your drivers causing this issue and you have to
find it.



-Mark
 

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