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...Administration ...Administration ...duplicate user warning during 3.x to 3.3.5, now userdb is messed upduplicate user warning during 3.x to 3.3.5, now userdb is messed up
Previous
 
Next
New Post
10/26/2006 2:40 PM
 

I had a 3.2.x (I think) site that was working fine except I didn't have my SuperUser password anymore. Luckily I was still logged in on one of my machines but that was not a workable situation. The reason for upgrading to 3.3.5 was that when I asked the site to send me my password it just sent me '****', how helpful :) I remembered reading that that bug was fixed.

During the upgrade there was a warning about duplicate usernames. It seemed pretty harmless so I let it go. There was an error during the upgrade related to this, something about not being allowed to insert NULLs.

Eventually I got my site back up but now I can't log on anymore. I'm still logged in as SuperUser, thankfully, but even that account can't set passwords. Nor can passwords be retrieved. When I try to set the password of the admin account (as SuperUser) I get a red ! icon with the text 'A critical error has occured. Object Reference not set to an instance of an object'.

I have a database copy that has the old user tables in it. Can I use that somehow?

Should I run the upgrade again? Do an install instead?

Thanks!
 
New Post
10/26/2006 3:46 PM
 
Well, I've discovered some more things. First I made a bad mistake when updating my web.config file. I have two DNN installs on the same database so I use an objectQualifier. To make matters more complicated I also needed to use a non-dbo username. I forgot to make these two changes to my web.config file. Or rather the merging of the old with the new did not retain those changes. Sigh.

During the transfer of my DNN site from my previous provider to this one I was given dbo permissions. So when the script ran and created new tables it happily created dbo.bla tables. So now I have tables with the same name, 1 owned by dbo and one by my username. What a mess.

I fixed the web.config file and I'm trying to run the upgrade again. It hobbles along for a while and then bombs:

Installation Status Report
00:00:00.015 - Installing Version: 3.1.0
00:00:00.015 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:00.156 - Installing Script: DotNetNuke.Schema.SqlDataProvider Error! (seeC:\...\Providers\DataProviders\SqlDataProvider\DotNetNuke.Schema.log for more information)
00:00:08.874 - Installing Script: DotNetNuke.Data.SqlDataProvider Error! (seeC:\...\Providers\DataProviders\SqlDataProvider\DotNetNuke.Data.log for more information)
00:00:09.562 - Installing MemberRole Provider:
00:00:09.562 - Executing InstallCommon.sql
00:00:10.296 - Executing InstallMembership.sql
00:00:11.609 - Executing InstallProfile.sql
00:00:12.249 - Executing InstallRoles.sql
Error!


Server Error in '/' Application.
Parameter count does not match Parameter Value count.
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.ArgumentException: Parameter count does not match Parameter Value count.

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:

[ArgumentException: Parameter count does not match Parameter Value count.]
Microsoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValues(SqlParameter[] commandParameters, Object[] parameterValues)
Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues)
DotNetNuke.Data.SqlDataProvider.UpdateDatabaseVersion(Int32 Major, Int32 Minor, Int32 Build) +144
DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +1226
DotNetNuke.Framework.Install.InstallApplication() +1162
DotNetNuke.Framework.Install.Page_Load(Object sender, EventArgs e) +265
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750


That seems fixable but I don't know what causes this mismatch. Anyone?

I was about to throw in the towel and recreate my site but maybe I'll give this some more time.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...duplicate user warning during 3.x to 3.3.5, now userdb is messed upduplicate user warning during 3.x to 3.3.5, now userdb is messed up


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