You are currently browsing the tag archive for the ‘Error processing resource’ tag.
Before I start I would like to tell all that I am using visual studio 2005, dotnet framework 2.0 , windows xp sp 2 and IIS 5.1 with sqlserver 2008. I developed a web application and I wanted to make it available online on our server. The first thing that I did was to publish the web site, the path for the published files was c:\eprocure. That went pretty well no error, and visual studio message was “published successfully”. The next thing was to make the published website accessible through the local server. I created a virtual folder named “epro” for my published web application. Than I tried to access the login.aspx page as http://localhost/epro/login.aspx and BANG the following error came out of no where
A name was started with an invalid character. Error processing resource ‘http://localhost/epro/’. Line 1, Posi…
<%@ Page Language=”C#” MasterPageFile=”~/Master.master” AutoEventWireup…
I tried a lot of tweaking , messed up a lot of thing but nothing worked. Finally the problem was solved as follows Type “cmd” in RUN. Go the following location.
Look for a file
When multiple versions of the .NET Framework are executing side-by-side on a single computer, the ASP.NET ISAPI version mapped to an ASP.NET application determines which version of the common language runtime (CLR) is used for the application. The ASP.NET IIS Registration Tool (Aspnet_regiis.exe) allows an administrator or installation program to easily update the script maps for an ASP.NET application to point to the ASP.NET ISAPI version that is associated with the tool. The tool can also be used to display the status of all installed versions of ASP. NET, register the ASP.NET version that is coupled with the tool, create client-script directories, and perform other configuration operations.
Execute the following command
this command installs the version of ASP.NET that is associated with Aspnet_regiis.exe and updates the script maps at the IIS metabase root and below. Only the script maps for applications that use an earlier version of ASP.NET are updated. Applications that use a later version are not affected.
Than execute the following command
this command removes the client-side scripts for ASP.NET from the aspnet_client subdirectory of each IIS site directory. Only the client-side scripts for the ASP.NET version associated with Aspnet_regiis.exe are removed.
Restart the system and check the website as http://localhost/epro/login.aspx and the site is functional.
Please leave your comments if this helps.