Re: spooler not starting



Hi John,
I will follow your instructions and hope this will fix,if I need
to go to Microsoft and get the correct fix I might join you in 'crow lunch',
maybe a nice red would help!!

regards

aga

"John John (MVP)" wrote:

Carefully follow all the instructions here:
http://members.shaw.ca/bsanders/CleanPrinterDrivers.htm If need be
download the Resource Kit and use Cleanspl.exe to cleanout all the
printer drivers. Make sure that you follow the instructions (including
those from Microsoft's site) to remove the Lexmark service and make sure
that you use the SC command to restore the spooler dependency to its
default setting. If it still fails to run then maybe the hotfix is
required, in that case you will have to call Microsoft for the fix. The
fix will be free, just tell Microsoft that you were instructed by
Lexmark tech support to download and install the fix. I am still quite
skeptical that the fix will work or even install on XP, but you never
know, maybe it will cure your problem...and then I'll eat crow!

John

aga151 wrote:

Hi John,
I see I'm not the only guy that see's them as a take your money
then sod off!!think that microsoft are a bit the same,they have the cure but
will not pass the info on,what's left to do now in your opinion
regards

aga

"John John (MVP)" wrote:


Either the guy at Lexmark is full of beans or you misunderstood what he
told you to do. Hotfixes are never, or almost never made available for
download to the general public. Hotfixes are issued to fix specific
problems and should only be used if you are experiencing these specific
problems. The hotfixes may not be fully tested for every possible
scenario and they may cause unforeseen problems on some machines. They
aren't meant to be installed to computers without the problems.
Computers being what they are you can be sure that if the hotfixes were
to be readily available to the general public a lot of folks who don't
know any better would download and install these fixes then they would
complain because the fixes broke their computers. Microsoft doesn't
want those headaches and hassles so they don't make the fixes available
to the general public.

If you ask me your problem is solely caused by Lexmark crap and their
cursed LexBce service that highjacks the print spooler and places a
dependency on it. Lexmark aren't smart enough to figure out how to make
their printers work without completely screwing up the spooler subsystem!

John

aga151 wrote:


Hi John,
This where I got the supposed hotfix: Q 318152 and I did ask the
guy and HE put me in to the articles page and he said I would find it
there,well, it is'nt there,I told him I was'nt an expert and needed him to
tell me exactly what and where I could get this,he insisted I go to where he
suggested.
I'm afraid I don't put very much faith ih either Lexmark or Microsoft
surely the idea of these guys is to help people who DON'T know and have there
knowledge,I get the idea they think that everyone knows what THEY are
talking about,I saw lots of articles!! but what is the correct one.

Very difficult, I did tell Lexmark that I was on to Microsoft when there
first expert took over my pc and left me with the task of contacting
Microsoft,that was a week ago and that guy told me exactly what the guy said
yesterday,sounds as though they were reading off a manual!

Come back Epson all is forgiven

regards
Allan

"John John (MVP)" wrote:



You have to call Microsoft for the hotfix.

John

aga151 wrote:



Hi John,
The Q318152 hotfix was what Lexmark gave to me to get from
Microsoft,theproblem I am having is I cannot seem to find this fix and to
download it, I have SP3 installed in windows xp Home,when I go to look for
this fix can't seem to find it.

regards

aga

"John John (MVP)" wrote:




The information in the article states that the hotfix applies to Windows
2000 and then only with SP1 or SP3 (Windows 2000 has a later service
pack 4 not mentioned in the article). The hotfix appears to be a bit
out of date and whether or not this hotfix also applies to Windows XP is
something that you would need to have confirmed by the folks at
Microsoft or at Lexmark.

Print Spooler Stops Scheduling Print Jobs
http://support.microsoft.com/kb/318152

John

aga151 wrote:




Hi,
My Lexmark x4580 has been playing up for some time,I have now had Lexmark
do a diagnostic test and they say that the spooler will not start when
printing from notepad,works or from any task from the pc,Lexmark say I need
this patch or update: Q318152

Anyone help on this one !!

regards

aga



.



Relevant Pages

  • Re: Recovery Storage Group: Invalid DN Syntax Error on names with
    ... Please contact Microsoft directly to receive a hotfix. ... Here is the fix. ... >> password for each package. ...
    (microsoft.public.exchange.admin)
  • Re: Q811493 hotfix
    ... after installing the Q811493 hotfix. ... Hopefully we'll see a fix soon. ... >Microsoft has stated they are working on the cause, ... >> Windows Update, installing the Q811493 update as suggested. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: spooler not starting
    ... Make sure that you follow the instructions to remove the Lexmark service and make sure that you use the SC command to restore the spooler dependency to its default setting. ... If it still fails to run then maybe the hotfix is required, in that case you will have to call Microsoft for the fix. ... The fix will be free, just tell Microsoft that you were instructed by Lexmark tech support to download and install the fix. ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Event ID 61 in Print Server
    ... After you install the hotfix that is described in this article, ... obtain the latest service pack for Microsoft ... A supported fix is now available from Microsoft, but it is only intended to ... contact Microsoft Product Support ...
    (microsoft.public.win2000.printing)
  • Re: Oops, heres the link - Re: Event ID: 5504
    ... I'll give Microsoft a call tomorrow and take it from there. ... The normal method for obtaining a hotfix would be to contact ... >> I did check out that hot fix link but I thought it was fixed in SP4 ...
    (microsoft.public.windows.server.dns)