Home > Print Spooler > The Print Spooler Could Not Open The Registry Key

The Print Spooler Could Not Open The Registry Key


If i go to User Accounts in the control panel, in addition to the jdoe and John, there are two more...Guest and ASP.NET Machine account. The Universal driver PCL 6 is working fine. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server. Also have 808 errors along with 7031 which is the print spooler stopping. navigate here

Since it was installed last week we have no morespooler crashes. Regards Thursday, September 30, 2010 1:59 PM Reply | Quote 0 Sign in to vote The patch did nothing for us. Perform local &cloud backup in the same step, and restore instantly—anytime, anywhere. Public <--- Normal jdoe <--- Normal John Doe <--- Why 3 John accounts. https://social.technet.microsoft.com/Forums/office/en-US/5fa57c02-6b50-44e0-86d4-624fdb20e258/printer-errors-on-new-server-2008-r2-remote-desktop-server?forum=winserverTS

The Print Spooler Could Not Open The Registry Key

I can have the users go for almost a week with no errors, the next time it'll error out 5 times in an hour. Wednesday, August 11, 2010 4:08 PM Reply | Quote 0 Sign in to vote Hello Ryan, i have an activesupport-case with hp, because we are using the hp universal printing driver. About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up

C:\>winerror 0xc1 193 ERROR_BAD_EXE_FORMAT Alan Morris Windows Printing Team Edited by Alan Morris Thursday, December 16, 2010 6:04 AM Monday, December 13, 2010 6:00 PM Reply | Quote 0 The hotfix hepled a little bit. My current profile jdoe is definitely a member of the Administrative Group. Group Policy Was Unable To Add Per Computer Connection 513 In first, the event ID 602error appearsandnext it'sthe event ID 808.

I have enabled "printer dirver isolation" so, the crash is not impacting the work of the other users on the server. Easy Print Feature On The 2008 R2 Make sure your Windows 7 userid is a member of the Administrator's group and then go to Computer, right click, Properties and then Advanced (left side of the window). Event source: Kernel-general, event id: 5 {Registry Hive Recovered} Registry hive (file): '\??\C:\Users\%username%\ntuser.dat' was corrupted and it has been recovered. http://blog.res.com/2011/02/11/the-print-spooler-failed-to-reopen-an-existing-printer-connection-because-it-could-not-read-the-configuration-information-from-the-registry-key/ This seems to be able to keep it going, but I can't watch the server all day possibly waiting for that ISD icon to show up in the task bar.

Others from MSread this when evaluating the issue. Regards Tuesday, August 24, 2010 7:57 AM Reply | Quote 0 Sign in to vote Have a TS Web Access 2008 farm with about 70+ internal/external users. Thursday, August 12, 2010 6:13 PM Reply | Quote 0 Sign in to vote Hello, same problem as here with hp universal driver. Legal | Privacy | Success Center | Sitemap Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses!

Easy Print Feature On The 2008 R2

There are 2 way to solve that problem : 1 - Go into the registry of the TS Server to configure all the printers to use the windows default print monitor Terminal servers are running 2008r2 and the DC is SBS2008 Sp2. The Print Spooler Could Not Open The Registry Key All Rights Reserved Privacy & Terms Home | Site Map | Cisco How To | Net How To | Wireless |Search| Forums | Services | Donations | Careers | About Retrieving Csr Cache Information For Printer Failed Error Code 0x2 A temp solution for my system is right now the following: I planned an task on my three Windows Terminal Servers with just a simple net start spooler batch file -

There is a text based report.wer file you can open in notepad. http://homecomputermarket.com/print-spooler/print-spooler-service-is-not-running.html Print the document again. I can't believe this issue isn't solved yet. I do not know why they should "relate" to other printers, though. Easy Print Server 2012

Thursday, May 27, 2010 9:02 AM Reply | Quote 0 Sign in to vote I've had the same issues on a 2008 R2 TS Server. I tried the spool restart, driver updates, registry tweaks, etc., but problem kept reappearing on and off. If you cannot remove the driver, stop the print spooler service and try removing the driver again. his comment is here Related Management Information Printer Connections Status Printing Infrastructure Show: Inherited Protected Print Export (0) Print Export (0) Share IN THIS ARTICLE Is this page helpful?

It probably can be deleted. I have a bunch of 602's in the event log and my spooler service will be crashed at some points. I can't use the new Easy Print option as one of the programs saves and uses printer name and we can't have the printer name changing all the time (session numer).

You should not see this.

Alan Morris Windows Printing Team Friday, October 29, 2010 4:01 PM Reply | Quote 0 Sign in to vote Hi Alan Like others above, I too have this issue and realise Print spooler will fail sporadically on both Server 2008 R2 servers. Regards Tuesday, February 08, 2011 9:03 PM Reply | Quote 0 Sign in to vote We are also experiencing 602 events. Any news from MS, I'm having the same problem on 3 Remote Desktop Hosts :( Monday, May 17, 2010 7:33 PM Reply | Quote 0 Sign in to vote What is

If the app is 32bit find out if they have64bit available. Can i send per mail to you? The thing is how to get the MS drivers back in the list .... ??? http://homecomputermarket.com/print-spooler/reinstall-print-spooler-windows-7.html Proposed as answer by tufillaro Friday, June 18, 2010 11:06 AM Thursday, June 17, 2010 7:46 AM Reply | Quote 0 Sign in to vote Good Morning The problem is not

Is it usefull to contact PSS and make a case of it or just wait? You should not disable UAC. Now we could check the RES PowerFuse user eventlog for printer connection failures: printers were connected without any errors or warnings, superb. If so, i'll also install it on our 4 terminal servers.

This is interesting. Having used the event viewer, I am now on a quest to solve my next issue which is the following error. Also, i've uninstalled all the printer drivers that are not in use anymore on this server. You can use windiff/beyond compare tool to verify it with a clean machine. ~Cheers http://blog.helpforsure.info Tuesday, April 13, 2010 6:48 PM Reply | Quote 0 Sign in to vote Hello

Wednesday, March 17, 2010 5:17 PM Reply | Quote 0 Sign in to vote Hello,I'm in the same situation. Which hP driver are you using?