Announcement

Collapse
No announcement yet.

Print spooler intermittently crashing - network wide issue

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Print spooler intermittently crashing - network wide issue

    I'm no longer working the help desk, but our staff here are rushing around trying to get a handle on a network wide problem today. I was hoping someone here might have run across it and have some advice.

    We have multiple machines where the print spooler crashes, for no apparent reason, and fails to restart. Even a full reboot isn't fixing the issue. Then, sporadically, the print spooler will restart on these machines. Then die again and refuse to restart for any reason. Wash, rinse, repeat.

    This has taken out almost all of our front desk printing capability (kind of important since they guest name tags & other info) as well as many of the admin office printing, too.

    Any suggestions? Though its not my job to fix it, I sympathize with our help desk staff and they currently have no idea what is causing the issue or how to fix it.

    Also, my PC is one of the affected machines and I really need the ability to print.

    Thanks!
    Tags: None
  • #2
    XP machines?
    Mine @ home and @ work would do that.
    Are these printers networked across the netowrk so someone can print @ desk and pick up@ watercooler, or are they on the desks?

    I D K if XP ever had a fix for that. Check Microsoft.
    In my heart, in my soul, I'm a woman for rock & roll.
    She's as fast as slugs on barbituates.

    Comment

    • #3
      I ran into that problem last week on a vista machine connected to a HP printer via USB. Turned out to be drivers gone bad. Ended up needing to hack the registry and part of the windows directory to get everything working right, still waiting to see how stable it's going to be in the long run.

      Comment

      • #4
        Yeah, sorry, forgot to mention it was the connections to all the network printers. Which is, of course, basically every major printer in the building.

        They managed to get it fixed by calling the lead help desk tech. In the middle of his 2 week vacation to have him log in remotely and fix it. From Peru.

        Took him 20 minutes, though the other 2 techs say it was something they would probably not have been able to diagnose and fix. They didn't elaborate on the cause or fix, at least not to me.

        I suggested up the chain that the lead tech deserves a raise, since we clearly need to hold onto his skills.

        Comment

        Previous template Next
        Working...