RE: Printing issues

From: Shilpa Sinha [MSFT] (v-shilsi_at_online.microsoft.com)
Date: 08/03/04 

Date: Tue, 03 Aug 2004 01:26:56 GMT

Hi

Maybe this will help:

Documents from Terminal Server Users Who Map LPT1 to Different Printers
Appear on the Same Printer

SYMPTOMS
==============
If two different Terminal Session users map LPT1 to two different printers
(for example, if "user1" runs the net use lpt1: \\server1\printer1 command,
and if "user2" runs the net use lpt2: \\server2\printer2 command), these
two users expect their documents to appear on different printers. In some
situations, and from some programs, documents from both users may appear on
the same printer.

You may see the following event in the system event log:

Event Type: Error Event Source: Print Event Category: None Event ID: 61
Description: The document Test Page owned by username failed to print.
Win32 error code returned by the print processor: 3003 (0xbbb).

CAUSE
=========
The internal addressing for MS-DOS devices, such as LPT1, was changed in
Terminal Server between Microsoft Windows NT 4.0 and Microsoft Windows
2000. Corresponding changes also had to be made to other modules in the
system that accessed such devices. However, these required changes were not
implemented in the local spooling system. Therefore, the spooling system
does not function in Windows 2000 as it did in earlier versions.

The hotfix that is described in this article adds the required logic to
address MS-DOS devices correctly and to correct the problem.

Note: You will have to re-create the local printer queue after you install
this hotfix.

RESOLUTION
=============
Hotfix Information

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

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. 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;[LN];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 usual support costs will
apply to additional support questions and issues that do not qualify for
the specific update in question.

Prerequisites

To install this hotfix, you must have Windows 2000 Service Pack 3 (SP3) or
Windows 2000 Service Pack 4 (SP4) installed on your computer.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix 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
   --------------------------------------------------------------
   08-Sep-2003 09:50 5.0.2195.6817 252,176 Localspl.dll
   04-Sep-2003 09:06 5.0.2195.6801 5,232,128 Sp3res.dll
   08-Sep-2003 09:50 5.0.2195.6741 80,656 Spoolss.dll
   08-Sep-2003 09:50 5.0.2195.6681 97,040 Win32spl.dll

WORKAROUND
================
To work around this problem, upgrade to Microsoft Windows Server 2003.

STATUS
===========
Microsoft has confirmed that this is a problem in the Microsoft products
that are listed in the "Applies to" section.

MORE INFORMATION
========================
For additional information about how hotfix packages are named, click the
following article number to view the article in the Microsoft Knowledge
Base:

        816915 - New naming schema for Microsoft Windows hotfix packages
http://support.microsoft.com/default.aspx?kbid=816915

The information in this article applies to:
 
        o Microsoft Windows 2000 Server
        o Microsoft Windows 2000 Professional
        o Microsoft Windows 2000 Advanced Server

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

Relevant Pages

  • Re: Cant open Application Log
    ... A support engineer will be assigned. ... Microsoft Windows Server 2003, Web Edition ... Microsoft Windows Server 2003, Standard Edition ... Hotfix Information ...
    (microsoft.public.windows.server.sbs)
  • RE: Backup Failing
    ... I am glad to hear that after you applied the hotfix again, ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • RE: Backup Failures
    ... I understand that you need the hotfix KB828481 for a VSS issue. ... call into the appropriate Microsoft Support phone line, ... help and advice from a Microsoft support professional. ... recommended that you use the built-in backup and restore utilities in SQL. ...
    (microsoft.public.windows.server.sbs)
  • Re: STOP 0x0000001e after MS05-018 on Windows 2000
    ... You'll need to contact Microsoft Product Support Services to obtain the free ... Microsoft Certified Professional ... | I see that a hotfix is available that might solve my problem. ...
    (microsoft.public.win2000.general)
  • Re: IIS caching output of pages
    ... Here are my server and development box specs: ... > Thanks, but the post does not include the URL of the hotfix, and the KB ... Microsoft recommends that you wait for the next Windows ... >> To resolve this problem immediately, contact Microsoft Product Support ...
    (microsoft.public.dotnet.framework.aspnet)