LabMice.net - The Windows 2000\XP\.NET Resource Index
Home | About Us | Search

Last Updated December 10, 2003

Printer Management
  Where to Start
  How To Articles
  Installing Printers
  Printer Drivers
  Print Spoolers
  Technical Articles
  Troubleshooting
  HP Printer Bugs

Troubleshooting
  Where to Start
  General Guides
  Boot.ini files
  Error Codes
  Event Logging
  How to Guides
  Memory Dumps
  Memory Leaks
  Performance Tuning
  Recovery Console
  Win2k Install Bugs
  WinNT Upgrade Bugs
  Win9x Upgrade Bugs

 

 

 

 

 

Troubleshooting Printers in Windows 2000

With hundreds of printer manufacturers, and thousands of programs that utilize printers, the potentials for problems are endless. Where do you begin troubleshooting? Is it the printer driver? Is it the application? Is it the network? Or is it the Operating System? To make a life a little easier, we've assembled a list of all the know Windows 2000 printing issues according to Microsoft.
General Troubleshooting Guides
How to Troubleshoot Windows 2000 Printing Problems 
Microsoft Knowledge Base Article: 260142 - This article describes how to troubleshoot some common printing problems in Windows 2000.

Some Error Messages When Printing in Windows 2000, Windows NT, Windows 98. or Windows 95
Microsoft Knowledge Base Article: 121074 - These messages are erroneous and occur if the Windows for Workgroups or Windows 95 printer share is password protected. If you attempt to connect to the share by doing a NET USE from the command line, you receive this (correct) message: 

Troubleshooting Printing Problems in Windows NT 4.0
Microsoft Knowledge Base Article: 163551 - This article describes how to troubleshoot printing problems in Windows NT 4.0.

Troubleshooting Windows NT Print Server Alteration of Print Jobs
Microsoft Knowledge Base Article: 132460 - Windows NT print servers are able to alter client print jobs. The software responsible for altering client jobs rarely malfunctions, but sometimes alters jobs when you do not expect it to. This article describes how to troubleshoot such situations, explains how this behavior changes with different network clients, and details the "data type" concept that controls the spooler's alterations.

Known Bugs and Issues
"%%Title" Field May Not Be Correct in PostScript Print Jobs
Microsoft Knowledge Base Article: 287047 - When you print an Enhanced Metafile (EMF - PostScript print job, the "%%Title" field may indicate the printer name instead of the document name. 

Add Printer Wizard Forces HTTP Connections to Windows 2000 Internet Print Servers
Microsoft Knowledge Base Article: 222078 - When you make a connection to a Windows 2000 Internet print server using the "Connect to an Internet Printer" option in the Add Printer Wizard, the port is automatically installed as an HTTP printer port. There is no attempt to test for RPC 

Add Printer Wizard Does Not Work and Previously Installed Printers Are Not Displayed
Microsoft Knowledge Base Article: 271248 - When you attempt to add a printer using the Add Printer Wizard, you may experience one or all of the following: 1) Printers that were previously installed no longer show up in the Printers folder; 2)When you double-click the Add Printer Wizard, the wizard does not start, and you are returned to the Printers folder. 3)When you click Server Properties in the File menu in the Printers folder, the Server Properties window does not open and you are returned to the Printers folder. 

Adobe Acrobat .pdf Documents May Not Print Correctly in a Terminal Services Session
Microsoft Knowledge Base Article: 267896 - When you try to print Adobe Acrobat .pdf documents inside of a Terminal Services session, the general page layout may print correctly, the fonts may not print correctly. Instead of characters, you may receive squares in the output. 

Alternate Printer Driver Setup Prompts for an .Inf File
Microsoft Knowledge Base Article: 238827 - When you install an alternate print driver for a specific platform, the printer setup may prompt you for the location of an .inf file. 

Banner Always Printed When Using GSNW Print Gateway
Microsoft Knowledge Base Article: 130226 - If you print from a computer running Windows NT 3.5x to a NetWare Print Gateway defined on a computer running Windows NT 3.5x Server and Microsoft Gateway Service for NetWare (GSNW), you always receive a NetWare banner page before the print 

Banner Page Printed Even Though It Is Disabled
Microsoft Knowledge Base Article: 222190 - If you print to a NetWare printer queue on a Windows 2000-based server on which Gateway Services for NetWare (GSNW) is installed, a banner page may be printed even though the option to print a banner page is disabled. 

BitWare Causes Spoolsv.exe Program Error in Windows 2000
Microsoft Knowledge Base Article: 257859 - You may receive the following error message when you boot your computer, try to use a printer, or start a program that interacts with a printer: Spoolsv.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. The Spooler service then stops, but can be restarted. While the spooler is stopped, the following error message is generated: Printer operation cannot continue due to lack of resources.  

Cannot Browse Shared Printers When Using More than One Print Spooler
Microsoft Knowledge Base Article: 246390 - If you create more than one print spooler in a resource group, one or more print spoolers may not work properly or work intermittently. You may also not be able to browse to shared printers from client computers.

Cannot Install Language Monitor-Based Printer Driver as a Power User
Microsoft Knowledge Base Article: 244938 - When you attempt to install a Microsoft Language Monitor-based printer driver in Windows 2000 from the console of a computer on which the operating system is located on an NTFS partition and you are logged on as a member of the Power Users 

Cannot Start Print Job on Windows 98 Printer Share
Microsoft Knowledge Base Article: 257709 - When you attempt to print from a Windows 2000-based computer to a printer on a Microsoft Windows 98-based computer that is shared with a share-level password, the print job may not succeed. You may receive the following error message: 

Completion Notification Goes to Wrong Computer When Printing
Microsoft Knowledge Base Article: 101867 - When you have the alert service started on a Print Server, you may receive messages at the wrong computer when you print, if you are logged onto more than one machine. 

Computer with More Than 10 USB Printers May Not Print Correctly
Microsoft Knowledge Base Article: 289777 - If more than 10 USB printers are connected to a computer, Windows does not load the Usbprint.sys driver, and USB printing functionality does not work. 

CSNW/GSNW Add Printer Wizard Does Not Display Large Number of NDS Print Queues
Microsoft Knowledge Base Article: 269867 - When you use the Add Printer Wizard to browse NDS trees for print queues and the OU contains a large number of print queues, no print queues are displayed. The exact number of print queues that are needed to display this problem varies due to length of name and tree structure, however, a number of print queues that is greater than 359 has displayed this problem 

Documents Do Not Leave the Print Queue
Microsoft Knowledge Base Article: 183500 - After you log in to Windows, you may be unable to print. The document may appear in the print queue, but there may be no status and the document may not be printed. 

Document Not Printed and No Error Message Received
Microsoft Knowledge Base Article: 154777 - When you print a document, it may appear in the print queue but never be printed out. When this occurs, you receive no error message and there is no error in the event log. 

Domain-Level Printer List Is Not Refreshed
Microsoft Knowledge Base Article: 227908 - When you use the Add Printer Wizard to add a printer, networked printers are listed at both the domain level and the server level. The list of printers at the domain level may not be correctly refreshed as printers on a server are removed, 

During Cluster Failover Print Queue Monitoring May Stop
Microsoft Knowledge Base Article: 229733 - When a print queue window is open and actively monitoring the queue of a printer that is shared from a virtual server on a Microsoft server cluster, during node failover, the printer queue may generate the following error message: 

Error Connecting to Printer When Logged on to a Domain
Microsoft Knowledge Base Article: 149913 - When you are logged on to a domain and you attempt to connect to a shared printer on the network, an error message may occur. 

"Error Loading the TCP MIB Library" Adding a Standard TCP/IP Printer Port
Microsoft Knowledge Base Article: 261302 - When you are using the Add Standard TCP/IP Printer Port Wizard, you may receive the following error message: 

Err Msg: Could Not Connect to the Printer: The printer name is invalid
Microsoft Knowledge Base Article: 100362 - You cannot use the server name in Print Manager to browse print servers. Printers should be published in the Active Directory, and then the directory can be searched. 

Err Msg: Error Writing to LPT1: Access Denied
Microsoft Knowledge Base Article: 180892 - When you attempt to print to a Hewlett-Packard (HP) 4000-series printer connected to printer port LPT1, you may receive one of the following error messages: 

ErrMsg: Error Writing to LPT1: System Cannot Find File Specified
Microsoft Knowledge Base Article: 150498 - When you try to print to a local printer attached to the parallel port, the following stop error message is reported by WIN32 Spooler: 

Error Message: "Error Writing to <printer port>" When Printing
Microsoft Knowledge Base Article: 228542 - When you attempt to send a print job to a Windows NT-based print server, the following error message may be displayed: 

Err Msg: Not Enough Storage to Complete Operation
Microsoft Knowledge Base Article: 166840 - When you try to open the Printers folder, you may receive the following error message: 

Error Message: Server Spool Directory Location Is Invalid
Microsoft Knowledge Base Article: 240905 - When you change the spool folder on the Advanced tab in Print Server properties, you may receive the following error message: Server spool directory location is invalid 

Error Message "The Directory Operation Is Still in Progress" in Printer Sharing Dialog Box
Microsoft Knowledge Base Article: 268545 - On a domain controller, member server, or workstation in a Microsoft Windows 2000 Active Directory domain, the Sharing tab of the Printer Properties dialog box displays the following error message below the List in the Directory check box: "The Directory Opertion is still in progress." This is often caused by the Domain Name System (DNS) server address in the TCP/IP settings of the computer is not set correctly, or the DNS server is not set up correctly.

Err Msg: The Printer Driver You Selected Is Not Compatible...
Microsoft Knowledge Base Article: 221208 - When you try to install a printer driver on your Windows 2000-based computer, you may receive the following error message:

Err Msg: The Printer Name Is Invalid, it Cannot Contain "!", "\", ","
Microsoft Knowledge Base Article: 221181 - When you attempt to change printer properties, you may receive the following error message: 

Error Message: The Requested Resource Is in Use
Microsoft Knowledge Base Article: 228357 - After you upgrade your computer to Windows 2000, and you try to print a test page from your Kyocera FS-3700 PCL or FS-7000 printer, you may receive the following error message: 

Err Msg: The Server on Which the Printer Resides Does Not Have a Suitable Printer Driver
Microsoft Knowledge Base Article: 227907 - When you attempt to install a network printer on a Windows 2000-based computer, you may receive the following error message: 

Error Message: You Do Not Have Sufficient Access to Your Machine to Connect to the Selected Printer
Microsoft Knowledge Base Article: 259937 - When you attempt to connect to a printer while you are connected to a Windows 2000-based server that is running Terminal Services by using the Remote Desktop Protocol (RDP) client, you may receive the following error message: 

General Protection Fault in Module Gdi.exe Printing from Internet Explorer
Microsoft Knowledge Base Article: 261156 - When you print from Internet Explorer with a Hewlett-Packard (HP) DeskJet 932C or 952C printer, you may receive a general protection (GP) fault in module Gdi.exe. 

Graphics Print Poorly with Panasonic KX-P4420 Printer Driver Included with Windows 2000
Microsoft Knowledge Base Article: 262306 - When you print to a Panasonic KX-P4420 printer using the driver that is included with Windows 2000, the graphics quality is poor. For example, if you print a test page the Windows logo is unreadable. 

Incompatible Windows NT4.0 Print Drivers Are Blocked and Replaced When Upgrading
Microsoft Knowledge Base Article: 224966 - When you upgrade from Microsoft Windows NT 4.0 to Windows 2000, incompatible Windows NT 4.0 printer drivers (such as the Okidata Okipage 20 driver) are blocked and replaced with the driver included with Windows 2000.

Installing a Printer Driver for Windows NT4.0 in Windows 2000 Professional Prompts for the Windows 2000 Server CD-ROM 
Microsoft Knowledge Base Article: 311985 - On a computer that runs Windows 2000 Professional and has a Hewlett-Packard DeskJet 722C printer attached, when you try to install a printer driver for Microsoft Windows NT version 4.0 so that you can share the printer with a computer that runs Windows NT 4.0, you may be prompted for the Microsoft Windows 2000 Server CD-ROM.

Large LPD Jobs Time Out After 60 Seconds
Microsoft Knowledge Base Article: 280344 - Large print jobs from some Line Printer Resource (LPR) clients may not be printed on a Windows 2000-based server that is running the Line Printer Daemon (LPD) service, although smaller print jobs may be printed correctly. You may be able to determine the maximum print job size that can be printed successfully in your client/server configuration. Other implementations of the LPR client software may not be affected. 

Large Print Job on ECP Printer Port Causes Jump in CPU Usage
Microsoft Knowledge Base Article: 227675 - When you print a large PostScript print job to an ECP printer port, CPU usage may jump to 100 percent. 

LPR Does Not Print PostScript Files Correctly
Microsoft Knowledge Base Article: 123107 - When you use LPR from the command line to submit print jobs to a LPD print server, PostScript files may print out as PostScript source code files instead of a normal printout. In addition, a print job sent to a PCL printer may reset the printer 

Malformed Print Request May Stop Windows 2000 TCP/IP Printing Service
Microsoft Knowledge Base Article: 257870 - After you install the TCP/IP Printing service on a Windows NT 4.0-based computer or the Print Services for UNIX component on a Windows 2000-based computer, it may be possible to exploit a security vulnerability in the Line Printer Daemon (LPD) Server service on those computers. By sending a specially-malformed print request via the LPD Server service, a malicious user could cause the service to stop, preventing the computer from servicing some print requests. Other services may also be affected by stopping this service, including the Dynamic Host Control Protocol (DHCP) service. Affected services can be put back in service by restarting them; it is not necessary to reboot the computer.

Mapping Shared Local Printers to Central Share Causes Server to Crash, Generates Event ID 2020 from SRV
Microsoft Knowledge Base Article: 286060 - When you have several shared local printers that are attached to Microsoft Windows 98-based clients on your network, and you map the shared local printers to a central share on a server running Microsoft Windows 2000, the server may crash and log the following Event ID 2020 error from source SRV: "The server was unable to allocate from the system paged pool because the pool was empty."

MS-DOS Application Prints Incomplete Pages
Microsoft Knowledge Base Article: 101850 - All MS-DOS application printing is done through the Windows NT spooler system. In order to know when to send a job to the spooler, there is a time-out on the printer port. Once something has been printed to the port, if this time-out passes with no more data presented to the port, the print job is sent to the spooler. On a slow computer running a complex calculation to produce the print job, it is possible that the time-out can expire during this calculation. This will cause the printout to appear over multiple pages instead of a complete page. To solve this problem, increase the time-out. 

NET STOP Command Does Not Work on Microsoft Fax Service
Microsoft Knowledge Base Article: 228880 - When you attempt to use the NET STOP command on the Fax service, you may receive the following message: 

Network Printer Renamed After Upgrade to Windows 2000 from Windows 95/98
Microsoft Knowledge Base Article: 244002 - When you upgrade to Windows 2000 from Microsoft Windows 95/98, the names of the printers you use may change. 

No Local Ports Are Available for Printers
Microsoft Knowledge Base Article: 255507 - There may be no local ports available when you are configuring printers. Any printers that are connected to a local port may stop working with the following error message: 

Non-White Text on Dark Background Is Not Printed
Microsoft Knowledge Base Article: 257073 - When you use Internet Explorer to print a Web page that contains non-white (colored) text on a dark background, the colors may not be printed. For example, red text may not be printed on a black background. 

Nothing Happens When You Right-Click a Printer and Then Click Properties
Microsoft Knowledge Base Article: 254220 - When you right-click a printer and then click Properties the desktop may be redrawn but nothing else may happen (the printer properties are not displayed). General printing functionality seems to be unaffected by this behavior. This behavior can occur if Novell Distributed Print Services is installed.

OEM Print Drivers Are Overwritten by Microsoft Drivers That Use Terminal Services Redirect Printing
Microsoft Knowledge Base Article: 270005 - If you have a Windows 2000-based server with Terminal Services enabled that also has the OEM printer drivers, the spooler may stop responding. When the drivers are overwritten, print jobs in the queue become garbled, and must be printed. 

Offline Print Queues May Cause Print Jobs to Hang When Print Queue Is Online
Microsoft Knowledge Base Article: 268334 - In Windows 2000, you can set a print queue for offline use. You can use this functionality to print a document while you are not connected to the network, or when a print server is not available. When the network or print server is available 

Permission Error Messages Occur When Printing with the Guest Account
Microsoft Knowledge Base Article: 271901 - When you are working on a computer that is running Windows 2000, if you attempt to connect to a printer on another Windows 2000 computer that is part of a workgroup or a member of an untrusted domain, you may receive the following error message: 

Printers Folder May Hang if You Type an Incorrect URL in the Add Printer Wizard and Use Basic Authentication
Microsoft Knowledge Base Article: 244917 - When you attempt to connect to an Internet print server by typing a URL in the Add Printer Wizard, if you type a URL with incorrect syntax followed by several successful connections to an Internet print server that uses Basic (clear text) 

Print Head Repeatedly Moves to Left Margin When You Print 
Microsoft Knowledge Base Article: 271551 - When you print to a dot matrix printer, the print head may travel to the left margin, and then back to the current print position before printing a character. 

Printing to LPD Printer Is Slow or Fails with Windows NT
Microsoft Knowledge Base Article: 141708 - Delays may result when you print to a Windows NT 3.51 Service Pack 5 (SP5) or Windows NT 4.0 print server connected through line printer remote (LPR) to a shared printer using the Line Printer Daemon (LPD) service. 

Printers May Produce Garbled Output After a Print Job Is Deleted
Microsoft Knowledge Base Article: 160861 - Printers such as the Epson ESC/P models or Hewlett Packard (HP) DeskJet printers may produce garbled output on jobs printed after a print job that was canceled. 

Printer Not Displayed in Active Directory Users and Computers Snap-in
Microsoft Knowledge Base Article: 245584 - When you publish a printer in Active Directory, the printer may not be displayed in the Active Directory Users and Computers snap-in in Microsoft Management Console (MMC).

Printer Pruner May Not Remove Printer Queue Objects from Active Directory
Microsoft Knowledge Base Article: 246174 - Print queues that have been orphaned in Active Directory may continue to appear in Active Directory, even though the print server no longer hosts the print queue and Printer Pruner is configured correctly and has had adequate time to attempt 

Printer Server Problem When You Try to Print with a Guest or Local User Account 
Microsoft Knowledge Base Article: 283795 - When you try to print to a network printer while you are using a guest or local user account, the print job may be placed in the queue but it may not be printed to the port (SPM or LPR). However, if an administrator logs on to the server and prints a test page, the subsequent print jobs may succeed from all clients until the print server is restarted. When you experience this problem, Event ID 45 may be reported in System Event log. 

Print Jobs Looping Continuously in Print Manager
Microsoft Knowledge Base Article: 137065 - Your computer is running Windows NT and has a printer connected to a local port. After you share the printer for use by other users and then issue a NET USE command from a command prompt of the same computer to establish a connection to your own printer, your own print jobs do not print and appear to loop continuously as recursive documents called "Remote Downlevel Document" in the print queue.

Print Jobs May Not be Deleted When Printed by Non- Administrator User
Microsoft Knowledge Base Article: 172288 - When you print to a Windows NT print server from a remote client, the print job may not be deleted and multiple jobs may stack up in the queue. Administrators and Print Operators may print normally. 

Print Manager: Unable to Configure Print Monitors
Microsoft Knowledge Base Article: 153477 - You are unable to create or select a print monitor. One of the following symptoms may occur: 

Problems Using Microsoft Windows NT 4.0 Lexmark Printers Drivers in Windows 2000
Microsoft Knowledge Base Article: 244869 - When you use the Microsoft printer drivers included in Microsoft Windows NT 4.0 Service Pack 4 or later for any of the Lexmark printer models listed later in this article on a Windows 2000-based computer, the following issues may occur: 

Random Access Violations in Programs with Third-Party Fonts 
Microsoft Knowledge Base Article: 269399 - Random access violations may occur in your programs after you print with third-party fonts. This problem occurs randomly only if the programs call the Gdi32.dll dynamic-link library 

Shared Printers Not Available After Upgrading to Windows 2000 Professional
Microsoft Knowledge Base Article: 221199 - When you upgrade a computer from Microsoft Windows 95 or Microsoft Windows 98 to Windows 2000 Professional, shared printers on the computer may not be accessible. 

Some Fujitsu DL Series Printers May Not Print Graphics Correctly
Microsoft Knowledge Base Article: 274295 - When you use a Fujitsu DL series dot matrix printer, you may experience either or both of the following symptoms: 

"Stop 0xC2 BAD_POOL_CALLER" Error Message on Print Server
Microsoft Knowledge Base Article: 258069 - A Windows 2000-based print server may randomly stop responding (hang) with a "Stop" error message on a blue screen. The stop code is 0xC2, and the first parameter is always 0x00000007.

Telcom Fax 3.0 Fax/Print Service Prevents Adding New Printer
Microsoft Knowledge Base Article: 155568 - When you attempt to add a new printer, you may receive the following error message: 

USB Printers Not Detected When You Start Windows
Microsoft Knowledge Base Article: 246354 - When you delete a USB printer from the Printers folder in Windows, the printer may not be redetected when you restart the computer. 

Windows 2000 Clients Cannot Print When You Set Certain System Policies in a Windows NT 4.0 Domain
Microsoft Knowledge Base Article  Q294706 - In a Microsoft Windows NT 4.0 domain, you can implement the system policy "Remove folders from Settings on Start Menu" for users or groups (which is located in the \User Policy\Shell\Restrictions\ folder). As a result, Windows 2000-based client computers on the domain are unable to print and the users receive the following error message: An error occurred during this operation. 

Windows 2000 Continually Prompts for the Proper Driver
Microsoft Knowledge Base Article: 236384 - When you connect a Windows 2000-based computer to a printer share on a computer running Microsoft Windows NT version 3.5x or 4.0, the Windows 2000-based computer may report that there is no suitable driver available, and prompt you for the proper driver 

Windows 2000 Direct and Indirect Printing over Infrared Port May Not Work
Microsoft Knowledge Base Article: 262286 - Neither direct nor indirect printing over an infrared (or IrDA) port may work. 

Windows 2000 Lprmon Does Not Restart Job If It Receives a "Nack" After Sending a Data File 
Microsoft Knowledge Base Article: 283014 -  When you use a printer in Windows 2000 that is defined as an LPR printer, a job can be lost if the LPR print monitor (Lprmon - receives a "NACK" response after the data file is sent. This can occur if the destination computer is UNIX-based and the /var folder is full. 

Windows 2000 Professional Prompts for Server CD-ROM When You Add Printer Drivers for Windows NT 4.0 or Windows 95/98
Microsoft Knowledge Base Article: 260107 - When you try to install printer driver support for Microsoft Windows NT 4.0, Microsoft Windows 95, or Microsoft Windows 98 on the Sharing tab in the Printer Properties dialog box, Windows 2000 Professional may prompt you for the Microsoft Windows 2000 Server CD-ROM

Windows 2000 Printer Driver Does Not Push Printer Configuration Changes to Windows NT 4.0 Driver
Microsoft Knowledge Base Article: 290874 - With the default Microsoft print drivers on a Windows 2000 print server, Windows NT 4.0 clients may not receive the printer configuration changes that are pushed down from the Windows 2000 print server. By default, the Point and Print function

Windows NT 4.0 Clients Cannot See Connect Link on Windows 2000 Internet Print Server
Microsoft Knowledge Base Article: 263593 - When you view printer properties from a Web page on a Windows 2000-based print server, the... 

You Cannot Create a TCP/IP Printer with a Host Name That Begins with Numbers
Microsoft Knowledge Base Article: 285041 - When you use a Windows 2000-based computer, you cannot create a TCP/IP printer that has a host name that starts with numbers. 

You Cannot Print to a Local Printer After Windows 2000 Service Pack 2 Is Installed 
Microsoft Knowledge Base Article: 319370 - After you install Windows 2000 Service Pack 2 (SP2), users without administrator permissions may receive the following error message when they try to print:


Epson Stylus Color 800 Incorrectly Detected as Incompatible During Upgrade
Microsoft Knowledge Base Article: 226375 - When you upgrade from Microsoft Windows 95 to Windows 2000, your Epson Color Stylus 800 printer is incorrectly detected as an incompatible printer. 

Epson Print Utilities Removed During Windows 2000 Upgrade
Microsoft Knowledge Base Article: 226380 - After you complete the Windows 2000 upgrade process on your computer that has Microsoft Windows 95 installed and uses an Epson Stylus Color 800 printer, the Epson print utility programs are no longer available. 

Graphics Print Poorly with Panasonic KX-P4420 Printer Driver Included with Windows 2000
Microsoft Knowledge Base Article: 262306 - When you print to a Panasonic KX-P4420 printer using the driver that is included with Windows 2000, the graphics quality is poor. For example, if you print a test page the Windows logo is unreadable. 

Installing Canon MultiPASS C5500 Driver May Result in Error Message
Microsoft Knowledge Base Article: 228214 - When you install the Canon version 2.30 driver for the Canon MultiPASS C5500 fax/printer, you may receive the following error message: 

Lexmark Optra Color 40 Printer Not Detected Automatically
Microsoft Knowledge Base Article: 223392 - Your Lexmark Optra Color 40 printer may not be detected and installed automatically by Windows 2000. Instead, the Add Printer Wizard may start so that you can choose a compatible printer driver. 

Printing to Xerox Workcenter 610 May Result in "Resource in Use" Error Message
Microsoft Knowledge Base Article: 228280 - When you print to a Xerox Workcenter 610 printer, you may receive the following error message: 

 

Entire contents
© 1999-2003 LabMice.net and TechTarget
All rights reserved

This site and its contents are Copyright 1999-2003 by LabMice.net. Microsoft, NT, BackOffice, MCSE, and Windows are registered trademarks of Microsoft Corporation. Microsoft Corporation in no way endorses or is affiliated with LabMice.net. The products referenced in this site are provided by parties other than LabMice.net. LabMice.net makes no representations regarding either the products or any information about the products. Any questions, complaints, or claims regarding the products must be directed to the appropriate manufacturer or vendor.