• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 14024
  • Last Modified:

Print Spooler error

We have a Win NT 4 Server w/ SP6a. When we try to start or stop the printer spooler the following error appears;

spoolss.exe - Entry Point Not found.

The procedure entry point GetPrinterA could not be located in the dynamic link library SPOOLSS.dll.

We replaced the localspl.dll, spoolss.dll and spoolss.exe as suggested  by Microsofts Knowledge Base. However, it did'nt fix the problem.

Any suggestions?

Thanks,

-Laz
0
Lbello
Asked:
Lbello
1 Solution
 
oBdACommented:
Did you indeed replace them from the NT4 installation disk, as suggested in the article? Then that might be your problem.
Unpack the service pack with -x (or open it in WinZip) and replace the files again with the ones found in the service pack.
0
 
LbelloAuthor Commented:
Yes we did! We found the solution, however. In the Print\Spooler folder where jobs that did not print. Once we deleted the jobs we where able to stop and start the service and our users can now print.
0
 
oBdACommented:
Then don't forget to post at Community Support to have your points refunded ;)
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
PashaModCommented:
Question closed and points refunded

PashaMod
Cs Moderator
0
 
Spectre71Commented:
This problem seems to have been mis-diagnosed by both Microsoft and HP.  The problem that causes this is the HP printer monitor.  The way to resolve the problem is to open the registry in the following:

HKey Local Machine\SYSTEM\CurrentControlSet\Control\Print\Monitors.

Delete the key for "HP Master Monitor".

This will resolve the problem.
0
 
sbooiCommented:
After deleting this key
HKey Local Machine\SYSTEM\CurrentControlSet\Control\Print\Monitors.

Delete the key for "HP Master Monitor".

What will be the impact? Any impact to TCP/IP Printing Service?
0
 
Spectre71Commented:
There is no impact on the actual printer service.  ALl continues to work well.
What i do assume though, is that the Monitoring Utility probably stops working.  I don't use this utility anyway, so this was not an issue to me.
Since I removed the entry in the registry, i have not investigated this issue any further, because once things are working, I tend to leave them alone.
Pity I didn't get the points for this.
0
 
thewordtheCommented:
Thanks guys, this was a helpful. A further comment might help others?

The error entitled [spoolsv.exe - Entry Point Not Found] and message [The procedure entry point GetPrinterA could not be located in the dynamic link library SPOOLSS.dll] was preventing users at a remote office printing through CITRIX. The Print Spooler Service kept crashing, and users were unable to connect to printers through their CITRIX desktop.

I renamed the registry entries to begin with, no joy, and I deleted them, again no joy. However, whilst they were deleted I went to M:/WINNT/System32/spool/Printers folder and deleted all the files in there. I then went through the entire list of CITRIX printers form the Server and made sure that there were no documents waiting to be printed, deleted the ones that I found. Then I started and stopped the spooler service, and reset the CITRIX sessions. This time when the users went into CITRIX, the print devices attached to their clients became available, they were able to print and the spoolsv.exe error did not re-occur

So really a combination of what the other guys said, but for CITRIX administrators
 
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now