Retry printing or restart the print spooler.
Windows Printing encountered an error; however, it may either retry printing or work around the problem. See Additional Information section for fix.
If printing is not working correctly, possible resolutions include:
Retry printing.
Examine the error code returned by this event.
Warning: Restarting the print spooler causes all print jobs to be restarted. Additionally, you might need to reset or turn off and then back on some printers after restarting the print spooler. 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 be completed, or pause all printers and wait for all Active print jobs to be completed.
In the Administrative Tools folder, open the Services snap-in.Locate the Print Spooler service in the list of services, and 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 and 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 service. This can happen if the Print Spooler service relies on other services that are not running. To resolve this issue, use the following procedure:
In the Services snap-in, right-click Print Spooler and select Properties. Click the Dependencies tab. The first box lists all of the system services that must be running for Print Spooler service to start. These are the dependencies. 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 is not already started, right-click it, click Properties, and then confirm that the Startup type is Automatic.
This key is missing by default. To correct this issue, you can do one of the following:
Disable the monitoring rule
Create the registry key manually.
Start Registry Editor and navigate to HKEY_USERS\S-1-5-18\Printers
Create a new key named Connections
| Target | Microsoft.Windows.Server.10.0.PrintServerRole | ||
| Category | Alert | ||
| Enabled | False | ||
| Event Source | Microsoft-Windows-PrintService | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
| ||
| Event Log | Microsoft-Windows-PrintService/Admin |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.EventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home
<Rule ID="Microsoft.Windows.Server.10.0.PrintServer.PrintSpoolerService.PrinterConnectionsStatus.System.Alert.3.4.5" Enabled="false" Target="Microsoft.Windows.Server.10.0.PrintServerRole" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Microsoft-Windows-PrintService/Admin</LogName>
<Expression>
<And>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>^(602|603|604)$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">Microsoft-Windows-PrintService</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.10.0.PrintServer.PrintSpoolerService.PrinterConnectionsStatus.System.Alert.3.4.5.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>