Share via


Print Spooler Status

Applies To: Windows Server 2008 R2

This is preliminary documentation and subject to change.

Print Server Status controls basic operations such as initializing the spooler, creating threads, and reading the registry.

Events

Event ID Source Message

99

Microsoft-Windows-PrintSpooler

The print spooler encountered a fatal error while executing a critical operation (%1, error %2) and must immediately terminate. Try to manually restart the print spooler service (from Control Panel | Administrative Tools | Services or from an elevated command prompt running: net start spooler).

312

Microsoft-Windows-PrintSpooler

Form %1 was added. No user action is required.

313

Microsoft-Windows-PrintSpooler

Form %1 was removed. No user action is required.

319

Microsoft-Windows-PrintSpooler

Printer %1 failed to initialize because a suitable %2 driver could not be found. The new printer settings that you specified have not taken effect. Install or reinstall the printer driver. You might need to contact the vendor for an updated driver.

349

Microsoft-Windows-PrintSpooler

The print spooler failed to create a symbolic link between HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Print\\Printers and HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\Print\\Printers. Error %1. This only affects older applications, but is probably a sign that the system itself is in a poor condition or that the print spooler does not have the proper registry permissions.

354

Microsoft-Windows-PrintSpooler

%1 initialization failed at %2. Error: %3. This can occur because of system instability or a lack of system resources.

361

Microsoft-Windows-PrintSpooler

Printer %1 failed to initialize its ports. Win32 error: %2. This error usually occurs because of a problem with the port monitor. Try recreating the port using a standard TCP/IP printer port, if possible. This problem does not affect other printers.

362

Microsoft-Windows-PrintSpooler

The print spooler failed to cache print connection %1. This can occur because there are insufficient system resources. No user action is required.

363

Microsoft-Windows-PrintSpooler

The print spooler %1 failed to start. To determine the cause of this error, examine the preceding events in the Event Log.

366

Microsoft-Windows-PrintSpooler

The print server security descriptor for %1 is invalid. The default print server security descriptor will be used.

368

Microsoft-Windows-PrintSpooler

The print spooler failed to verify printer driver package %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive. The print spooler will try to regenerate the driver information from the driver store, which is where drivers are saved before they are installed. No user action is required.

369

Microsoft-Windows-PrintSpooler

The print spooler failed to verify printer driver package for environment %1. Win32 system error code %2. This can occur because of insufficient memory or other system failures. No user action is required.

370

Microsoft-Windows-PrintSpooler

The print spooler failed to regenerate the printer driver information for driver %1 for environment %2. Win32 system error code %3. This can occur after an operating system upgrade or because of data loss on the hard drive.

372

Microsoft-Windows-PrintSpooler

The document %1, owned by %2, failed to print on printer %3. Try to print the document again, or restart the print spooler.
Data type: %4. Size of the spool file in bytes: %5. Number of bytes printed: %6. Total number of pages in the document: %7. Number of pages printed: %8. Client computer: %9. Win32 error code returned by the print processor: %10. %11

373

Microsoft-Windows-PrintSpooler

The spooler has detected that a component has an unusually large number of open Graphical Device Interface (GDI) objects. As a result, some enhanced metafile (EMF) print jobs might not print until the spooler is restarted.

Print Spooler Service

Printing Infrastructure