Chris Love's Official ASP.NET Blog : Error processing resource

Navigation

Resources

Archives

Error processing resource - What in the world does this mean?

Over the past two days I have created some test sites and some new sites to begin development on. Yesterday I hit a little stumbling block and had a little bit of trouble finding the solution. So I created a new site, MyNewSite for example, on my local web server. If I ran it from within Visual Studio 2005 it came up fine, but as you know I do not rely on that web server to build and test because it is difficult to configure third party controls to work in it. When I tried to browse it using http://localhost/mynewsite I kept getting this error displayed everytime I went to the page:

The XML page cannot be displayed

Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

A name was started with an invalid character. Error processing resource 'http://localhost/mynewsite/'. Line 1, Posi...

<%@ Page Language="VB" MasterPageFile="~/default.master" AutoEventWireup="false" CodeFile="Default.aspx.vb" Inherits="_De...

Great, I said, what does this mean. I tried a few things, like making sure the virtual directory was set to an application, it was using ASP.NET, etc., and had no luck. So I checked my IIS logs to see what Status Code was logged, 200 and 302/304, which are all good and expected in this situation.

So I hit the messageboards and saw many others are having this issue. Several solutions I found were to uninstall and reinstall the ASP.NET 2.0 framework. I really did not think that was the problem because I have many other sites that are running off the same IIS 5.1 installation. They were all set up in the past 30 days (this is a new workstation afterall) and worked just fine.

So I thought I would try the 'Browse' option from within the IIS manager. The site came up! So I thought what is different, that is the same as I tried before. Then it hit me, case sensativity. Yep that was the culpret, http://localhost/MyNewSite worked just fine. So if you get this error, try changing the URL in your address bar to be case sensative. BTW, all the problems I saw people reporting in the messageboards seemed to be related to Windows XP and IIS 5.1, so I think this is a security feature of the latest patches, etc.

Posted: Friday, April 07, 2006 7:21 PM

by Chris Love

Filed under: ASP.NET, IIS

Comments

Gavin said:

Man ... you are a legend. I looked everywhere, and lots of notes about re-registering ASP.NET,etc setting the ASP.NET version, none of which worked. Changed the case of the url and it worked perfectly. How annoying! Strangely, the case of the site in IIS is Reports, but in IE it has to be reports. Very odd ...

# April 17, 2008 10:22 AM

Lawk Salih said:

What if you only have one website and it's the default site in your IIS? I still get that error.

# July 3, 2008 2:23 PM

Karthik said:

This post looks different, but I still get the same error when I try out to access the pages.

# July 8, 2008 5:03 AM

Ariful Ambia Noman said:

I am still getting this error. I tried lot of things but no luck. why this is happening with me :(

# July 22, 2008 1:58 AM

peter nguyen said:

I installed community server on Windows 2k3 R2 w/SQL 2005 and had a similar error. I followed the steps above and it didn't work. This is how I fixed mine: 1. Re-registered ASP.NET frameworks 2. Tested, still failed 3. Navigate to C:\Program Files\Telligent\Community Server 2008\Web, right click, properties, security 4. Assign full access to the Network Service account (I used to domain's Network Service account) 5. Tested it and it worked. This is my original error: The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. -------------------------------------------------------------------------------- A name was started with an invalid character. Error processing resource 'http://localhost/cs/'. Line 1, Position 2 <%@ Page %> -^

# August 25, 2008 2:33 PM

Ramana said:

Great dude, Its working. Thanks

# August 30, 2008 2:04 PM

Ehsan said:

you should run this line on command prompt : C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i After that, restart your computer

# August 31, 2008 12:39 AM

Bto said:

=( i tried all of things but no luck =( somebody have another answer???

# September 1, 2008 12:26 PM

Chris Harris said:

Strange, I came upon this problem when using localhost instead of 127.0.0.1

# September 4, 2008 11:28 AM

Prince said:

I have been encountering problems with accessing my webite which I pblished on a local server but I can't seem to access it with my Internet explorer. Whay do you guys think of my IIS. What version do you recommend to be used or what IE browser version do you think I should be using coz my system runs on Windows XP. Any one who can help,will be appreciateted. I once also had a problem like this <%@ Page Language="VB" MasterPageFile="~/default.master" AutoEventWireup="fals"

# September 16, 2008 1:35 PM

Tazul Islam said:

I got the same error when I installed IIS 5.1 on Windows XP professional, service pack 2. I executed the following command from command prompt, and my IIS now works fine. Thanks Mr Ehsan. C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i FYI, if you install IIS after visual studio 2005/2008 had already been installed there, then this problem occurs.

# October 28, 2008 2:34 AM

fedrok said:

HI! I'm sorry but I'have this problem too. I installed my site into 2 different IIS machines, and in the first it works, but in the second I've got the error here discussed. I'm sure once it works in all two machines. Is it possible that is a problem of some security update from Microsoft, downloaded with "windows update"?

# October 30, 2008 1:28 PM

Bill Hamilton said:

Thanks MUCH! I was having the same problem... I'm building a new 2008 Server Standard, IIS 7 native modules, .net 2.0 app pool, trying to serve a moderate xml page... I've tried everything else everywhere and then I came here and saw your "Case sensitive" observation... Geez, that worked for me too!!!! You saved my head from imploding :) Thanks... Bill

# November 12, 2008 11:55 PM

Ian McD. said:

Thanks from me too! This bustin' my head and had tried many other options before stumbling onto your advice.

# November 26, 2008 10:47 AM

Harold said:

I ran C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i. This clear up this problem. Thanks

# February 23, 2009 11:22 AM

fahad272@yahoo.com said:

installed community server on Windows 2k3 R2 w/SQL 2009 and had a similar error. I followed the steps above and it didn't work. This is how I fixed mine: 1. Re-registered ASP.NET frameworks 2. Tested, still failed 3. Navigate to C:\Program Files\Telligent\Community Server 2008\Web, right click, properties, security 4. Assign full access to the Network Service account (I used to domain's Network Service account) 5. Tested it and it worked. This is my original error: The XML page cannot be displayed Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later. -------------------------------------------------------------------------------- A name was started with an invalid character. Error processing resource 'http://localhost/cs/'. Line 1, Position 2 -^ i want work this xml now emmidiyaly

# March 6, 2009 5:41 AM

Nanda said:

Hi i tried wat "Harold" said in this blog, its works fine without restarting the machine.

# April 1, 2009 4:40 AM

Audai said:

I am still getting this error. I tried lot of things.... and i have windows XP prof. SP2, and Visual Studio 2008........ I need help

# April 12, 2009 8:15 AM

GabrielVarun said:

Thanks Buddy . The Problem with me was that i've reinstalled iis so it was not registered with asp.net 2008. run this line on command prompt : C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i. restart was not needed and the thing worked fine...

# June 1, 2009 4:17 AM

Grizzie said:

After reading this thread I still hadn't found any solution to the same problem. I am not very good with ISS and stuff so this might not have nothing to do with anything but it solved my problem. 1.I went into ISS and the properties of my default site. 2.I opened the ASP.NET tab and went to Edit configuration. 3. Under general tab I found something called EnableFriendlyUrl or something and the value was set to true. So I changed it to false and my site worked. However, this could be a value that EPiServer sets, so it might not even be in a "normal" site. As I said, I am not good with stuff like this.

# August 21, 2009 4:20 AM

wmin said:

Chris, you are my hero! I spent 2 f@cking days on this! .... another wonderful Microsoft feature :-@'

# November 10, 2009 7:31 PM

sacala said:

thanks Chris. you save my day!

# February 14, 2010 11:23 PM

Chris Love's Official ASP.NET Blog

Recent Posts

Tags