Event ID 370 — Print Spooler Status

Updated: January 8, 2008

Applies To: Windows Server 2008 R2

This is preliminary documentation and subject to change.

red

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

Event Details

Product: Windows Operating System
ID: 370
Source: Microsoft-Windows-PrintSpooler
Version: 6.1
Symbolic Name: MSG_PACKAGE_REGENERATION_FOR_DRIVER_FAILED
Message: 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.

Resolve

Retry printing or restart the print spooler

Windows Printing encountered an error; however, it may retry the action or work around the problem. If printing is not working correctly, possible resolutions include:

  • Retry printing.
  • Examine the error code returned by this event. For a list of system error codes and a brief explanation of what they mean, see the Microsoft Web site at http://msdn2.microsoft.com/en-us/library/ms681381.aspx
  • Start or restart the Print Spooler service, using the following procedure.

    Warning: Restarting the Print Spooler causes all print jobs to be restarted. After restarting the Print Spooler service, you might need to reset some printers or turn them off and then turn them back on. On an active print server, perform this procedure outside of normal business hours or during scheduled maintenance time, if possible. Before performing this procedure, take all printers offline and wait for all print jobs to becompleted, or pause all printers and wait for all Active print jobs to be completed.

    1. In the Administrative Tools folder, open the Services snap-in.
    2. Locate the Print Spooler service in the list of services, and then confirm that its status is Started. If its status is not Started, select the service and then click Start on the Action menu.

      Note: You can also do this from an elevated Command Prompt window by typing the following command: net stop spooler && net start spooler

    In some instances, you might receive Error 1068 â€“ "The dependency service or group failed to start" – when attempting to start the print spooler. This can happen if the Print Spooler service relies on other services that are not running. To resolve this issue, use the following procedure:

    1. In the Services snap-in, right-click Print Spooler and then click Properties.
    2. Click the Dependencies tab. The first box lists all of the system services that must be running for the Print Spooler to start. These are the dependencies.
    3. Make a note of each service, click OK, and then start each service that the Print Spooler service depends on, if the service is not already started. If a particular service was not already started, right-click it, click Properties, and then confirm that the Startup type is Automatic.

Verify

Perform the following tasks to verify that you resolved the problem:

  • Print the document again.
  • If the print server logs spooler information events, look for Print Spooler Event 10 after printing, and then examine the document to confirm that it printed correctly.

Related Management Information

Print Spooler Status

Printing Infrastructure

Show: