Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...Installation Wizard ErrorInstallation Wizard Error
Previous
 
Next
New Post
2/8/2011 2:19 PM
 
khashayar parhami


Joined: 2/7/2011
Posts: 11
sorry for the long post , I started from the begining and recieved another failure message as follow :

Installing Database - Version 05.00.00...Success
Upgrading Database to Version 05.00.01...Success
Upgrading Database to Version 05.01.00...Success
Upgrading Database to Version 05.01.01...Success
Upgrading Database to Version 05.01.02...Success
Upgrading Database to Version 05.01.03...Success
Upgrading Database to Version 05.01.04...Success
Upgrading Database to Version 05.02.00...Success
Upgrading Database to Version 05.02.01...Success
Upgrading Database to Version 05.02.02...Success
Upgrading Database to Version 05.02.03...Success
Upgrading Database to Version 05.03.00...Success
Upgrading Database to Version 05.03.01...Success
Upgrading Database to Version 05.04.00...Success
Upgrading Database to Version 05.04.01...Success
Upgrading Database to Version 05.04.02...Success
Upgrading Database to Version 05.04.03...Success
Upgrading Database to Version 05.04.04...Success
Upgrading Database to Version 05.05.00...Success
Upgrading Database to Version 05.05.01...Success
Upgrading Database to Version 05.06.00...FAILURE ERROR: Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)
at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()
at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String strProviderPath, String strConfigFile, Version version, String strReason)
Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)
at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()
at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String strProviderPath, String strConfigFile, Version version, String strReason)
Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)
at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()
at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String strProviderPath, String strConfigFile, Version version, String strReason)
Error: Object reference not set to an instance of an object. at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)
at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)
at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()
at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String strProviderPath, String strConfigFile, Version version, String strReason)
 
New Post
2/8/2011 4:17 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
It would appear that either

1. The ASP.Net worker process account did not have necessary file system permissions on the root install folder of the site so that it could not make changes to web.config or

2. The structure of the web.config file was corrupted so that the XmlMerge utility could not locate the nodes within web.config where changes were to be made.

If possible, please check the database to see if any tables and stored procedures had been created by the DotNetNuke installation and let us know if they were or not.

Then, delete all of the DotNetNuke folders and files from the installation folder and delete the database so that you can start fresh. Here's a short refresher of the install procedure:

1. Download a fresh copy of the DotNetNuke_Community_ 05.06.01_Install.zip package, "unblock" the zip folder and extract it into an empty folder.
2. Make sure that the ASP.Net worker process account (IIS Identity account) has full file system permissions including modify on the root folder of the install and that file system permissions will be inherited by child folders of the root as they are created.
3. Copy or upload all of the folders and files extracted from the Install package to the root install folder.
4. Do not manually modify the web.config file.
5. Create a new MS SQL Server 2005/2008 (Express or Standard) database and a new database user login (SQL Authentication with username and password).
6. Make sure that ASP.Net 4.0 or ASP.Net 3.5 SP1 has been selected for the ASP.Net version for the site's IIS AppPool. If you have a choice of classic or integrated pipeline mode in IIS, select Integrated.
7. Browse to the site to trigger the installation.
8. When entering the database information in the Install Wizard, make sure that you select SQL Server 2005/2008 and NOT SQL Server 2005/2008 Express even if your database server is the Express version. Uncheck Integrated security so that you can enter the database username and password.

Hopefully all will go well this time!
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
2/9/2011 1:47 AM
 
khashayar parhami


Joined: 2/7/2011
Posts: 11
Dear William,
The above mentioned error still happens. I checked the DataBase and there are (89) tables and (19) views created.
I don't have the Dotnetnuke installed yet.

thanks for your helps
 
New Post
2/9/2011 2:57 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Since it appears that it was possible for the installer to create objects in the database, we know that the connection to the database was correct. Please double and triple check that the ASP.Net worker process account has been granted full file system permissions on the root folder into which DotNetNuke will be installed, then delete all folders and files under this root folder and delete then recreate the MS SQL database. It is important that you start with an empty file system and blank database before reattempting the install. Then, follow my basic outline of steps when reattempting to install.
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
2/10/2011 2:10 PM
 
khashayar parhami


Joined: 2/7/2011
Posts: 11
I downloaded the latest version and installed it on the web hosting . the problem solved.

thank you very much William
 
 Page 2 of 2
Previous12 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation Wizard ErrorInstallation Wizard Error


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