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 ...Missing GetDesktopModule procs after botched 4.0.3 upgradeMissing GetDesktopModule procs after botched 4.0.3 upgrade
Previous
 
Next
New Post
7/25/2006 8:52 PM
 

Our shared hosting provided upgraded our DNN3 installation to DNN4.0.3. Unfortunately things didn't go smoothly and a number of errors popped up related to viewing and installing modules while under admin and host modes (specifically, so far, errors indicating missing GetDesktopModulesByPortal and GetDesktopModuleByModuleName procedures). We seem to have fixed these by copying the missing procedures into the db , but now the failure pasted below comes up after an otherwise successful processing of module upload.

So here are some questions:

  • Is there any way to fix all these errors related to Module management with an SQL procedure?
  • Would an upgrade to 4.3.3 replace all the missing procedures?
  • Does the appearance of "PaDnnInstaller_V3" provide any clues? Should this be "V4" instead? If so, what does that mean and any suggestions for a fix?

Thanks everybody.

ExceptionSystem.Data.SqlClient.SqlException: Invalid object name 'dnn_DesktopModules'. 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.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(SqlConnection connection, SqlTransaction transaction, CommandType commandType, String commandText, SqlParameter[] commandParameters, SqlConnectionOwnership connectionOwnership) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.GetDesktopModuleByModuleName(String ModuleName) at DotNetNuke.Entities.Modules.DesktopModuleController.GetDesktopModuleByModuleName(String ModuleName) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstaller_V3.GetDesktopModule(PaFolder Folder) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.ValidateVersion(PaFolder Folder) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.Install(PaFolderCollection folders) at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install() 

 
New Post
7/29/2006 3:49 AM
 
Our solution was to find a fairly recent backup of the DNN3.0.13 database and file system. After confirming that the site was working correctly, we upgraded in step-wise fashion: 3.0.13 -> 3.3.3 -> 4.3.3. At each step we double checked that it was working. We now have a fairly functional site, although we have some File Manager issues that others have been noting on these forums.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Missing GetDesktopModule procs after botched 4.0.3 upgradeMissing GetDesktopModule procs after botched 4.0.3 upgrade


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