locked
Start-Service spooler NOT WORKING RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a Server Core 2016 print server.

    None of the printer commands will work because the print spooler service isn't running (example: Get-Printer). Note, I'm remoted in but I've try to do it at the actually computer too. Also, I am running powershell as an admin.

    Every time I type "Start-Service Spooler" it returns an error message that is pretty vague. I did install the print server roll as you can see from the 2nd screenshot. 

    Why can't I start the spooler?



    • Edited by finsfree11 Wednesday, June 20, 2018 7:29 PM
    Wednesday, June 20, 2018 7:22 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    This is not really a scripting issue.  Go to the service controller and use the "Computer Management" MMC snap-in from and system to remotely connect the server then try to start the service.   You will get a better error message.

    Use normal troubleshooting techniques to resolve.

    If you do not know how to do this then contact MS support for help.

    Again -  this is not a scripting issue and this is not a system support forum.

    \_(ツ)_/

    • Marked as answer by finsfree11 Wednesday, June 20, 2018 9:17 PM
    Wednesday, June 20, 2018 8:48 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    is the service hung?
    Wednesday, June 20, 2018 8:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote 
    Get-Service spooler -Computer ursula | Start-Service
    give it a shot.
    • Edited by The Grim Wednesday, June 20, 2018 8:14 PM
    Wednesday, June 20, 2018 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote 
    Get-Service spooler -Computer ursula | Start-Service
    give it a shot.

    No, same result. Weird.....

    I can stop and start other services but not the print spooler. Is there a way to force it?



    • Edited by finsfree11 Wednesday, June 20, 2018 8:33 PM
    Wednesday, June 20, 2018 8:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is not really a scripting issue.  Go to the service controller and use the "Computer Management" MMC snap-in from and system to remotely connect the server then try to start the service.   You will get a better error message.

    Use normal troubleshooting techniques to resolve.

    If you do not know how to do this then contact MS support for help.

    Again -  this is not a scripting issue and this is not a system support forum.

    \_(ツ)_/

    • Marked as answer by finsfree11 Wednesday, June 20, 2018 9:17 PM
    Wednesday, June 20, 2018 8:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is not really a scripting issue.  Go to the service controller and use the "Computer Management" MMC snap-in from and system to remotely connect the server then try to start the service.   You will get a better error message.

    Use normal troubleshooting techniques to resolve.

    If you do not know how to do this then contact MS support for help.

    Again -  this is not a scripting issue and this is not a system support forum.

    \_(ツ)_/

    That did it!

    I didn't really want to do it this way, but it worked.

    I wanted to be able to setup a Server Core Print Server 2016 all through Powershell. 

    It seems ridiculous that I have to use the GUI to perform this task.  


    • Edited by finsfree11 Wednesday, June 20, 2018 9:21 PM
    Wednesday, June 20, 2018 9:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can but the problem is not caused by a script.  It is caused by something else in your system.  I would research the event log to find out why this is failing.

    To remotely start a service just use Start-Service.

    Get-Service spooler -Computer remotehost | Start-Service

    If this also fails then you may have WMI issues.

    \_(ツ)_/

    Wednesday, June 20, 2018 9:32 PM