Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Pages Menu
TwitterRssFacebook

Posted by on Oct 12, 2016 in Development

Windows Insider AND Doing Web Development? Read this!

Windows Insider AND Doing Web Development? Read this!

If you’re a Windows Insider who also does web development or uses IIS at all, then you should know about this issue which just caused me to loose 2 hours of my life.

What happens if you’re on build 14942 is that IIS won’t do anything and the World Wide Web Publishing Service won’t start, with a super unhelpful message to tell you to look in the Event Log. In the Event Log, you’ll see this equally vague message:

The World Wide Web Publishing Service service terminated with the following service-specific error:
The dependency service or group failed to start.

It turns out that this is a known issue with this build (thanks windowscentral.com). There is a workaround though:

  • Insiders doing web development may find themselves their local intranet server unreachable, as service host separation will leave the IIS World Wide Web Publishing Service (W3Svc) unable to start successfully. To fix this issue:
  • Run the following from an admin cmd line (or edit the registry accordingly):
  • REG ADD HKLM\SYSTEM\CurrentControlSet\Services\W3SVC /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
  • REG ADD HKLM\SYSTEM\CurrentControlSet\Services\WAS /v SvcHostSplitDisable /t REG_DWORD /d 1 /f
  • Reboot the system, so that the W3Svc and WAS services share a service host process.

This worked for me 🙂

Written by Tom Morgan

Tom is a Microsoft Teams Platform developer and Microsoft MVP who has been blogging for over a decade. Find out more.
Buy the book: Building and Developing Apps & Bots for Microsoft Teams. Now available to purchase online with free updates.

Post a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Share to Microsoft Teams