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 ...Generate Usernames and PasswordsGenerate Usernames and Passwords
Previous
 
Next
New Post
8/19/2009 10:37 PM
 

How can I create user names and passwords?

I inherited a website that was first developed by someone else back in 2004 using DNN (version unknown). I was asked to upgrade the site to the latest version of DDN, which I did earlier today. But when I browse to the updated website, it simply prompts for username and password on the main web page (forms authentication?). It retained my user names in dbo.Users (Admin and Host), but no passwords. The new tables aspnet_users and aspnet_members are both empty tables. It it does me no good to click Forgot Password on the web page.

When I click Register on the main web page, is it suppose to add my specified user and password to the database? If so, it doesn't seem to be working. My aspent_<table_names> remain empty. I'm stuck at this point with no valid user names and passwords.

How do I go above fixing this problem? Is there a way that I can insert user names and passwords into the necessary tables?

 
New Post
8/20/2009 3:52 AM
 
  • which version has been installed before?
  • if aspnet membership and users table are empty, the upgrade failed. these tables need to be populated
  • make sure to keep machine key in your web.config file
  • you may want to validate your upgrade procedure against this check list.

 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
8/20/2009 8:21 AM
 

The original website (an Intranet site) is still in-tact. How can I determine the DNN version of this original site?

The web.config for the original website does not have a machineKey. Does that mean anything? My new web.config does have a machinekey.

Some additonal background: In case something went wrong, I did not want to upgrade over top of the original site. So I copied the root of the original site (including all files and subfolders) to another IIS machine. I made sure that ASPNET had full control to the root portal on the new IIS machine and that the property settings of the new virtural directory matched the property settings on the original machine. I then detached the DNN database from the original SQL Server and copied it over to the new IIS machine (which is also running SQL Server). I attached the database and created the same SQL account to match the account used by the original machine. After making this SQL account the dbo of the database, I made sure that the account could access the DNN database. I then updated the connectionString in web.config to point to the new SQL Server. Then I extracted DNN 5.1.1 to the root of the new website and began the install.

I appreciate the check list that you have provided and I am going thru it now.

Thank you.

 
New Post
8/20/2009 10:11 AM
 

Additional info; I made sure that the virtual directory on the new IIS machine is using ASP.NET 2.0. This is currently the only website on my new IIS machine, so I did not concern myself with assigning it its own application pool.

I have confirmed that both datebase connection strings within the new web.config point to the correct database, using the correct User ID and Pwd. BTW, the original web.config has only one connectionString= located within <appSettings>. It does not have a <connectionStrings> node.

Also, the original web.config does not have encryption keys. It does have codeSubdirectories and I copied the DataBaseOwner and ObjectQualifier keys to the new web.config, but I find no encryption keys in the original web.config. And it has no machinekey either.

More Background: During the install of DNN 5.1.1, the Installwizard.aspx seemed to enter some sort of infinite loop, where it repeatedly displayed Undefined:Success. While this was occurring, I found several suggestions within the forums to run Install.aspx instead of InstallWizard.aspx. I got much better results with Install.aspx. Most installation components were successful, but I got about a dozen error logs that ranged from  02.02.01.log  to  05.01.01.log. I went thru each error log yesterday, fixing whatever the log reported as being wrong. I then ran Install.aspx again and it generated about 3 more error logs and I fixed the problems that were reported by those logs as well. I ran Install.aspx a third time and it displayed the message like Installation Complete, and it also displayed a hyperlink that read Click here to enter your portal. And that is where I am currently at. I am viewing the root of my portal (Default.aspx), which looks exactly like the home page on the old, original DNN website, except that on this new site, I have boxes for entering Username and Passwords, but it excepts no names or passwords that I enter. As soon as I click the Logon button, it clears out the username and password that was entered, and waits for me to reenter another username and password (BTW, if I go back and try to run Install.aspx again, I simply get a blank page).

I really don't want to install DNN 5.1.1 directly over top the original website, b/c it is a production site that is used daily by employees. If that site is down during business hours, I will be in big trouble. If I had a better understanding with what I was doing, I would wait and come in on Saturday, and upgrade the site to DNN 5.1.1. But at this point, I don't feel confident that I could have the site back up and running by Monday morning.

I've been exposed to DNN for one full week now and I'm really stumped on what to do next. Should I wipe out the test environment on my new IIS machine and start over? If so, what should I do differently? I went thru the following guides and I don't think I overlooked anything:

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1228/This-is-how-I-upgrade-a-DNN-instance.aspx
http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/1459/Upgrading-DotNetNuke.aspx
http://www.deutschnetnuke.de/AboutDotnetNuke/V3V4TippsTricks/Upgradedurchführen.aspx
 

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Generate Usernames and PasswordsGenerate Usernames and Passwords


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