Upgrade from Kentico 6 to 8.2

Doug Roberts asked on April 15, 2015 17:54

I am upgrading a pretty advanced installation of an ASPX based website from Kentico 6 to Kentico 8.2, I have successfully gone through each step of the upgrade process to the final 8.2 phase. However once my site has been upgraded to 8.2 I get "The script was registered too soon, no page form nor header was found." whenever I go into the "pages" application on the Kentico main page. This site functioned properly in previous versions. The site uses an advanced master page / user control architecture. Any suggestions on where to start looking for the problem? The error message does not reference which file is causing the error. The full error message I am receiving is:

Description: Message: Exception of type 'System.Web.HttpUnhandledException' was thrown.

Exception type: System.Web.HttpUnhandledException Stack Trace: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.cmstemplates_eventsdc_homepage_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\e2a9caab\d1211ecb\App_Web_homepage.aspx.67978f37.mgbwml48.0.cs:line 0 at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Message: [ScriptHelper.RegisterClientScriptFile]: The script was registered too soon, no page form nor header was found.

Exception type: System.Exception Stack Trace: at CMS.Helpers.ScriptHelper.RegisterScriptFile(PageElement element, String url, Boolean minify) at CMS.Helpers.ScriptHelper.RegisterLoader(Page page, String text) at CMS.PortalControls.CMSPortalManager.CMSPortalManager_Init(Object sender, EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Recent Answers


Kwik Trip Developers answered on April 15, 2015 18:07

Clear the cache in your browser(s) and recycle the app pool. Typically the JS files are cached and cause a lot of problems with it.

1 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on April 15, 2015 20:07

I'd agree with clearing your cache, a very common problem I've experienced with upgrades.

0 votesVote for this answer Mark as a Correct answer

Doug Roberts answered on April 16, 2015 18:21

Thanks for the suggestion, however I tried that and still no luck. Any other ideas on how I can debug this problem?

0 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.