question

Hello,

Exactly same problem for me.

Regards,

Nice to know I'm not alone as I don't find anything on internet so far... very strange for something that appears to be a general problem

@ITBogaertsGL-2940

What is the precise error on the client system?

I'm hoping you are reviewing the Windows PrintService / Admin and / Operational events
Here's how to enable Operational. https://www.papercut.com/kb/Main/LogPrintJobsInEventViewer

Make sure you have Port 135 open on the print server. It's a new requirement from Microsoft.

You have been keeping the print server patched, correct? I just want to confirm you at least had the September updates on the print server prior to installing the February update.

Thanks

I am also facing same Problem with update KB5010359.

after uninstall this update printer working fine.

But Next day again found update installed on server.

I had the same problem
Then I installed a brand new server from scratch
installed all updates and tried again an that worked
The message on the client is this one

error 0x00000bbb

Te message in operational is this

But I doubt this has anything to do with it

Hi @krisgeerts-1549

Event 812 does have nothing to do with it. The .SHD file is a schedule file the spooler will use to schedule the print job. Error 2 is file not found. So guess what, the spooler tried to delete the scheduling file and it was not there.

Error 0xbbb, now that more like it.

C:\>winerror 0xbbb
3003 ERROR_SPL_NO_STARTDOC

Unfortunately not that helpful, but the application can't create the job.

Is this Windows event from the client machine?

The spool folder path for printer connections is c:\Windows\System32\spool\SERVERS[YourServerName] so I am guessing this log is from the print server.

If this is not the client logs, please enable the Operational logs and review both the Admin and Operational logs when this fails.

We might need to enable the super secret PrintService / Debug logs but come back and I will give you those details if we need to go there.

Thanks

This is indeed from the client
I don't think it even comes to the server.
There is nothing there

I can use the printer on the server
but if I want to connect to the spooler from the server it self , it fails

Hi all,
I have the same problem with KB5010351 on Windows server 2016 and KB5010351 on Windows server 2019. When this update are installed on printserver, it is impossible to print to shared printers.
Operation log from printserver says that the print spooler can not delete SHD file with error 0x2. But no SHD file with this name exists at that time.

Any help is appriciated.

Thanks
Bohdan Biječek

Indeed, The only thing that worked for me was a complete reinstall from a iso , updated it with all KB including the 'faulty' and placed the printers on it
What is in the iso now is not the same as the updated server over time ; that's for sure ...even if they have the same KB's applied , its different.
But that is as far that I can prove anything for now .