Solved

Event ID 4 Failed to reopen existing printer connection

Posted on 2009-05-12
3
3,610 Views
Last Modified: 2013-11-10
Every night I get this event for every server on my network:

Message:  System log generated Warning Event 4 on lsmessaging.lafeber
For more information see http://www.eventid.net/display.asp?eventid=4&source=Microsoft-Windows-SpoolerWin32SPL

Log: System
Type: Warning
Event: 4
Agent Time: 02:09:29  12-May-09
Event Time: 00:09:29  12-May-09 UTC
Source: Microsoft-Windows-SpoolerWin32SPL
Category: None
Username: N/A
Computer: messaging.PS.local
Description: The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-18\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.

When I look on the website eventid.net they say that I must create this registry value. But when I do this the event won't go away. What can I do to get rid of this event?
0
Comment
Question by:emieldmz
  • 2
3 Comments
 
LVL 5

Accepted Solution

by:
DNadon57 earned 500 total points
ID: 24381488
Microsoft has a hotfix for this problem.  It occurs in error when the SYSTEM account accesses the WMI Win32_Printer class.  See the technet article http://support.microsoft.com/kb/967159 
0
 

Expert Comment

by:Kwmulligan
ID: 32997569
I have a similar problem in the X64 version of Windows Server 2008

The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21\Printers\Connections\,,Y-Resource.,07 Tempe Copier BW. This can occur if the key name or values are malformed or missing.
0
 

Expert Comment

by:Kwmulligan
ID: 32997580
2008 R2
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Know what services you can and cannot, should and should not combine on your server.
Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

828 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question