2019 Server - Printer Installation Wizard fails "access is denied"

Question

I cannot add a printer using an existing port and driver in Print Management. I get "Access is denied". This is a recent issue. That print servers has dozens of print queues.

Event log shows
"The print spooler failed to share printer RICOH Aficio SP C830DN PCL 6 with shared resource name RICOH Aficio SP C830DN PCL 6. Error 5. The printer cannot be used by others on the network."

I have looked that up but the posts are extremely old and do not offer much.z

Any assistance is appreciated.

Answer 1

We are having exactly the same problem, but on Windows Server 2012. I can add printers but cannot share them, failing with the error message: "Unable to install printer. Access is denied."

If you turn off sharing (which I know is no good) then I am sure the printer will install. However, that is no good on a network printer!

Sharing fails whatever the share name is and permissions have not been changed - the printer can be added by the 2 or 3 admin accounts I have tried with.

This print server has 80+ printers on and the problem has only been noticed this week. I thought it might be the latest Windows Updates so uninstalled all of them but that has not helped.

Is there anyone who can help? Thanks.

Answer 2

After days of troubleshooting without finding any solution i was able to solve the issue with a veeam restore of the vm. We had to add a few new printers but now everything is working agian.
I couldn't find the solution and for me this procedure was more time efficient.
Not very satisfactory - but it works.

Answer 3

HI

We can enable SetupAPI log first, then install printer again, When the problem happened, are there any event logs in below location on session host w2012r2?

event viewer\windows logs\
application
security
system
event viewer\windows logs\applications and services logs\microsoft\windows\printservice
SetupAPI.dev.log

SetupAPI Logging Registry Settings
https://learn.microsoft.com/en-us/windows-hardware/drivers/install/setupapi-logging-registry-settings

Answer 4

I found a solution!!!, There was some issue with folders permission: drivers,DriverStore & DRVSTORE. I have replaced owner to local administrator with disable inheritance under System32.