Microsoft KB Archive/199915

= Spoolss.exe Generates Dr.Watson Log =

Article ID: 199915

Article Last Modified on 2/25/2007

-

APPLIES TO


 * Microsoft Windows NT Server 4.0, Terminal Server Edition
 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Datacenter Server
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q199915



IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
When you run Windows on a print server, you may receive several Dr.Watson logs with Access violations in Spoolss.exe. When you view the Dr.Watson log, you see the fault after the function: Ordinal3578 was called. There is also information in the stack-back trace with pointers to mfc40u!Ordinal3578.

When you view the event log on this server, the following event log may be present:

Event Id: 2510

Source: SRV

Type: Error

Description: "The server service was unable to map error code 1722."



CAUSE
This problem can occur if the JetAdmin port monitor is corrupted or outdated.



RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, use either of the following methods:  Download the latest version of JetAdmin. To do so, visit the following HP Web site:

http://www.hp.com/cposupport/swindexes/hpwebjetad1880_swen.html

-or- Follow these steps:  Create LPR ports for all the JetDirect cards, open the printer properties for each printer, and then move the printers to their respective LPR port instead of using the JetAdmin port. Uninstall JetAdmin, and then restart the server. Stop the Spooler Service, and then remove the JetAdmin port monitor from the following registry path:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Monitors

 Close the registry and the restart the server.</li></ol>

NOTE: When you create the LPR Port on the Ports Tab in the Printer properties, specify the IP address of the printer (not the IP address of the Windows print server). Otherwise, the print documents will not print. Instead, the print documents will constantly spool at the print server and cause the print server to timeout.</li></ul>

HP no longer supports JetDirect. They now use SDI (Simple Device Installation) to install network printers. For more information, visit one of the following HP Web sites:

http://www.hp.com/cposupport/network ing/support_doc/bpj06765.html

<div class="moreinformation_section">

MORE INFORMATION
To obtain more information on JetAdmin and the latest version of HP's JetAdmin software, please refer to the following HP Web site:

http://www.hp.com/cposupport/docindex/hpjetadmin1876.html

Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kbprb KB199915

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.