Installed the FriendlyUrlProvider_04.06.11 into my dev box and everything worked fine. Install it on my test box and it works, but I get a weird error. When I click on a link I get the following RTE: Input string was not in a correct format. 

The url at this point is http://foo.com/Default.aspx?tabid=5062. If I navigate to http://foo.com/Managment.html  (by just typing in the URL) - the page comes up fine. As a matter of fact the starting URL is http://foo.com/Home.aspx - any ideas. This is on DNN 4.8.2

There are no significant differences between my dev box and the test box as far as DNN goes that I'm aware of.

Here''s the stack trace (aka Yellow screen of doom)

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2755599
   System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +112
   iFinity.DNN.Modules.FriendlyUrl.UrlRewriteModule.ProcessRequest(HttpContext Context, HttpRequest Request, HttpServerUtility Server, HttpResponse Response) +470
   iFinity.DNN.Modules.FriendlyUrl.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +104
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

 More information. If the links are in this format /tabid/xxx/default.aspx.. everything works fine but if they are in the format of /default.aspx?tabid=xxx  then I get the crash.  And more details - my dev box is a copy of my test box from a couple of days ago.. I have done some changes to the test box since then, but near as i can tell I've reversed all the changes out. Let me know if you need any other information, thanks for the quick response. Also - I'm using the stock example web.config entries provided with the zip file in the example web.config.

Bruce,

Unfortunately I fixed the issue by changing to a backup of the database - but I've run into a new issue - when the site is first hit - we see a HUGE memory spike upwards of 900 Megs by the w3wp.

When the provider is first building the cache is it building the cache for ALL the portals in an instance for just the one that's being requested? In our system we have 200 + portals and 76774 tabs. Each individual portal doesn't see a large amount of traffic on a daily basis.  The problem we are having is it's takeing FOREVER to get the first site loaded after an application restart.  On the order of 30 minutes MINIMUM.

We ran into this problem with the stock DNN core code, turns out there's a section where the portal ID isn't being passed down to a lower level call when asking for tabs, so it would return ALL the tabs for ALL the portals with every call.. Not a problem once or twice, but do that a bunch of times and performance TANKS.

Is it possible to get the source code to review what's happening?

Thanks.