Member Avatar for Sumith Asanka

Hi Guys

I have a asp.net application(4.0) , done on VS 2010 Ultimate,i want to launch it on the IIS Server
on Windows XP(ver 5.1), when i am trying to create the Virtual Directory I am Getting this error, but directory is created , but i can't access the application on it

thanks
regards
sumith

IIS_error.JPG 111.01 KB
  • 1 Contributor
  • 2 Replies
  • 304 Views
  • 36 Minutes Discussion Span
  • Latest Post Latest Post by Sumith Asanka

Dani AI

Generated

Quick diagnostic and practical steps for the situation described by : a virtual directory is created but the ASP.NET 4.0 site hosted on IIS 5.1 (Windows XP) does not serve the app. Typical root causes are (1) ASP.NET 4.0 not registered with IIS, (2) the folder was not converted into an application, (3) file-system or service/port problems, or (4) use of IIS7+ features that IIS 5.1 does not support. Verify those in order.

Register ASP.NET and recreate the application mapping. Run an elevated command prompt on the XP box and register .NET 4 with IIS:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

Then restart the web server (or run iisreset). In IIS Manager open Default Web Site, locate the virtual folder, open Properties and click Create under Application settings to make it an application. On the ASP.NET tab check that the selected framework version is v4.0.

Quick sanity tests and small edits that uncover the failure cause: place a tiny test page inside the virtual directory (test.aspx) and try accessing it via . A small test page:

<%@ Page Language="C#" %>
<!DOCTYPE html>
<html><body><%= "ASP.NET is running" %></body></html>

If requests still fail, temporarily enable detailed errors in web.config and turn off customErrors while debugging:

<configuration>
  <system.web>
    <customErrors mode="Off"/>
    <compilation debug="true" targetFramework="4.0"/>
  </system.web>
</configuration>

A few focused checks: confirm IIS services are running, test static file access (to rule out port/firewall issues), inspect the Windows Event Viewer Application log for ASP.NET/.NET runtime errors, and note the HTTP status code returned (403 -> permissions, 404 -> path/mapping, 500 -> configuration/runtime error). Remember that IIS 5.1 is limited (no application pools, older pipeline)—features or <system.webServer> settings from IIS7+ may not apply. For modern development or complex apps, consider IIS Express or a newer Windows/IIS host.

Member Avatar for Sumith Asanka

Hi Guys

I sorted out that issue now i am getting a error like this what is it about ?

thanks
regards
sumith

IIS_error_1.JPG 150.02 KB
Member Avatar for Sumith Asanka

b9eb5d419cd83813fcf9b62c1ac2e5ac Hi Guys

I sorted out that issue now i am getting a error like this what is it about ?

thanks
regards
sumith

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.