I don't think that I fixed the underlying code defect, let me rephrase that I *know* that I didn't fix the problem, that is causing this error, but I was able to get my pages to render again.  It seems like the problem was in the RewriteService.cs file.  I changed the USE_REWRITE constant value to false and now the pages that I create within the admin module are rendering and I no longer get the "resource cannot be found error". 

I changed line 88 in RewriteService.cs:

private const bool USE_REWRITE = false;//TODO: Move to SiteSettings

Like I said before, this didn't fix the underlying problem, and I figured I would post this just in case anyone else is having this problem, and to get this in as a defect in the RC1.

Tim

That will definitely be a problem for me, and potentially others, since I am using an ISP that won't let me change the aspx server mapping properties.  I guess there will eventually be an option in the admin module for turning off the "rewriting"?

Tim

Tonight I started seeing this problem for the first time since loading 3.0 Web Ready release a day or two ago. (I thought this  was working last night, in fact I'm 5 9s certain that it was working last night.) I just got off the phone with GoDaddy support for shared hosting and they technician said there was no IIS setting he could check other than the 3 that are available to me via the Hosting Control Panel: Anon Access, Dir Browsing, Set App Root.

Any pointers?

I submitted an email troubleticket to my Host. We'll see what they say.

I just got off the phone with GoDaddy and the tech confirmed that the "check that file exists" setting was not checked. I am going to try to turn it off in the rewrite service code file and see what happens.

Any other ideas what could be causing this?

The problem can be recreated as follows. 1. log into Admin >> Content Mgmt and create a new page. 2. Return to site and click the link that was added for your new page and whamo!

phatPhil:

"check that file exists" setting was not checked

protected void Application_BeginRequest (object sender, EventArgs e) {
   if(Request.Url.ToString().Contains("Page-Hope-for-Growers_4"){
       Context.RewritePath("Default.aspx");
       //Or some other way to see if it gets to here
   }
}

If you get to there then you might have a different problem please let me know.

Hi All,

     I finally was able to figure out why I was getting this error...and it is rather stupid on my part.  I am using Visual Studio 2008, and converted the projects to use .NET 3.5.  So, this modified the csproj and web.config files.  So, each time that I got latest from the repository I just ignored that there were changes to the web.config files.  Well, today I went line by line through my 2008 web.config and the version in source control, and lo and behold my web.config was missing all of the entries for the UrlRewriter.  So, I went through and added in the missing entries in the web.config and downloaded the urlrewriter binaries from http://urlrewriter.net/, and presto!  everything works.  I really hope that this helps the other people that were experiencing this problem.

I was going to post the lines in the web.config that I was missing, but there are too many of them.  So, check to make sure that you have the latest web.config.  Also, when you download the urlrewriter binaries, be sure to add the reference to the Web project.

Tim

Thanks Tim.

Summary of my fix: I updated the web.config file to the version containing the configuration for url rewrite. I got this version from the Web Ready release build.

Your reply gave me a much needed clue and led me to the fix for my problem. After reading your post, I realized that my site quit working when I uploaded the Web Ready kit, which I purposely loaded over the RC 1 build. I loaded all but one file, the web.config file. (I did this because I didn't want to overwrite my connection string, forgetting that the connection string is located in another file, the connectionString.config file)

I pulled down the web.config that was being used at the time that url rewriting was broken and compared it to the local version of RC 1 and also compared it to the version in the Web Ready build. Sure enough, I noticed the difference right away, the references to url rewrite were not in the web.config file I was using.

So my fix was to load the Web Ready version of the web.config which contains all the necessary references to url rewrite and the site started working right away.

I didn't have to go to urlrewriter.net and download anything because the Intelligencia.UrlRewriter.dll that came with the Web Ready build was already in the bin folder (which I uploaded when I upgraded from RC 1 to the Web Ready build)

Phillip