Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade failed from 4.5.1 to 4.5.5upgrade failed from 4.5.1 to 4.5.5
Previous
 
Next
New Post
8/13/2007 4:37 PM
 

Hi,

I have a problem with upgrading a DNN site from 4.5.1 to 4.5.5.
The upgrade procedure started normally, however the 4.5.2 and 4.5.3 sql-db-upgrade scripts failed. See below for the logfile-contents.

The site itself loads normally, login is also possible. Frontpage for example shows all modules normally. Viewing the Host-settings tab reports the new version "04.05.05". But when trying (for example) to edit page-settings of the front-page I get a module-load exeption, and I see only the site-header, but not anymore the modules on the front-page. See below for the exception details.

My question is: is this easy to solve? Edit database manually? Or try to re-run the upgrade-script? This site does not run full production yet, so some trial-and-error is possible.
Problem for me is that all upgrades until so far went without any problem, so this time I skipped the backup..... (so sorry...)

Thanks in advace for all help!

Regards, Jan-Pieter Veen, The Netherlands.

 

Contents of the 04.05.02 log:
"
System.Data.SqlClient.SqlException: The query has been canceled because the estimated cost of this query (69) exceeds the configured threshold of 65. Contact the system administrator.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)


delete
from dbo.DesktopModules
where FriendlyName = 'Solutions' 
"

Contents of the 04.05.03 log:
"
System.Data.SqlClient.SqlException: The query has been canceled because the estimated cost of this query (69) exceeds the configured threshold of 65. Contact the system administrator.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)


delete
from dbo.DesktopModules
where FriendlyName = 'Solutions' 
"

Exception details when trying to edit page-settings:
"
DotNetNuke.Services.Exceptions.ModuleLoadException: Onafgehandelde fout bij toevoegen module aan ContentPane ---> 
             **** this means something as "unhandled fault while adding module to contentpane"
DotNetNuke.Services.Exceptions.ModuleLoadException: Fout: Paginabeheer is op dit moment niet beschikbaar.
             **** this means something as "fault: page-management is not available at this time" 
---> System.Web.HttpParseException: The ID 'cmdDelete' is already used by another control. ---> System.Exception: The ID 'cmdDelete' is already used by another control. ---> System.Web.HttpException: The ID 'cmdDelete' is already used by another control. at System.Web.UI.TemplateParser.ProcessError(String message) at System.Web.UI.TemplateParser.ProcessBeginTag(Match match, String inputText) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---
"

 
New Post
8/13/2007 6:44 PM
 

it looks like either your sql server is too slow, the available RAM not sufficient or the database in a bad condition.

I suggest to revert to a backup and delete first all log entries from the database by executing from Host :: SQL the following commands:

truncate table {databaseOwner}{objectQualifier}Eventlog

truncate table {databaseOwner}{objectQualifier}SiteLog

truncate table {databaseOwner}{objectQualifier}ScheduleHistory

truncate table {databaseOwner}{objectQualifier}SearchItemWordPosition

truncate table {databaseOwner}{objectQualifier}SearchItemWord

truncate table {databaseOwner}{objectQualifier}SearchWord

truncate table {databaseOwner}{objectQualifier}SearchItem

Delete the recycle bin and restart upgrade


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/14/2007 10:22 AM
 

I agree with the above, however, it should be noted that due to the errors that you are getting, you might have to login to the DB as the SA user to be able to actually execute the truncate commands as they too might result in "too expensive" errors.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
8/14/2007 4:07 PM
 

Thanks for the tips. Problem is that I cannot restore a backup.

I tried to run the truncates from within the SQL-tab under Host. This worked out ok. (no too expensive messages).

Next I loaded first the 04.05.02 script into the SQL-tab under Host, and excecuted it as a script. I repeated for 04.05.03, .04 and .05.

But the problem still persist. The whole site works, admin- and host-pages work normally. Only page-settings go wrong with the error
"DotNetNuke.Services.Exceptions.ModuleLoadException: Onafgehandelde fout bij toevoegen module aan ContentPane (*** means Unhandled Error Adding Module to ContentPane") ---> DotNetNuke.Services.Exceptions.ModuleLoadException: Fout: Paginabeheer is op dit moment niet beschikbaar. (*** means something as Error: Page settings are not available at this time ) ---> System.Web.HttpParseException: The ID 'cmdDelete' is already used by another control. ---> System.Exception: The ID 'cmdDelete' is already used by another control. ---> System.Web.HttpException: The ID 'cmdDelete' is already used by another control. at System.Web.UI.TemplateParser.ProcessError(String message) "

What I cannot find in the forums is why it displays "page settings not available at this time". Is there a possible setting somewhere preventing the page-settings from entering during upgrade? Should I alter the database somewhere for this?

The site itself (the rest of it) seems to work normally!

 
New Post
8/15/2007 4:44 PM
 

Things changed. There was a backup...
Backup restored, tables truncated, and after that upgraded again. No errors anymore during upgraded. All db-upgrade-scripts completed ok.

However problem still persists. Page properties still not available. Same exceptions as above. What's wrong???

Then I re-downloaded and re-uploaded all the 4.5.5 upgrade-package files to the site. And guess what? Problem solved!

Final conclusion: this exceptions can be caused by corrupt files. Re-uploading them is always worth a try!

Thanks for your help! Regards,
Jan-Pieter

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...upgrade failed from 4.5.1 to 4.5.5upgrade failed from 4.5.1 to 4.5.5


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out