Event ID 354 — 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.
|Product:||Windows Operating System|
|Message:||%1 initialization failed at %2. Error: %3. This can occur because of system instability or a lack of system resources.|
Restart the server or troubleshoot hardware problems
Determine whether the computer is low on system resources such as CPU resources, disk I/O performance, or memory. To identify what is causing the system to be low on resources, you can generate a System Diagnostics Report by using Reliability and Performance Monitor.
To perform this procedures, you must be a member of the local Administrators group on the affected computer, or you must have been delegated the appropriate authority.
To collect system information for 60 seconds and generate a System Diagnostics Report:
- Open an elevated Command Prompt window. (Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.)
- At the command prompt, type perfmon /report and then press ENTER. Reliability and Performance Monitor will start collecting data to create the System Diagnostics Report.
- When the report is ready for viewing, locate the Diagnostic Results section of the report and then check for any warnings (indicated by Warning in the report). You can follow links to additional help on resolving warnings from this section. In addition, you can expand each category in the Basic System Checks section to see more details about why warnings appear. Also, the Performance section provides process-level details about top consumers of resources.
If you cannot resolve the issue after reviewing the recommendations of the System Diagnostics Report, possible resolutions include:
- Notify users, and then restart the print server.
- Use hardware diagnostic utilities to troubleshoot potential hardware issues.
- Restore the print server from a stable backup.
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.