Member Avatar for senthilg

I'm new to this asp.net while i'm creating a new website i got error like this i don't know what to do..
my error is...
" Configuring web site 'http://localhost/mysite to ASP.NET 2.0 failed. You need to manually
configure this for ASP.NET 2.0 in for your site to run correctly"

  • 3 Contributors
  • 3 Replies
  • 195 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by reach_shailshar

Dani AI

Generated

This thread points at the three usual root causes for the error message reported by : missing ASP.NET-to-IIS registration, the site not being configured as an IIS application/virtual directory, and permission/handler mismatches. ’s pointer to official ASP.NET/IIS guidance is useful background; ’s report shows registration can fix handler issues; ’s note about virtual directories highlights configuration-level causes. Below is a focused, practical checklist and troubleshooting guidance that complements those replies.

Common checks (in order)

  • Confirm the site is an IIS application (not just a plain folder). In IIS Manager an application has its own application icon and can be assigned an application pool.
  • Verify the application pool’s CLR version matches the application (.NET 2.0 in this thread) and that the pool is started.
  • If IIS is not handling .aspx pages, register the ASP.NET runtime with IIS using the framework registration utility (run elevated and use the framework folder that matches the OS bitness).
  • Check Handler Mappings and ISAPI/CGI restrictions so ASP.NET handlers are enabled.
  • Recycle the app pool or restart IIS after making changes.

Additional troubleshooting tips

  • Inspect Event Viewer (Application/System) for specific ASP.NET or IIS errors — these often show the exact handler or permission problem.
  • Test static content first (HTML) then a minimal .aspx page to isolate whether IIS or ASP.NET is failing.
  • Verify file-system permissions for the site folder: the app pool identity needs appropriate read/execute access.
  • Check web.config for malformed sections or incompatible configuration entries that will prevent application start.

Notes and cautions

  • Steps differ between IIS versions (IIS6 vs IIS7+) and 32/64-bit Windows; administrative privileges are required for registration changes. Back up configuration before making system-level changes. For targeted diagnostics, include OS, IIS version, and installed .NET versions when comparing solutions.

Recommended Answers

All 3 Replies

Member Avatar for senthilg

i used this command
%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i

and it worked for me

Member Avatar for reach_shailshar

hello!!!
the error occurs because of the absence of the virtual directory of the website.
when u develop a website it automatically genrate its directory in ISS , when u carry a website from another system in removable memory device, it creates the same problem as u have mentioned.
to overcome the problem u have to create a virtual directry in The IIS for which follow the path..

START>>Control Panel>>Administrative Tools>>IIS>>New Virtual Directory(right click on Web Root) .
it will work for you.

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.