Spoolsvr error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Last week we installed some routine patches via Windows Update to one node of
a cluster with Windows 2000 Advanced Server SP4. Following the reboot we got
the following error "The procedure entry point GetPrinterA could not be
located in the dynamic link library SPOOLSS.dll." and the print spooler
service now fails to start on that node. I have tried last known good config,
windows repair, removed the hotfixes, reapplied SP4, but the problem remains
....

Much appreciate and clues from anyone else whose ever encountered this and
resolved it?
 
Mulder said:
Last week we installed some routine patches via Windows Update to one node
of
a cluster with Windows 2000 Advanced Server SP4. Following the reboot we
got
the following error "The procedure entry point GetPrinterA could not be
located in the dynamic link library SPOOLSS.dll." and the print spooler
service now fails to start on that node. I have tried last known good
config,
windows repair, removed the hotfixes, reapplied SP4, but the problem
remains
...

Much appreciate and clues from anyone else whose ever encountered this and
resolved it?
Click to expand...


try moving the print spooler location

create a location ie C:\Spooler
go to Printers and Faxes in Control Panel
File
Server Properties
Advanced tab
enter the new location ie C:\Spooler

stop and restart the spooler
 
Many thanks for your reply Steve and an otherwise good suggestion. Not quite
as straightforward as that though - the cluster node that has the issue won't
allow you into the Print Server properties whilst the resource is running on
the other node and when you try and move onto it's own node the resource
fails. I did try creating a new Spool location on the good node and then
seeing if when it failed over the bad node could start from the new location
but alas no.

The error you get in the event logs is the same as this article
http://support.microsoft.com/kb/324183/en-us and I requested the fix already
but it's for SP3 only and the node already has SP4.

Looks like I may have to resort to rebuilding the node soon. Annoying to say
the least
 
Mulder said:
Many thanks for your reply Steve and an otherwise good suggestion. Not
quite
as straightforward as that though - the cluster node that has the issue
won't
allow you into the Print Server properties whilst the resource is running
on
the other node and when you try and move onto it's own node the resource
fails. I did try creating a new Spool location on the good node and then
seeing if when it failed over the bad node could start from the new
location
but alas no.

The error you get in the event logs is the same as this article
http://support.microsoft.com/kb/324183/en-us and I requested the fix
already
but it's for SP3 only and the node already has SP4.

Looks like I may have to resort to rebuilding the node soon. Annoying to
say
the least
Click to expand...


Have you tried reservice packing with SP4, this should be uneccessary but in
the past I've found such issues fixed by reapplying the service pack

There's further info on that error here:

http://www.eventid.net/display.asp?eventid=45&eventno=607&source=Print&phase=1

that may be of help.
 
OK I finaly got an answer back from the MS Advisor service which worked and
saved me a time costly rebuild. Feel the need to share as this was a pig to
try and resolve -

The Ask the Expert answer:
If the HP software and drivers for your HP printer(s) are NOT current, you
will experience this problem. To resolve the problem: 1. Uninstall all your
HP printers. 2. Search for and rename all occurrences of HPBMMON.DLL in the
%SystemRoot% folder and sub-folders. 3. Use the registry editor to delete any
reference to HPBMMON.DLL at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors and its'
sub-keys. 4. Install the printer using the latest HP software.
 
Back
Top