Server 2008 Print Spooler Warning

[Steve G]

I get this error in the system event log on my 64Bit 2008 Server Domain
Controller. The user sid belongs to an administrator who to my knowledge had
never previously logged onto the server? If I log on as this user the errors
stop and you can see the appropriate registry key. The error messages restart
as soon as I logoff. In any event the error is logged every 30 seconds and we
eventually have to restart the spooler as it slowly bogs down. The errors
started after we installed a new printer which did not have ceritfied
drivers. I have uninstalled and re-installed all the printers under that
specific user as well as the default administrator.

"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-2591247208-3686103071-4132917375-1117\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."

[Pegasus \(MVP\)]

- Which account does the print spooler service run on?
- What is the permission structure of this key and its subkeys?

[Mervyn Zhang [MSFT]]

According to your description, I understand that:

The error "The print spooler failed to reopen an existing printer
connection" related to an administrator who had never previously logged
onto the server were logged on your Windows Server 2008 Domain Controller.
But the error stops if you logon as this user.

If I have misunderstood the problem, please don't hesitate to let me know.

This issue may be related to the "Point and Print" feature. Please try the
suggestions in the following article.

The print operation is unsuccessful when you use the "Point and Print"
feature on a client computer that is running Windows Server 2008, Windows
Vista Service Pack 1, or Windows Server 2003
http://support.microsoft.com/?id=952832

Please also try to clear all printing jobs and restart spooler services.

If the issue persists, please help to collect the following log for
research.

The MPS Reporting Tool is utilized to gather detailed information regarding
a systems current configuration. The data collected will assist you with
fault isolation.

A . Please download MPS Reporting Tool (MPSRPT_PFE.EXE) from the following
link:
(http://www.microsoft.com/downloads/d...0eac-720f-4441
-9ef6-ea9f657b5c2f&DisplayLang=en)

Please note: The link may be truncated when you read the E-mail. Be sure to
include all text between '(' and ')' when navigating to the download
location.

B . Right click MPSRPT_PFE.EXE and select Run as Administrator to run this
tool, and you will see a Command Window start up.

C . Please type Y with the message of <Include the MSINFO32 report?
(defaults to Y in 15 seconds)[Y,N]?

D . When the tool is done you will see an Explorer Window opening up the
%systemroot%\MPSReports\Setup\Reports\cab folder and containing a
<Computername>MPSReports.cab file. After collecting, please use Windows
Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then
give me the download address.

[Steve G]

The printer is installed on a Domain Controller. I don't know how I could
access the Local User group, since users are controlled by Active Directory.
Is their something I am missing?

[Alan Morris [MSFT]]

the error is not really an error. There is no key for that user but the
spooler thinks there is one. Possible due to roaming profile. You can add
the key onto the DC under the Users sid key but I'd personally not waste the
time.

[Mervyn Zhang [MSFT]]

Is the problem administrator a Domain User account? If not, please try to
add it to Domain User group.

At the same time, let’s try to check the "%windir%system32\spool\PRINTERS"
folder permission.

Click Start, type "%windir%system32\spool", right-click PRINTERS folder,
choose Properties, switch to Security tab, make sure the Administrator
group is listed and have full control permission.

Log on and log off the account to test. If the issue continues, please
clear all printer tasks and test again.

[Steve G]

You can't create a sid key for a user not logged directly on the DC in
registy. When that user is logged on the DC the key is created automatically
and the error stops, but restarts as soon as they log off. It does cause the
print spooler to slowly bog down and then it hangs.

[Steve G]

The user is a member of both Domain Users and Domain Administrators. On the
security tab of the printers folder it shows Domain Admins as having full
control, however if you go to the effective permissions tab in advanced and
look at Domain Admin no permissions are inciated. The same is true for
Domain Users but they are all ticked for System.

I am begining to think it must have to do with a failed driver install. When
I am logged on the DC in the sytem log you see an one event 7036 "Windows
module installer entered the running state". When the problem user is logged
on the 7036 event is recorded repeatedly saying the module enterd the stop
state and next saying it has entered the start state - cycling over and over
again. It may still be something like the point and click issue we looked at
earlier even though his laptop is Windows XP and the print server is a DC.

[Mervyn Zhang [MSFT]]

Based on current information, it mostly caused by printer driver. If the
printer was installed by GPO or scripts, please try to remove it on clients
and reinstall it manually on Windows XP to check if there is any error.

Please also try to clear printer spooler on Windows XP. Open CMD, run the
following commands.

net stop spooler
del %SYSTEMROOT%\system32\spool\PRINTERS\*.* /q /s
net start spooler

Restart clients and test.

[Mervyn Zhang [MSFT]]

Would you mind letting me know the result of the suggestions? If you need
further assistance, feel free to let me know. I will be more than happy to
be of assistance.

[Steve G]

Since this is going to involve a lot of work to uninstall all the network
printers from the server and all the workstations and then re-install them, I
have asked Konica to provide Windows Server 2008 cetified drivers. Right now
we are using a Beta version since that is all they have!

To miniumize the impact of Printer down time we won't do it until next
weekend. I will let you know then.

[Mervyn Zhang [MSFT]]

I understand you have to postpone the troubleshooting to minimize the
impact.

Please take time to test, if there is anything we can do for you, please
let us know.

[Mervyn Zhang [MSFT]]

Have you had time to troubleshoot this issue? If there is anything that I
can do for you on this issue, please do not hesitate to let me know and I
will be happy to help.

[Alan Morris [MSFT]]

there is a KB on a similar issue, unclear if this is exactly your scenario

http://support.microsoft.com/kb/952832

Log Name: Application
Source: SpoolerWin32SPL
Event ID: 4
Level: Error
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

[RobertAndersen]

I'm having this exact problem.

Steve-

Did you get this resolved by reinstalling the printers on the server and the workstations? I hope there's an easier way. It's only a problem with one users account, so I'd really like to avoid inconveniencing my entire organization.

Any advice would be greatly appreciated! Thanks!
-Rob