Cannot Start Server Service

While scripting a report; I came across an error about being unable to connect.

I examined the server in question and found the server service was not running.

I tried to start it but it stopped immediately with the following error in the system event log:

Windows could not start the Server service on Local Computer Error: 1808: The account used is a computer account. Use your Global user account or local user account to access this server.

However, the service was configured correctly to run as the Local System account.

It’s an odd problem and the error is misleading. The actual cause was that a user had placed a share path in in the system Path variable (ie \servershare)

After removing the offending entry the server service started right away.

WinRM Not Listening

While scripting the same report as earlier, I cam across a server which I could not connect to remotely via PowerShell.

The WS-Management service was running but was not listening on port 5985 as it should be.

Running the  winrm quickconfig command resulted in another error:

WinRM already is set up to receive requests on this machine.
WSManFault
Message = The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: “winrm quickconfig”.

Error number: -2144108526 0x80338012

Restarting the winrm service resulted in a couple errors in the System event log for port 5985 and 47001 with event ID 10128:

The WinRM service is not listening for HTTP requests because there was a failure binding to the URL (http://+:47001/wsman/) in HTTP.SYS.

No remote requests will be serviced on that URL.

User Action
Please use “netsh http” to check if ACL for URL (http://+:47001/wsman/) is set to Network Service.

Additional Data
The error code received from HTTP.sys is 5: %%5

 

I ran netsh http show urlacl from and elevated command prompt and discovered there were no wsman entries at all.

I then ran the following commands to add the URL ACL entries and restart the WinRM service.

netsh http add urlacl url=http://+:47001/wsman/ user=”NT SERVICEWinRM” 

netsh http add urlacl url=http://+:5985/wsman/ user=”NT SERVICEWinRM” 

net stop winrm

net start winrm

I tried running winrm quickconfig again and this time it was successful! PowerShell remoting was working again.

Upgrade Windows Server 2012 Essentials to Windows Server 2012 R2 Standard

There is no direct upgrade path from Windows Server 2012 Essentials to Windows Server 2012 R2 Standard. These are the steps I performed as a workaround:

Transition to Windows Server 2012 Standard

Open Windows PowerShell as Administrator, and then run the following command.

dism /online /set-edition:ServerStandard /accepteula /productkey:Product Key

Where Product Key is the product key for your copy of Windows Server 2012 Standard.

The server restarts to finish the transition process.

Upgrade to Windows Server 2012 R2

  1. Mount the Windows Server 2012 R2 media and follow the wizard.

Install the Windows Server 2012 R2 Essentials Experience Role

  1. Open Server Manager on your server
  2. Select Dashboard on the left hand navigation bar
  3. Click the Add Roles and Features link
  4. In the Add Roles Features Wizard, review the before you begin message and click Next
  5. On Installation Type verify Role-based or Feature-based installation is selected and click Next
  6. On Server Selection Screen, select the server you wish to install the Essentials Experience on and click Next
  7. On Server Roles select Windows Server Essentials Experience.  You may be prompted to add additional features for the Windows Server Essentials Experience,  review the additions and click Add Features:
    imageNotice: The Essentials experience will also install the Web Server Role, After you have added roles and features click Next:
  8. On Features, review the selections and Click Next
  9. On Window Server Essentials Experience, review the message and click Nextimage
  10. On Web Server Role (IIS) review the message and click Next
  11. On Role and Services, review the selections and click Next.
  12. On Confirmation review the installation and click Install
  13. On Results, verify the installation was successful and click Close.
  14. You will be returned to Server Manager, and in the upper left hand portion of the Window click on the notification flag.
  15. Click on Configure Windows Server Essentials
  16. On Configure Windows Server Essentials welcome page review the message and click Next
  17. On Company information fill in your Company name and Domain name and click Next
  18. On Create a network administrator account, type in the information for your administrator account and click Configure.   The configuration process may take up to 30 minutes and your server will reboot, so go get your favorite beverage and relax.
  19. After server reboots you will see the Results, verify the installation was successful and click Close.  Also close server manager.