I just finished upgrading to a new server.  I went from Win2000, IIS6, SQL2000 (ouch) to Win2008 with SQL2008 and of course IIS7.  Everything is working great, with the exception of newly created pages.  When I create a new page, it shows in the page list, but when I actually try to navigate to the page it throws a 404 error.  All other pages that were there before the migration are working fine.  Has anyone seen this before?

Thanks,

Shane

Hey there Bill, thank you for the response.  Here are the answers to your questions.

DNN v5.01.04 (3)  We were at the cap for upgrades because of the old environment.  We did this upgrade in part because we needed to upgrade past this version.  We have not upgraded yet though.

ASP.net is running 3.5, and yes this was an upgrade from 2.0

I have friendly URL's turned on yes.  Here are teh web.config lines for these:
- <section name="friendlyUrl" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />
- <add name="UrlRewrite" type="iFinity.DNN.Modules.FriendlyUrl.UrlRewriteModule, iFinity.FriendlyUrlProvider" />
- <friendlyUrl defaultProvider="iFinity.FriendlyUrl">
      <providers>
        <clear />
        <add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="HumanFriendly" />
        <add name="iFinity.FriendlyUrl" type="iFinity.DNN.Modules.FriendlyUrl.DNNFriendlyUrlProvider, iFinity.FriendlyUrlProvider" includePageName="true" regexMatch="[^\+a-zA-Z0-9 _-]" urlFormat="HumanFriendly" redirectUnfriendly="true" doNotRedirect="SearchResults;" checkForDupUrls="true" forceLowerCase="false" redirectWrongCase="false" replaceSpaceWith="_" logCacheMessages="false" />
      </providers>
    </friendlyUrl>

One thing that I find a little odd about the Friendly URL's is that I looked for an installed instance of this module/extension and could not find it installed.  It is working though as the other URL's of existing pages don't have tabid's in the path.  I set this up a while ago and my memory escapes me, but it seems as if I did not install a module to execute this.  Is it a built in funciton?

Any new page will throw the error, but for example, if I create the page urltest in the page manager, I will get an error back on http://domain/urltest.aspx.

No errors that I can see.

Thanks again!

There has been a pretty long delay since I first responded to this, I am sending this response to make sure it is not getting rejected because of my web.config references.