Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 602 Source: PrintService
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-1482476501-362288127-839522115-8193\Printers\Connections\,,"printername". This can occur if the key name or values are malformed or missing.
|English: Request a translation of the event description in plain English.|
According to ME2457866, if you get this event after you log on to a Windows 7-based or Windows Server 2008 R2-based computer, a hotfix is available to fix the problem.
From a support forum: "I was getting this in our Terminal Services (TS) servers. The constant errors and spooler service crashing were mainly caused by the 3rd party printer monitors installed with the drivers. 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
2 - Uninstall all printers from the TS server and use the new Easy Print feature on the 2008 R2
We tried the 1st solution and still had problems because the printers installed by GPO were constantly bringing back the 3rd party monitors because they were on a print server. So solution #2 was the way to go, and it pretty much fixed everything."
From a support forum: "I did something that's a bit risky, but it worked. I searched through the registry for mentions of the obsolete printer, and as carefully as I could, deleted the entries. After that, the event viewer errors stopped."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated