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 ...Wrong Database after 3.3.7 Upgrade ??? HELP!Wrong Database after 3.3.7 Upgrade ??? HELP!
Previous
 
Next
New Post
12/6/2006 7:02 AM
 

I'm not so sure the update even started. I unzipped the 3.3.7 upgrade into the directory including the modified web.config file. Then, I hit the site and got the "Runtime" error I mentioned above, so I hit refresh for the heck of it and I got the following message which is why I "assumed" the wrong database version..

DotNetNuke Upgrade Error

The Assembly Version ([ASSEMBLYVERSION]) does not match the Database Version ([DATABASEVERSION])

Error" Cound not connect to database.

The stored procedure 'dbo.GetPortalAliasByPortalID' doesn't exist.

I've only found one other person with this same error message but I've gotten no response to their fix for it. I've also gone through the web.config file to see if I can find anything that tried to match a database version and assembly version but I didn't see anything at first glance.


Mike DeBaise President/CEO Trial by Fire Web Design, LLC. URL: www.TBFWD.com Email: President@TrialByFireDesigns.com
 
New Post
12/6/2006 7:12 AM
 

I found a " />" that was missing in the web.config file, hitting the site again resulted in the following;

  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: Couldn't load <profile> configuration section

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[Exception: Couldn't load <profile> configuration section]
   Microsoft.ScalableHosting.Profile.ProfileBase.InitializeStatic() +1210
   Microsoft.ScalableHosting.Profile.ProfileBase.Create(String username, Boolean isAuthenticated) +50
   DotNetNuke.Entities.Users.UserController.FillUserProfile(UserInfo objUserInfo) +158
   DotNetNuke.Entities.Users.UserInfo.get_Profile() +50
   DotNetNuke.Entities.Users.UserInfo.get_FirstName() +32
   DotNetNuke.Entities.Users.UserController.FillUserInfo(IDataReader dr, Int32 PortalId) +810
   DotNetNuke.Entities.Users.UserController.GetUser(Int32 PortalId, Int32 UserId) +94
   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +761
   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +93
   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3717
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87

Server Error in '/' Application.

Couldn't load <profile> configuration section

 


Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300


Mike DeBaise President/CEO Trial by Fire Web Design, LLC. URL: www.TBFWD.com Email: President@TrialByFireDesigns.com
 
New Post
12/6/2006 9:27 AM
 
The 3.3.7 web.config file does not have a <profile> section, but the 3.2.2 web.config did. Again, it appears that the 3.2.2 version of DotNetNuke.dll in the \bin folder of the website did not get replaced by the 3.3.7 version.  I suspect this may have happened with other files as well.  I would try unzipping the original download of the new 3.3.7 version update (again being careful not to overwrite the necessary database connection string, databaseOwner, objectQualifier and machine keys) and reload them to the server.

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/6/2006 9:38 AM
 

Perhaps I unzipped these files in the wrong area. The instructions say to do so in the main directory, but like I said I don't think that the installation even started so no files would have been changed yet. I'm almost to the point of going back to HTML because DNN isn't as seemless as I once thought.

 


Mike DeBaise President/CEO Trial by Fire Web Design, LLC. URL: www.TBFWD.com Email: President@TrialByFireDesigns.com
 
New Post
12/16/2006 7:13 PM
 

Any luck with this upgrade?  I'm doing the same upgrade and getting the same error, however mine is less helpful.  After adding the 3.3.7 dotnetnuke.dll to the server /bin folder the under construction page never came up.  Instead I got the runtime error telling me to turn the custom errors off.  I did this and the same error still shows up.  No differencee. 

I went ahead and uploaded all 3.3.7 files over the top of the 3.2.2 files and tried the install (/Install?mode=install) - nothing except the same runtime error about custom errors.  If I try and hit the site www.vasus.com it just endlessly loads and nothing.  Any help would be extremely helpful. 

Godaddy shared server and Asp.net 1.1

Thanks,

ian

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Wrong Database after 3.3.7 Upgrade ??? HELP!Wrong Database after 3.3.7 Upgrade ??? HELP!


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