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...Can't log in after 7.1 upgrade.Can't log in after 7.1 upgrade.
Previous
 
Next
New Post
7/19/2013 3:31 PM
 
According to the signature of the call in DotNetNuke.Security.Membership.Data.SqlDataProvider.UpdateUser of stored procedure UpdateUser as updated in 07.01.00.sqldataprovider, there is a parameter mismatch, caused by an additional "vanityName" in the stored procedure.
it looks like you are still using an old version of dotNetNuke.dll, is this possible? please check version and date

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
7/22/2013 5:40 PM
 

I just re-copied everything over from a freshly downloaded upgrade package and still no luck. 

 
New Post
7/22/2013 6:52 PM
 
As Sebastian says it looks like you have a mismatch between the DB and the code.

The safest way to fix this is always to recover a matched set of Database and site files and have another go.

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
7/23/2013 7:34 PM
 

The problem is my backup was corrupted so no recovery (otherwise I would have done that already). Is there any other option or am I just up the creek? I really don't want to re-create 2 years worth of postings.

Maybe a way of forcing it to re-run the DB scripts?

 
New Post
7/26/2013 1:14 PM
 
I'm continuing to dig and here is what I'm finding:
The login is successful. In the eventLog table, it logs a LOGIN_SUCCESS event. The very next event is a PAGE_LOAD_EXCEPTION and that is what is throwing the error.

Here is the raw XML from the LogProperties field:
AssemblyVersion7.1.0PortalID0PortalNameGunNoobUserID-1UserNameActiveTabID55ActiveTabNameHomeRawURL/login.aspx?ReturnUrl=/&popUp=trueAbsoluteURL/Default.aspxAbsoluteURLReferrerhttp://www.gunnoob.com/login.aspx?ReturnUrl=/&popUp=trueUserAgentMozilla/5.0 (Macintosh; Intel Mac OS X 10_8_4) AppleWebKit/536.30.1 (KHTML, like Gecko) Version/6.0.5 Safari/536.30.1DefaultDataProviderDotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProviderExceptionGUID66869f06-8af7-4400-8295-6fc720f212c9InnerExceptionParameter count does not match Parameter Value count.FileNameFileLineNumber0FileColumnNumber0MethodMicrosoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValuesStackTraceMessageDotNetNuke.Services.Exceptions.PageLoadException: Parameter count does not match Parameter Value count. ---> System.ArgumentException: Parameter count does not match Parameter Value count.
at Microsoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValues(SqlParameter[] commandParameters, Object[] parameterValues)
at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)
at DotNetNuke.Security.Membership.Data.SqlDataProvider.UpdateUser(Int32 userId, Int32 portalID, String firstName, String lastName, Boolean isSuperUser, String email, String displayName, Boolean updatePassword, Boolean isApproved, Boolean refreshRoles, String lastIpAddress, Boolean isDeleted, Int32 lastModifiedByUserID)
at DotNetNuke.Security.Membership.AspNetMembershipProvider.UpdateUser(UserInfo user)
at DotNetNuke.Entities.Users.UserController.UpdateUser(Int32 portalId, UserInfo user, Boolean loggedAction, Boolean clearCache)
at DotNetNuke.Entities.Users.UserController.UserLogin(Int32 portalId, UserInfo user, String portalName, String ip, Boolean createPersistentCookie)
at DotNetNuke.Modules.Admin.Authentication.Login.ValidateUser(UserInfo objUser, Boolean ignoreExpiring)
at DotNetNuke.Modules.Admin.Authentication.Login.UserAuthenticated(Object sender, UserAuthenticatedEventArgs e)
at DotNetNuke.Modules.Admin.Authentication.Login.OnLoginClick(Object sender, EventArgs e)
at System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---
Source
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Can't log in after 7.1 upgrade.Can't log in after 7.1 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