Print Spooler Hangs on Windows 7 with Event ID 372 - RPC error

The network configuration is: Windows SBS 2003 server with Windows 7 32-bit clients.  There are other servers on the network, but the SBS server is acting as the print server.  Periodically various workstations will be unable to print to any printer.  The print spooler service appears to be running normally, but the event log shows the following error message:

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          4/21/2010 12:09:57 PM
Event ID:      372
Task Category: Printing a document
Level:         Error
Keywords:      Classic Spooler Event,Document Print Job
User:          WSPLAW\JStartz
Computer:      WSP53.WallerSmithPalmer.local
Description:
The document Local Downlevel Document, owned by jstartz, failed to print on printer {88F50B3B-808D-4015-9C4B-F340B5609B10}. Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 0. Number of bytes printed: 0. Total number of pages in the document: 0. Number of pages printed: 0. Client computer: \\WSP53. Win32 error code returned by the print processor: 1722. The RPC server is unavailable.

Restarting the print spooler service on the workstation solves the problem temporarily, about 90% of the time. Sometimes, however, it requires restarting the spooler service several times, or even restarting the computer.  Also, it usually seems to happen with the first print job of the day, although we are not 100% sure that is the case.

This is very annoying and disruptive to our users at this site, and we've been unable to find any answers to this one so far. I have tried changing the registry settings on the workstations so that print jobs are rendered on the server rather than the workstation, but that doesn't seem to have helped.

Any ideas would be appreciated!
LVL 39
Hypercat (Deb)Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

phLOxRSACommented:
Greetings hypercat!

I'm going to be very impersonal and merely give you a link to the error, in the hopes that you haven't tried anything there yet. Goodluck!

http://technet.microsoft.com/en-us/library/dd393167(WS.10).aspx
0
Hypercat (Deb)Author Commented:
Thanks for the post. There was one thing on that article that I hadn't checked...Unfortunately, it didn't turn out to be the issue.
0
holtzerCommented:
I have the exact same problem, did you find any solution yet?

Nom du journal :Microsoft-Windows-PrintService/Admin
Source :       Microsoft-Windows-PrintService
Date :         2010/04/22 10:10:54
ID de l’événement :372
Catégorie de la tâche :Impression d’un document
Niveau :       Erreur
Mots clés :    Événement de spouleur classique,Travail d’impression de document
Utilisateur :  SHDM0\Boylyn
Ordinateur :   SHDM-051.shdm.org
Description :
Échec de l’impression du document Document local de bas niveau appartenant à Boylyn sur l’imprimante {FF8C5F3B-75D4-4DD6-A1FF-907C8D4B43A2}. Essayez de réimprimer le document ou redémarrez le spouleur d’impression.
Type de données : RAW. Taille du fichier spouleur en octets : 0. Nombre d’octets imprimés : 0. Nombre total de pages dans le document : 0. Nombre de pages imprimées : 0. Ordinateur client : \\SHDM-051. Code d’erreur Win32 renvoyé par le processeur d’impression : 1722. Le serveur RPC n’est pas disponible.
0
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Hypercat (Deb)Author Commented:
No, holtzer, I haven't found a solution yet. This has been going on at my client for a couple of months now, ever since we upgraded them to Windows 7. I've done quite a bit of searching already and I'm getting desperate.
But thanks for posting the error message in French! I love testing my admittedly rusty language skills against some real-life examples.
0
holtzerCommented:
Well it was hard to find the right translation cause in french the support for this is minimal so i though that i could post it so it can be searchable for people that only know the french error message
0
Hypercat (Deb)Author Commented:
That was a good idea.  I just hope we find some answers.
Quick question for you - are you using Windows Small Business Server 2003 also?  If not, what operating system are you using on the print server end?
0
holtzerCommented:
We have AD 2003 with some windows 2000 Server and some windows 2003, though the printers are all shared on the win2k server

It's weird though, only 1 of all windows 7 Pro has the problem, other have other kind of problem but not has annoying as this one, temporary i installed a local printer directely linked to the printer the user is using and it's the perfect backup but i don't want to install local printers to all users with windows 7
0
phLOxRSACommented:
Hey it's me again.
Do you guys mind sharing what printers it is you are using? Maybe the have something in common?
0
Hypercat (Deb)Author Commented:
In our case, the site has a mixture of Canon Imagerunners and HP Laserjet printers. The problem doesn't appear to relate to the printer model. When the problem happens, the user can't print to any of the network printers, regardless of make or model.
0
phLOxRSACommented:
So we know it's NOT driver related and NOT model specific, neither is it OS specific.
Perhaps it's the ports?
I found this: http://www.annoyances.org/exec/forum/win2003/t1122974217

It's not the exact same error that you have, but maybe it's worth trying. Here's the summary.

Go to Printers from Control Panel. Right click-->Properties on the Printer having the issue.
Go to Ports Tab, add Port.
Choose "Standard TCP/IP Port" and click "New Port...".
Click Next, then enter the IP address of your printer, then Finish.
Click Close. Ensure that the checked row has a description of "Standard TCP/IP Port", not "HP Standard TCP/I...".
Click Apply and Close
0
holtzerCommented:
Local printers work just fine, the problem appear when we are using a shared printer , in my case we have only HP Laserjets and it work fine for all users not under win7 and not all win7 user are getting the problem at the same time.

I noticed something too, when the problem arise, check if the driver is selected on the shared printer, cause mine is not, it's blank and i have to restart the spooler couple of time before i can see the driver name in the drop box (which is in gray for none admin user but still should be there)

but if I had a local (tcp/ip port) directely on the computer we can print

I feel it's the communication between win2k / win2k3 and win7 spooler that is the problem
0
holtzerCommented:
Oh, let me try this tomorow, i've misunderstood what you were saying, i don't think i ever used the "HP Standard TCP/IP" but i'll check out to be sure.
0
phLOxRSACommented:
Great, please let us know about your findings holtzer.
Also, when not using a HP printer, the driver could be named otherwise.
0
holtzerCommented:
Ok, after checking all printers port, none is configured with the "HP Standard TCP/IP"

any other ideas?
0
Hypercat (Deb)Author Commented:
@phLOxRSA - Responding to your posts about the port, in my case all of these devices are already using standard TCP/IP ports. These printers are exactly the same devices (except for updated drivers for Win7 in some cases) that were working fine before replacing the WinXP workstations with new Win7 workstations.
@holtzer - I haven't noticed the printer driver behavior that you described.  I'll take a look the next time this happens and see if it matches what you're seeing.
0
holtzerCommented:
@hypercat: this is the image from the printer properties where I said i didnt see any drivers, it took 3 print spooler restart to get the driver in the "drop down menu"


ok i' think I found a "temporary solution" it worked so far for 1 of the workstation, ill test it with more later

i have removed all the shared printers from the computer (I made sure that all account shared printer were removed too), and removed all the drivers and reinstalled all printers it seem to have worked but maybe it's just temporary.. i hope it can help others


noSharedPrinterDriver.png
0
holtzerCommented:
After some days of work, i've notice the removing and reinstalling the printers/drivers do not help

I'll try to let 1 user administrator to see if the problem occur
I'll also try on 1 other pc to print on another server

and I configured the GPO to let user (with no admin right) the ability to install and update printer drivers w/o admin intervention, i'll see all those changed do, and hope one of them works

Anyone has any suggestions ?
0
Hypercat (Deb)Author Commented:
Hi, holtzer. Good of you to do all this testing.  I was just about to try the steps of removing the printers and reinstalling. My situation is a bit more complicated, since I'm using printer deployment through group policy. I may still try that, but it's good of you to test on your end, too.
It'll be interesting to see if administrative rights make a difference, although that would not be a feasible long-term solution for my clients. As a firm policy, we do not allow users to have administrative rights to their computers. It helps cut down a great deal on the spyware/malware that gets through despite all of our filtering and antivirus/antimalware software.
I'd be interested to know which GPO you configured to allow users without admin rights to install and update printer drivers - I'm not familiar with that policy.
0
holtzerCommented:
Hi hypercat,

the GPO I used is that one,

Computer Configuration (Enabled)
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the local machine.
Printers
Policy      Setting      Comment

Point and Print Restrictions      Enabled
   Users can only point and print to these servers:      Enabled
   Enter fully qualified server names separated by semicolons       serveursql.shdm.org
   Users can only point and print to machines in their forest      Disabled
 
 Security Prompts:
   When installing drivers for a new connection:      Do not show warning or elevation prompt
   When updating drivers for an existing connection:      Do not show warning or elevation prompt
 This setting only applies to:
 Windows Vista and later


User Configuration (Enabled)
Policies
Administrative Templates
Policy definitions (ADMX files) retrieved from the local machine.
Control Panel/Printershide
Policy      Setting      Comment

Point and Print Restrictions      Enabled       
   Users can only point and print to these servers:      Disabled
   Enter fully qualified server names separated by semicolons       
   Users can only point and print to machines in their forest      Disabled
 
 Security Prompts:
   When installing drivers for a new connection:      Do not show warning or elevation prompt
   When updating drivers for an existing connection:      Do not show warning or elevation prompt
This setting only applies to:
Windows Vista and later


found on this thread : http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/ab86bc47-3186-45ec-90e6-a36e7d083deb
0
Hypercat (Deb)Author Commented:
Thanks!
0
holtzerCommented:
Well, here the result of 1 day of test

after having 4 possible solution applied yesterday

1- administration right
2- Windows 7 HotFix (KB976494) (fix with the relationship between win2k and win7)
3- Using a windows 2003 R2 shared printer
4- GPO

what I saw this morning

1- my boss told me that this morning the user with solution 1 couldn't print
2- I've received a call that user with solution #2 couldn't print
3- Went to see the user with solution #3 and said she could print.
4- Users with the applied GPO could not print and still had the driver missing in the advance tab of the printer properties

it seems server side problem but I really have to do more testing

This is getting to my nerves! -_-

We wanted to update the server, but at our own time, not being force to do so, i guess we will have to change that sooner than expected

ho and the share printer server is one of our DC, if that change anything.

any other advices?
0
Hypercat (Deb)Author Commented:
So you're thinking that the problem is the server OS version  and that you will need to upgrade to Windows 2003 R2 from regular Windows 2003)? This could be a real problem for me, since the client that is having this issue is on SBS2003. I don't think that you can update SBS to R2. They'd probably have to upgrade to SBS2008.  That is not going to be a happy solution for my client, since it would cost them thousands of dollars! Would upgrading the AD version be enough, do you think? They have a Windows 2008 Standard license, but I don't believe I upgraded the AD schema to Windows 2008 - I will give that a try when I have a chance.
0
holtzerCommented:
I'll try as many possible solution as possible but i am out for now,  I rather not update server right now, and I understand your position....
the thing that make me nervous is that i don't see anyone else except us getting the problem. Sometime I wonder if I did something wrong  and the answer might be very obvious and i'm just blind -_-
0
holtzerCommented:
did you noticed the missing driver name in the advance tab in the properties of the printer that is shared by ur server?
0
Hypercat (Deb)Author Commented:
We are not the only ones having this problem. I have done some other research and, although I'm not seeing it everywhere, I have found posts on the Microsoft Technet community forums with the same problem.  No resolution as far as I've been able to find out.
<<did you noticed the missing driver name in the advance tab in the properties of the printer that is shared by ur server?
Yes, we checked the last time this occurred for one of these users (a couple of days ago) and saw exactly the same behavior you saw - no driver listed in the printer properties.
0
holtzerCommented:
I've tried admin + hotfix and it's still not working...

got any new information?
0
phLOxRSACommented:
Hey again guys. I discovered another microsoft help tech page (http://technet.microsoft.com/en-us/library/cc773865%28WS.10%29.aspx) which includes one more possible solution than the previous one I posted. It has somethign to do with temporarily removing certain folders for some reason. Heres the jump link. http://technet.microsoft.com/en-us/library/dd393167%28WS.10%29.aspx#_1E12A501_EF2C_47F6_B83D_34B786ED9EAA

Also, it would seem there is still more info out there about the spooler service not starting, than it crashing. Seeing that we might be all out of options, I suggest you sift through this site when you have some spare time. Perhaps it inadvertently solves something. http://blogs.technet.com/fixit4me/archive/2009/01/08/restart-print-spooler-fix-it-live.aspx

All of the best

0
holtzerCommented:
It seems that it happens even on Windows 2003 Server R2 with SP2, so i'm back at square one...

@phLOxRSA: i would understand if it was happening on 1 machine or 1 server but it's been 2 servers and multiple client with windows 7

the thing that is common for all machine is really the driver missing in the advance tab from the client that is using a share printer.

I have notice that some client that log and the login server is the win2k have the problem but that's not always the case, i'm trying to find a common external factor that could result in that specific behavior.
0
holtzerCommented:
The only thing on expert-exchange that has a solution (which i dont like so much either) was that

http://www.experts-exchange.com/Hardware/Peripherals/Printers_Scanners/Q_25516507.html
0
Hypercat (Deb)Author Commented:
I did see that one, but since it involved 64-bit operating systems on the client end, I discounted it in my situation - our Windows 7 client machines are 32-bit.  Plus, I wouldn't have a 64-bit server at this site that I could use as a print server anyway.
I just found some info on increasing the diagnostic information for RPC errors.  I'm going to try this and see if it does me any good in terms of giving more information for troubleshooting. I'll let you know.
0
anchornetCommented:
I'm going to join in this group as this just happened at one of my sites. SBS 2003 Standard R2. Printers are Kyocera. My login script deletes them all and recreates. This is the first time it's happened in the last 4 months this Windows 7 has been in production.
0
anchornetCommented:
I came across this and while my issue isn't IPP specifically the hotfix does hit upon a couple of dll's with the local spooler and print processor so maybe with a little luck....

I'm going to give it a try though I'm not reproducing the problem enough to really verify the fix.

http://support.microsoft.com/kb/981620/EN-US

0
Hypercat (Deb)Author Commented:
One thing we've observed is that the Web Client service seems somehow to be involved in the mix.  We observed that the Print Spooler service is dependent upon the HTTP service as well as the RPC services.  We found that the Web Client service is set to manual startup, but that it starts up during printing. We tried simply setting the Web Client service startup to Automatic, but that hasn't helped. I'm now trying to see if there's a way to make the Print Spooler service dependent on the Web Client service, or to use the delayed automatic startup feature on the print spooler service. So far, neither one has worked. If I make the Print Spooler service dependent on the Web Client service, it throws an error on startup indicating that there's some sort of circular processing going on in the dependency tree. I can't find anything in the dependency tree that looks circular to me.  If I try to set the Print Spooler to delayed autostart, I get an error 87 - the parameter is incorrect.  
Anyone have any ideas on these issues?
0
Hypercat (Deb)Author Commented:
Hi, guys - we have found a possible solution. Someone else on my team was researching this issue this morning and found the following thread on one of the Microsoft community forums:

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/388395df-737b-4bfa-abbb-33643e7f6f58
Look for the post by jdickson289.  Essentially it has to do with a new kind of RPC communication called ASync RPC, which is new in Vista, Win7 and Win2008 server.  There is a regedit to turn it off, and someone else later in the thread also mentions using group policy preferences to create the registry entry.  I'm going to test this out here, and hope you all will, too. It seems to have worked for some of the people who were participating in this thread.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LogisticsOneCommented:
I'm also experiencing something similar, almost same kind of client (64 bit W7) and same server machine, but instead of hanging, the document prints and I also get a print error in the event log with the event id 372.  Needless to say, there have been 216 errors in the past month, since an error is generated after every print job.  Tried the registry fix posted by hypercat and restarted the print spooler, but no luck - still getting the error after every print job.

Hypercat, did the registry fix help you at all?
0
Hypercat (Deb)Author Commented:
At this point, my registry fix has been in place for 2 days and so far we haven't had any calls from users having the printing problem. However, since the calls are somewhat sporadic, I don't think 2 days is a sufficient trial period to say for sure if it worked or not.
I'm going to wait another 5-7 days and then if we don't get any further calls on this issue, I will close the question accepting my own answer (Post #32687526) as the solution. In the meantime, I'd love to see any responses from other posters who've tried the registry hack solution to know whether or not it worked for you.
Deb
0
holtzerCommented:
Good call,

though, as workaround,I installed a win7 Pro machine that serve as a print server, it works, not the best but works until we move to win2k8 R2
0
phLOxRSACommented:
Good find hypercat. I have no system to test this on, but coming from a Microsoft official, that's as good a bet as any. Keep us posted.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.