THANKS IN ADVANCE FOR *ANY* HELP on this... During an upgrade from 4.5.5 to 5.2.1, everything registered "success", EXCEPT FOR  ONE error of
00:00:26.691 -   Executing Application Upgrades: 05.00.01 Error!

When I pull up the portal, I get a "System.OutOfMemoryException" error that disallows the portal to display at all. (It's on a dual processor with Win2008 Enterprise, 4 GB of RAM, so no hardware issue)

This is a DEV machine, but I'm dead in the water to get to production...ANY HELP ANYONE? THANKS. Patrick

An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Exception of type 'System.OutOfMemoryException' was thrown. ---> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at DotNetNuke.UI.Utilities.Reflection.CreateType(String TypeName, String CacheKey, Boolean UseCache, Boolean IgnoreErrors) at DotNetNuke.UI.Utilities.MSAJAX.get_ScriptManagerType() at DotNetNuke.UI.Utilities.MSAJAX.get_IsInstalled() at DotNetNuke.UI.Utilities.MSAJAX.RegisterStartupScript(Page objPage, String Key, String Script) at DotNetNuke.UI.Utilities.ClientAPI.RegisterStartUpScript(Page objPage, String key, String script) at DotNetNuke.Framework.DefaultPage.InitializePage() in C:\inetpub\wwwroot\SCPortal\Default.aspx.vb:line 224 at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) in C:\inetpub\wwwroot\SCPortal\Default.aspx.vb:line 482 at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

Upgrading DotNetNuke
Current Assembly Version: 05.02.01
Current Database Version: 04.06.00

I found a lot of posts via Google that point to this error as being a memory issue with SQL.

For your local dev machine try restarting SQL then IIS and rehit your site.

I get the same error if I have run 15 or more test installations and not restarted SQL.

I believe the fix is to rejig the memory allocation in SQL Server Main properties but since I don't run into very much, maybe twice in 6 months, I haven't done much investigating.

As to the 5.00.01 error can you post the output of the 5.00.01 log? I'm curious as to what it is showing as a failure there.