Products

Solutions

Learn More

Partners

Community

Blog

About

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 ...Can't login anymoreCan't login anymore
Previous
 
Next
New Post
1/20/2014 11:45 AM
 

What version of DNN was running on the site before the problem started?
Version 6. I don't know which version exactly.

Did you recently upgrade the DNN platform framework or a module. If so, to what version?
No

Did you create a backup of the site's files and database before attempting any upgrades?
Not relevant

Describe in detail how you added another site or DNN installation to the server?
First I had a URL-registration transfered to the hosting provider I'm now working with.
Then I tried to install the DNN-app that it provides again. (I think this was a mistake, I don't need a second DNN installation, I need another portal...)
Then I got the Install Wizard when I visited the website at the correct URL.
I had problems getting the Install Wizard to work, but I did manage to do so. I used the same database that I allready created for my first website. (Though I did create another database when trying to get the Install Wizard to proceed)
The installation didn't go succesfully, I got this error.
After this, my initial first website was down as well.

Do you have access via FTP to the site's files?
Yes

Do you have remote access to the site's MS SQL database?
No

Have you tried restarting the site's application pool on the server? Usually this can be done from your hosting provider's control panel, if not then by re-saving the site's web.config file on the server.
Yes, didn't help unfortunately.


Thank you very much for trying to help!

 
New Post
1/20/2014 11:54 AM
 
I altered the web.config and managed to get more info about the error. Doe this help any? It says:


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:


Line 130: if (portalSettings != null && !String.IsNullOrEmpty(portalSettings.LogoFile))
Line 131: {
Line 132: IFileInfo fileInfo = FileManager.Instance.GetFile(portalSettings.PortalId, portalSettings.LogoFile);
Line 133: if (fileInfo != null)
Line 134: {
 
New Post
1/20/2014 6:05 PM
 

Ouch! That's what I was afraid you'd say regarding how you "added another site" to your DNN installation. Depending on how the hosting provider's DNN installer handled an installation over an existing site, you've basically done a failed upgrade from DNN 6.x to probably 7.1.x with the added problem that the site's web.config file was overwritten by that of the new install. Hence the reason that the install wizard appeared. My guess is that the database upgrade ran successfully before the install/upgrade failed.

At any rate, your best hope is to contact the hosting provider immediately to see if they have a backup of the installation's files AND database taken prior to your trying to add the second site. If so, it would be best to roll the site and database back to that from the backups. Most likely you will need help from the hosting provider to restore the database backup.

If the hosting provider does not have a backup of the site and database - and most likely they won't if it's been more than 2 or 3 days since the "upgrade" happened - we'll have to try to sort out exactly what has been broken and try to repair the site.

Here's some more questions and info needed if the hosting provider cannot restore from their backups:

1. Via FTP download the file dotnetnuke.dll from the site's /bin folder. On your local machine right click on the file, select "properties" from the context menu, and make note of  the file and assembly version #.

2. Via FTP examine the site's  /Providers/DataProviders/SqlDataProvider folder. Note the highest version number of the xx.xx.xx.SqlDataProvider files. Also look for xx.xx.xx.log.resources files. Any with xx.xx.xx greater than your DNN version # prior to the upgrade that are more than 1KB in size will contain errors logged during upgrade of the database.

3. Also via FTP look at the site's /Portals/_default/Logs folder for files that have names like InstallerLog#######.resources. Where ####### should be the date of the install/upgrade. These may contain other errors that were logged during the install/upgrade.

4. Do you happen to have a local backup of the site's web.config file that was made sometime (anytime!) before the problem occurred?

5. How critical is it to restore the site? Did it contain mostly text/html modules whose content can be recreated?


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
1/21/2014 3:04 PM
 

Thanks for your help!
I've mailed my hosting provider, hope they can help me. I was only starting up my website yet, so it wouldn't be a big deal if things got lost.

1. Via FTP download the file dotnetnuke.dll from the site's /bin folder. On your local machine right click on the file, select "properties" from the context menu, and make note of  the file and assembly version #.
Fileversion: 6.2.4.63
Assembly version: 6.2.4.63

2. Via FTP examine the site's  /Providers/DataProviders/SqlDataProvider folder. Note the highest version number of the xx.xx.xx.SqlDataProvider files. Also look for xx.xx.xx.log.resources files. Any with xx.xx.xx greater than your DNN version # prior to the upgrade that are more than 1KB in size will contain errors logged during upgrade of the database.
Highest number: 06.02.04.SqlDataProvider
No log-files larger than 1KB

3. Also via FTP look at the site's /Portals/_default/Logs folder for files that have names like InstallerLog#######.resources. Where ####### should be the date of the install/upgrade. These may contain other errors that were logged during the install/upgrade.
There are no InstallerLog-files there. There are #######.log.resources though. I found two different errors in there:
1)
2014-01-18 08:57:06,393 [S083][Thread:227][FATAL] DotNetNuke.Framework.PageBase - An error has occurred while loading page.
System.Web.HttpException (0x80004005): The file '/Admin/ControlPanel/ControlBar.ascx' does not exist.
2)
2014-01-18 08:57:06,549 [S083][Thread:227][FATAL] DotNetNuke.Web.Common.Internal.DotNetNukeHttpApplication - System.Web.HttpException (0x80004005): Error executing child request for /ErrorPage.aspx. ---> System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.ArgumentException: Parameter count does not match Parameter Value count.

4. Do you happen to have a local backup of the site's web.config file that was made sometime (anytime!) before the problem occurred?
No I don't. But see question 5, maybe it wouldn't matter that much.

5. How critical is it to restore the site? Did it contain mostly text/html modules whose content can be recreated?
It's not critical. If I would have two blank websites for the two URL's I have, I would be very happy. All content can easily be recreated.

Thank you!! 

 
New Post
1/24/2014 6:38 AM
 
Could you please help me out once more?!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Can't login anymoreCan't login anymore


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out