(Stephen Parker, Head of Cloud Strategy)
This is off topic from service provider licensing, however on the basis that it is possible our partner community may be the type of people who could have Windows Home Server and may therefore have encountered this issue I thought I would post here. (and if you are here just for this article then maybe you could look around a bit further )
Time lost that I will never get back, knowledge gained that I can only hope in some future life has some advantage!!!!
- Have Windows Home Server 2011 – love it
- Lots of home machines and no previous (major) issues
- Get new Lenovo X220, setup with everything I need
- Install the WHS Connector works fine, however after the first reboot I am told that “The server appears to be offline. Do you want to sign in to offline mode”
- Backups will not work and alerts fail
After much searching etc I finally got to the bottom of the problem:
- Windows Home Server installs a number of additional services, “Windows Server….” on the client machine (Start, type services, click on “view local service” scroll to the bottom)
- These are all set to “startup type” of Automatic
- However not all of them are started
- The 2 critical ones are “Windows Server Client Computer Backup Provider Service” and “Windows Server Health Service”
- Looking in the service descriptions I tracked down the dependencies:
- Backup and Health depend on “Windows Server Service Provider Registry”
- “Windows Server Service Provider Registry” depends on “Net.Tcp Port Sharing Service”
- And when I looked in the Event Viewer (System) I found that “Net.Tcp Port Sharing Service” is failing with an error “A timeout was reached (30000 milliseconds) while waiting for the Net.Tcp Port Sharing Service service to connect”
- This then has a cascade event on the “Windows Server….” Services
- If you check “Net.Tcp Port Sharing Service” in the Local services list it has probably gone through its recovery process and started up, however the “Windows Server…” services are left in stopped state
- You can just go to the View Local Services after each boot and manually start the “Windows Server Client Computer Backup Provider Service” and “Windows Server Health Service” services and all will be good
- OR the solution that I chose was to increase the timeout limit for services in the registry:
- Fire up regedit (disclaimer – make sure you have done a registry backup)
- In Registry Editor, locate, and then click the following registry subkey:
- By default there should be no “ServicesPipeTimeout” so you need to create it:
- Point to Edit/New, and then click DWORD Value.
- In the right pane of Registry Editor, notice that New Value #1 (the name of a new registry entry) is selected for editing.
- Type ServicesPipeTimeout to replace New Value #1, and then press ENTER.
- Now to modify the timeout value:
- Right-click the ServicesPipeTimeout registry entry that you created (or was already there) and then click Modify. The Edit DWORD Value dialog box appears.
- Click “Decimal” under Base
- Type in 50000 in the “Value data” text box and then click OK (Note the default value for this is 30,000 milli-seconds. I initially set to 100,000 and then reduced to 50,000. You may need to alter this to suit your situation)
- Restart the computer. You must restart the computer for Service Control Manager to apply this change.
Everything is now good…..