Event ID - 67

Event Id	67
Source	Microsoft-Windows-PrintSpooler
Description	The print spooler failed to cache print connection %1. This can occur because there are insufficient system resources. No user action is required.
Event Information	According to Microsoft : Cause : This event is logged when the print spooler failed to cache print connection. Resolution : Check Windows resources Windows printing could not allocate sufficient resources for an operation or was processing an upgrade. No immediate action is required. If problems persist, 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, or you can use Resource Monitor to determine (in real time) which applications or services are utilizing too many system resources. To generate a System Diagnostics Report, which will present system information collected for 60 seconds, use the procedure in the following section ("Generate a System Diagnostics Report"). To use Resource Monitor to monitor system resources in real time, use the procedure in the "Start Resource Monitor" section. To perform these procedures, you must have membership in Administrators , or you must have been delegated the appropriate authority. Generate a System Diagnostics Report 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. Start Resource Monitor To start Resource Monitor: Important : Resource Monitor stops collecting information while a System Diagnostics Report is being generated. To start collecting information after a System Diagnostics Report has completed, click Start in Monitor . 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 /res and then press ENTER. Resource Monitor will start running. Four scrolling graphs in the Resource Overview pane display the real-time usage of CPU, Disk, Network, and Memory. Four expandable sections below the graphs contain process-level details about each resource. Click the resource labels to see more information, or click a graph to expand its corresponding details. You can use the real-time usage information to identify top resource consumers. Click a column heading to sort the data in the table by that column; click the column heading again to reverse the sort order. 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.
Reference Links	Event ID 67 from Source Microsoft-Windows-PrintSpooler

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught