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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 4.95 to 5.6 was succesful but now Extensions are greyed out on dashboardUpgrade from 4.95 to 5.6 was succesful but now Extensions are greyed out on dashboard
Previous
 
Next
New Post
12/11/2010 7:00 PM
 
I did a test upgrade from 4.95 to 5.6 for one of my sites and it was succesful but now Extensions are greyed out on dashboard.

The related menus bring up blank pages.  There are some other pages that come up blank as well.  Here is a detailed list of the pages that come up blank.

Admin >
Skins - Comes up blank
Languages - Comes up blank
Extensions - Comes up blank
Google Analytics - Comes up blank
Search Engine Sitemap - Comes up blank

Host>
Module Definitions - Comes up blank
Extensions - Comes up blank
Market Place - Comes up blank
Configuration Manager -- Comes up blank


Again there were NO errors during the upgrade that I saw, but in reviewing the Log files in the \Providers\DataProviders\SqlDataProvider folder i found a 05.03.00_Application.log.resources with errors in it.

Error: Invalid column name 'ModuleTitle'.
Invalid column name 'ModuleTitle'.   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.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteScalar()
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters)
   at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues)
   at DotNetNuke.Data.SqlDataProvider.AddModule(Int32 ContentItemID, Int32 PortalID, Int32 ModuleDefID, Boolean AllTabs, DateTime StartDate, DateTime EndDate, Boolean InheritViewPermissions, Boolean IsDeleted, Int32 createdByUserID)
   at DotNetNuke.Entities.Modules.ModuleController.AddModuleInternal(ModuleInfo objModule)
   at DotNetNuke.Entities.Modules.ModuleController.AddModule(ModuleInfo objModule)
   at DotNetNuke.Entities.Modules.ModuleController.DeserializeModule(XmlNode nodeModule, XmlNode nodePane, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules)
   at DotNetNuke.Entities.Tabs.TabController.DeserializePanes(XmlNode nodePanes, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules)
   at DotNetNuke.Entities.Tabs.TabController.DeserializeTab(XmlNode nodeTab, TabInfo objTab, Hashtable hTabs, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Hashtable hModules)
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion_530()
   at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(String strProviderPath, Version version, Boolean writeFeedback)


For the most part the rest of the site works other than a few modules that are not compatable with 5.6 and I will need to obtain the upgrades for them.

Anybody got any ideas of where to even look?

Thanks for the help.


Have a great day!
Larry
 
New Post
12/11/2010 11:01 PM
 
Do you currently or did you at some time in the past use (but later un-installed)  the IFinity URL Master or iFinity Inline Link Master modules?

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
12/11/2010 11:59 PM
 
I currently have the IFinity URL Master installed, I turned it off to do the upgrade but it is still installed. I did however use a clean config file from the Install folder of the 5.6 zip file so there is no reference to it in the config but any dll's or other source is still part of the file system as well as in the database.

Have a great day!
Larry
 
New Post
12/12/2010 7:20 AM
 
Due to a trigger which the iFinity URL Master applied to the Modules table and which references the ModuleTitle field which was removed from the Modules table in DotNetNuke 5.05.00, you must upgrade URL Master to the latest version BEFORE upgrading your site. The trigger is not disabled or removed when you turn off URL Master or even un-install it.

I would suggest rolling back to DNN 4.09.05 using the filesystem and database backup you made before the upgrade, upgrading the iFinity URL Master module, then re-attempting the upgrade to 5.06.00. Also, do NOT use the web.config from the install package. Use the upgrade package which does not include a web.config file. During the upgrade, your existing web.config file will be automatically merged with any changes required for each upgrade version.

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
12/12/2010 8:15 AM
 
Thanks for the information. I will roll back to my backups and give it another go. I wasn't aware that the web.config was automerged with any changes. That will make upgrading much simpler. Thanks for all of your help.

Have a great day!
Larry
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 4.95 to 5.6 was succesful but now Extensions are greyed out on dashboardUpgrade from 4.95 to 5.6 was succesful but now Extensions are greyed out on dashboard


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