Member Avatar for ecupirate

My default website has a state of stopped. I right click on and select start and get the message "the service did not respond to the start or control request in a timely fashion". For some reason, I cant get this started. Any ideas

  • 3 Contributors
  • 2 Replies
  • 352 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by sypher

Dani AI

Generated

Quick summary and focused troubleshooting steps (builds on , and ).

The error "the service did not respond to the start or control request in a timely fashion" usually means IIS (IIS Admin / World Wide Web Publishing Service) or one of its dependencies failed to start before the Windows service timeout expired. Before reinstalling framework packs, collect facts and try targeted fixes: check the Event Viewer for the exact error text and source (System and Application logs), look for IISADMIN/W3SVC or Service Control Manager entries, and note any Event ID or error code.

Check for a port conflict (as suggested) and identify the process binding port 80:

netstat -ano | findstr :80
tasklist /fi "PID eq <PID_FROM_NETSTAT>"

If a non-IIS process (Skype, Apache, another web server) owns :80, stop or reconfigure it. Use Services (services.msc) or taskkill /PID <pid> /F if appropriate.

If ASP.NET integration is suspect (common after installs/updates), re-register the correct .NET with IIS and restart:

%windir%\Microsoft.NET\Framework\<version>\aspnet_regiis.exe -i
iisreset /restart

Replace <version> with the framework folder you use (for example v1.1.4322 or v2.0.50727) and run from an elevated/admin prompt.

If services still time out, increase the service startup timeout (backup the registry first) at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServicesPipeTimeout (DWORD, milliseconds — e.g., 120000), then reboot.

If configuration corruption is suspected, stop IIS Admin, restore a recent metabase from %windir%\system32\inetsrv\metaback (backup current files first), then restart IIS. Also confirm dependent Windows services (RPC, etc.) are running.

Typical mapping: netstat → port conflict; aspnet_regiis → ASP.NET/IIS registration problems; metabase restore → corrupted IIS config; ServicesPipeTimeout → slow startup or hung dependency.

Recommended Answers

All 2 Replies

Member Avatar for Letscode

Download the .NET framework servicepack 1,

Member Avatar for sypher

Could be a port conflict...Make sure you dont have any other services listening on port 80 on that server.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.