Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 513 Source: PrintService
Group Policy was unable to add per computer connection \\<server>\<printername>. Error code 0x2. This can occur if the name of the printer connection is incorrect or if the print spooler cannot contact the print server.
|English: Request a translation of the event description in plain English.|
According to TD380098, the administrator should try these suggestions:
- Confirm that the Universal Naming Convention (UNC) name of the printer connection is correct and available from the affected computer or user.
- Use Group Policy Results to confirm that the appropriate Group Policy object (GPO) is applied to the affected computer or user.
Error code 0xbc4 - From support forum:
I may have found my solution. It appears the printer in question was added using a printui.dll command, and not through Group Policy as stated in the event log. I verified this by running the following command:
rundll32 printui.dll, PrintUIEntry /ge
I got rid of it with the following:
rundll32 printui.dll, PrintUIEntry /gd /n\\printserver\printername
I managed to find this by searching for the printer name in the registry, and finally stumbling on the key at hkey_local_machine\software\microsoft\windows nt\currentversion\print\connections. That "connections" key seems to relate to computer-level printer additions via printui.dll commands.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated