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 to 4.6.2 from 3.0.13Upgrade to 4.6.2 from 3.0.13
Previous
 
Next
New Post
11/19/2007 3:08 PM
 

Hey all. I have finally gotten to the big jump from 3.3.7 to 4.3.7 and wanted to know what the procedure is. I haven't really had much luck here in the forums. Can anyone out there give me some upgrade tips?

I have copied the files over, changed the machine key, decryption key, and connection strings. I added the Installation Date Key too. I also changed the website to use my .NET 2.0 application pool and changed the ASP.NET version to the 2.0 framework in IIS. When I browse to the website, I see that the site is unavailable with the 'please come back later' message - Looks good so far. However, when I point my browser to the /install/default.aspx page, I get an error stating the following:

@CurrentTimeUtc is not a parameter for procedure aspnet_Membership_GetUserByName.

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.Data.SqlClient.SqlException: @CurrentTimeUtc is not a parameter for procedure aspnet_Membership_GetUserByName.

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. 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:

[SqlException (0x80131904): @CurrentTimeUtc is not a parameter for procedure aspnet_Membership_GetUserByName.]
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +862234
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739110
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1956
System.Data.SqlClient.SqlDataReader.ConsumeMetaData() +31
System.Data.SqlClient.SqlDataReader.get_MetaData() +62
System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +297
System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +903
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132
System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +32
System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +122
System.Data.SqlClient.SqlCommand.ExecuteReader() +84
System.Web.Security.SqlMembershipProvider.GetUser(String username, Boolean userIsOnline) +1491
System.Web.Security.Membership.GetUser(String username, Boolean userIsOnline) +81
System.Web.Security.Membership.GetUser(String username) +6
DotNetNuke.Security.Membership.AspNetMembershipProvider.GetUserMembership(UserInfo& user) +21
DotNetNuke.Entities.Users.UserInfo.get_Membership() +69
DotNetNuke.Entities.Users.UserInfo.set_Username(String Value) +18
DotNetNuke.Security.Membership.AspNetMembershipProvider.FillUserInfo(Int32 portalId, IDataReader dr, Boolean isHydrated, Boolean CheckForOpenDataReader) +722
DotNetNuke.Security.Membership.AspNetMembershipProvider.GetUser(Int32 portalId, Int32 userId, Boolean isHydrated) +43
DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +798
DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +83
DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +5776
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Any Ideas? TIA!


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
11/19/2007 4:14 PM
 

Ok, it would seem that I had to simply add the install mode argument to the url... and everything seems to have gone ok on the surface.... will post back when I have more.


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
4/14/2008 6:06 PM
 

Its been a while since I updated this post. I was pulled off to work on another project. I am back on this project for about 50% now. So here is my issue. I typed the url in with the mode argument and I am still not able to get the site to upgrade on our production server. I think I may need to bounce IIS/ or worse the server itself.

I'll post back when I find out what the deal is. But if anyone can point me in the right direction, I would be very greatful.


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
New Post
4/15/2008 11:44 AM
 

I did some digging and found some articles about upgrading IIS after installing the Microsoft.NET 2.0 framework. Unfortunately, it recommends running "aspnet_regiis -i". I strongly disagree with that approach (I am running both 1.1 and 2.0 apps in production); however, running the appropriate commands doesn't seem to have helped. Now I am afraid that I will have to go ahead and bounce the production server to get the apps to recycle properly. I gotta wait until midnight to perform this operation... so I suppose I have waisted another day.

Can anyone else think of anything that may point me in a new direction? I wonder if there is something I am overlooking... I am still getting the same error I posted above, and I have no answers to why I was able to upgrade my QA environment, but not my production environment.

The only configuration difference is that I have only 2.0 apps in QA, but the production server runs both 1.1 and 2.0 apps. So running aspnet_regiis with the -i flag is not an option.

For those of you who are curious, I ran the following 2 commands:

  1. aspnet_regiis -ir -enable : this registers the framework with IIS but doesn't update any of the script maps in the web roots.
  2. aspnet_regiis -s W3SVC/<identifierForMyAppFoundInIIS> : this updates the script maps for this site (and subdirectories) only; thereby eliminating the possibility of breaking my 1.1 apps.

Does anyone have any idea's?


Cheers!
John Valentine
http://www.webinnovationsystems.com
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Upgrade to 4.6.2 from 3.0.13Upgrade to 4.6.2 from 3.0.13


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