Printing Problems Caused By Fax Software (158751)
The information in this article applies to:
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
This article was previously published under Q158751 SYMPTOMS
The Spooler Service stops running on a Windows NT computer and the
following error occurs:
On the print server, the following error appears in the system log when
users attempt to print:
Event ID: 2510
Source: SRV
Type: Error
Description: "The server service was unable to map error code 1722."
-or-
When you attempt to print on a computer running Windows NT Workstation the
following error message appears:
An application error has occurred and an application error log is being
generated.
Spoolss.exe
Exception: access violation (0xc00000005), Address: <Hex address>
CAUSE
These error conditions during printing may occur when third-party fax
software is installed either on an Windows NT print server computer or on
a computer running Windows NT Workstation.
RESOLUTION
Some fax software programs modify the registry. It might become necessary
to remove the fax software in order to print. However, some programs do
not clean up the registry when they are removed. Check the registry to see
if there are entries added by a fax software program that might be causing
one of the previous errors.
WARNING: Using Registry Editor incorrectly can cause serious problems that
may require you to reinstall your operating system. Microsoft cannot
guarantee that problems resulting from the incorrect use of Registry
Editor
can be solved. Use Registry Editor at your own risk.
- Start Registry Editor (Regedt32.exe) and locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Pri - Look for any entries that might be related to a fax software program.
- Delete these entries.
NOTE: Do NOT delete any of the subkeys of the Print key, such as
Environments, Forms, Monitors, Printers, and Providers.
NOTE: The symptoms described in this article may also be caused by
third party port monitor software, and it may be necessary to remove
the port monitor from the registry using the steps above.
Modification Type: | Major | Last Reviewed: | 7/13/2006 |
---|
Keywords: | kbprb kbprint KB158751 |
---|
|