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 ...New Install of DNN 5.4.4 consistently failsNew Install of DNN 5.4.4 consistently fails
Previous
 
Next
New Post
7/23/2010 3:42 PM
 
Scott Turner

Joined: 3/22/2007
Posts: 9

Attempted install of DNN 5.4.4 Community Install Package - has partialy failed the installation sequence twice now with the same results as below. Website is in accessible - portalalias table empty. Previous versions DNN based websites running fine on server with same setup. 

Ideas anyone as to how to troubleshoot? This a fresh install with correct database setup and correct file system setup...

Installing DotNetNuke

Version: 05.04.04


Installation Status Report

00:00:00.015 - Installing Version: 05.00.00
00:00:00.031 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:20.172 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:25.015 - Installing MemberRole Provider:
00:00:25.015 -   Executing Script: InstallCommon
00:00:25.500 -   Executing Script: InstallMembership
00:00:26.640 -   Executing Script: InstallProfile
00:00:27.328 -   Executing Script: InstallRoles
00:00:27.343 - Upgrading to Version: 05.04.04
00:00:27.359 -   Executing Script: 05.00.01.SqlDataProvider Success
00:00:28.906 -   Executing Script: 05.01.00.SqlDataProvider Success
00:00:37.187 -   Executing Script: 05.01.01.SqlDataProvider Success
00:00:38.234 -   Executing Script: 05.01.02.SqlDataProvider Success
00:00:38.250 -   Executing Script: 05.01.03.SqlDataProvider Success
00:00:38.390 -   Executing Script: 05.01.04.SqlDataProvider Success
00:00:38.406 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log.resources for more information)
00:00:40.906 -   Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log.resources for more information)
00:00:41.125 -   Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log.resources for more information)
00:00:41.156 -   Executing Script: 05.02.03.SqlDataProvider Success
00:00:41.734 -   Executing Script: 05.03.00.SqlDataProvider Error! (see 05.03.00.log.resources for more information)
00:00:43.703 -   Executing Script: 05.03.01.SqlDataProvider Success
00:00:43.703 -   Executing Script: 05.04.00.SqlDataProvider Error! (see 05.04.00.log.resources for more information)
00:00:45.828 -   Executing Script: 05.04.01.SqlDataProvider Success
00:00:45.875 -   Executing Script: 05.04.02.SqlDataProvider Success
00:00:45.984 -   Executing Script: 05.04.03.SqlDataProvider Success
00:00:46.015 -   Executing Script: 05.04.04.SqlDataProvider Success
00:00:46.031 -   Executing Application Upgrades: 05.00.01 Success
00:00:46.078 -   Executing Application Upgrades: 05.01.00 Error!
00:00:46.219 -   Executing Application Upgrades: 05.01.01 Success
00:00:46.250 -   Executing Application Upgrades: 05.01.02 Success
00:00:46.250 -   Executing Application Upgrades: 05.01.03 Success
00:00:47.890 -   Executing Application Upgrades: 05.01.04 Success
00:00:47.890 -   Executing Application Upgrades: 05.02.00 Error!
00:00:48.453 -   Executing Application Upgrades: 05.02.01 Success
00:00:48.469 -   Executing Application Upgrades: 05.02.02 Success
00:00:48.469 -   Executing Application Upgrades: 05.02.03 Success
00:00:48.469 -   Executing Application Upgrades: 05.03.00 Success
00:00:49.375 -   Executing Application Upgrades: 05.03.01 Success
00:00:49.375 -   Executing Application Upgrades: 05.04.00 Success
00:00:50.156 -   Executing Application Upgrades: 05.04.01 Success
00:00:50.156 -   Executing Application Upgrades: 05.04.02 Success
00:00:50.156 -   Executing Application Upgrades: 05.04.03 Success
00:00:50.156 -   Executing Application Upgrades: 05.04.04 Success
00:00:50.156 -   Cleaning Up Files: 05.00.01 Success
00:00:50.156 -   Cleaning Up Files: 05.01.00 Success
00:00:50.172 -   Cleaning Up Files: 05.01.01 Success
00:00:50.172 -   Cleaning Up Files: 05.01.02 Success
00:00:50.172 -   Cleaning Up Files: 05.01.03 Success
00:00:50.172 -   Cleaning Up Files: 05.01.04 Success
00:00:50.172 -   Cleaning Up Files: 05.02.00 Success
00:00:50.172 -   Cleaning Up Files: 05.02.01 Success
00:00:50.172 -   Cleaning Up Files: 05.02.02 Success
00:00:50.172 -   Cleaning Up Files: 05.02.03 Success
00:00:50.172 -   Cleaning Up Files: 05.03.00 Success
00:00:50.172 -   Cleaning Up Files: 05.03.01 Success
00:00:50.172 -   Cleaning Up Files: 05.04.00 Success
00:00:50.172 -   Cleaning Up Files: 05.04.01 Success
00:00:50.172 -   Cleaning Up Files: 05.04.02 Success
00:00:50.172 -   Cleaning Up Files: 05.04.03 Success
00:00:50.172 -   Cleaning Up Files: 05.04.04 Success
00:00:50.172 -   Updating Config Files: 05.00.01 Success
00:00:50.172 -   Updating Config Files: 05.01.00 Success
00:00:50.187 -   Updating Config Files: 05.01.01 Success
00:00:50.187 -   Updating Config Files: 05.01.02 Success
00:00:50.187 -   Updating Config Files: 05.01.03 Success
00:00:50.187 -   Updating Config Files: 05.01.04 Success
00:00:50.187 -   Updating Config Files: 05.02.00 Success
00:00:50.187 -   Updating Config Files: 05.02.01 Success
00:00:50.203 -   Updating Config Files: 05.02.02 Success
00:00:50.203 -   Updating Config Files: 05.02.03 Success
00:00:50.203 -   Updating Config Files: 05.03.00 Success
00:00:50.203 -   Updating Config Files: 05.03.01 Success
00:00:50.203 -   Updating Config Files: 05.04.00 Success
00:00:50.203 -   Updating Config Files: 05.04.01 Success
00:00:50.219 -   Updating Config Files: 05.04.02 Success
00:00:50.219 -   Updating Config Files: 05.04.03 Success
00:00:50.219 -   Updating Config Files: 05.04.04 Success
00:00:50.219 - Performing General Upgrades















Server Error in '/' Application. 




Object reference not set to an instance of an object. 


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.NullReferenceException: Object reference not set to an instance of an object.



Source Error: 





    
        

            The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

            

            1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

            

              <%@ Page Language="C#" Debug="true" %>

            

            or:

            

            2) Add the following section to the configuration file of your application:

            

            <configuration>

               <system.web>

                   <compilation debug="true"/>

               </system.web>

            </configuration>

            

            Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

            

            Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. 		
        

    




Stack Trace: 





    
        

            
            
[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.Entities.Tabs.TabController.GetTabsByNameAndPortal(String TabName, Int32 PortalId) +72 DotNetNuke.Entities.Tabs.TabController.GetTabByNameAndParent(String TabName, Int32 PortalId, Int32 ParentId) +19 DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication() +55 DotNetNuke.Services.Upgrade.Upgrade.UpgradeDNN(String strProviderPath, Version dataBaseVersion) +1044 DotNetNuke.Services.Upgrade.Upgrade.InstallDNN(String strProviderPath) +116 DotNetNuke.Services.Install.Install.InstallApplication() +443 DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +256 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627 

            		
        

    







Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3614



Then after the failed install when trying to access the site:




DotNetNuke Error




 


Domain Name Windows Server 2003 Does Not Exist In The Database 



DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process: 




    
    
  1. Web Server Processing
    
    
      
        
    • When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
      • 
        
    • Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
      • 
        
    • The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.
      • 
    
    
    
    
    
    
    
    2. 
    
  2. HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
    
    
      
        
    • The Request URL is parsed based on the "/" character
      • 
        
    • A Domain Name is constructed using each of the relevant parsed URL segments. 
      
        
      
        Examples: 
      
        
      
        URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
      
        URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
      
        URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
      
        URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
      
        URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory
      
        
      
        
      • 
        
    • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record. 
      
        
      
        Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list. 
      
        
      
        Example: 
      
        
      
        URL: http://localhost/DotNetNuke/default.aspx
      
        URL: http://MACHINENAME/DotNetNuke/default.aspx
      
        URL: http://209.32.134.65/DotNetNuke/default.aspx
      
        PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke 
      
        
      
        Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above. 
      • 
    
    
    
    3. 




										

									

										 
									

								

							

						

					

						
					

						

							

								

									

										New Post

											7/24/2010 4:55 AM
										
 
									

								

							

						

					

						

							

								

									

										Sebastian Leupold
									

								

							

								

							

								
Sebastian Leupold's Avatar		
							

								
Sebastian Leupold's Avatar		
							

								
Sebastian Leupold's Avatar		
							

								
Sebastian Leupold's Avatar		
							

								
www.dnnwerk.de
Joined: 3/8/2004

									Posts: 46212
								

							

						

							

								

									

										
									

										

											

												

													

														
													

												

											

										

									

								

							

								

									

										

											did you make sure, .Net framework 3.5 SP1 is installed on the web server?
										

											
Cheers from Germany,

Sebastian Leupold



dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group


Speed up your DNN Websites with TurboDNN
										

									

										 
									

								

							

						

					

						
					

						

							

								

									

										New Post

											7/29/2010 5:10 PM
										
 
									

								

							

						

					

						

							

								

									

										Todd Allen
									

								

							

								

							

								
www.collectiveDNN.com
Joined: 5/26/2005

									Posts: 3
								

							

						

							

								

									

										
									

										

											

												

													

														
													

												

											

										

									

								

							

								

									

										

											I'm getting the same error installing a new version of 5.4.4 on windows 2003 server with all service packs, .NET 4.0.  I've tried clean installs at least 4 times.  Any ideas?

 


Installing DotNetNuke


Version: 05.04.04






Installation Status Report

00:00:00.150 - Installing Version: 05.00.00

00:00:00.190 -   Executing Script: DotNetNuke.Schema.SqlDataProvider Success

00:00:05.047 -   Executing Script: DotNetNuke.Data.SqlDataProvider Success

00:00:11.286 - Installing MemberRole Provider:

00:00:11.296 -   Executing Script: InstallCommon

00:00:12.027 -   Executing Script: InstallMembership

00:00:12.698 -   Executing Script: InstallProfile

00:00:12.918 -   Executing Script: InstallRoles

00:00:13.469 - Upgrading to Version: 05.04.04

00:00:13.519 -   Executing Script: 05.00.01.SqlDataProvider Success

00:00:14.080 -   Executing Script: 05.01.00.SqlDataProvider Success

00:00:17.194 -   Executing Script: 05.01.01.SqlDataProvider Success

00:00:17.775 -   Executing Script: 05.01.02.SqlDataProvider Success

00:00:17.865 -   Executing Script: 05.01.03.SqlDataProvider Success

00:00:18.045 -   Executing Script: 05.01.04.SqlDataProvider Success

00:00:18.055 -   Executing Script: 05.02.00.SqlDataProvider Error! (see 05.02.00.log.resources for more information)

00:00:19.157 -   Executing Script: 05.02.01.SqlDataProvider Error! (see 05.02.01.log.resources for more information)

00:00:19.357 -   Executing Script: 05.02.02.SqlDataProvider Error! (see 05.02.02.log.resources for more information)

00:00:19.387 -   Executing Script: 05.02.03.SqlDataProvider Success

00:00:19.417 -   Executing Script: 05.03.00.SqlDataProvider Error! (see 05.03.00.log.resources for more information)

00:00:20.309 -   Executing Script: 05.03.01.SqlDataProvider Success

00:00:20.349 -   Executing Script: 05.04.00.SqlDataProvider Error! (see 05.04.00.log.resources for more information)

00:00:21.220 -   Executing Script: 05.04.01.SqlDataProvider Success

00:00:21.270 -   Executing Script: 05.04.02.SqlDataProvider Success

00:00:21.350 -   Executing Script: 05.04.03.SqlDataProvider Success

00:00:21.390 -   Executing Script: 05.04.04.SqlDataProvider Success

00:00:21.410 -   Executing Application Upgrades: 05.00.01 Success

00:00:21.550 -   Executing Application Upgrades: 05.01.00 Error!

00:00:23.093 -   Executing Application Upgrades: 05.01.01 Success

00:00:23.203 -   Executing Application Upgrades: 05.01.02 Success

00:00:23.203 -   Executing Application Upgrades: 05.01.03 Success

00:00:27.529 -   Executing Application Upgrades: 05.01.04 Success

00:00:27.529 -   Executing Application Upgrades: 05.02.00 Error!

00:00:28.551 -   Executing Application Upgrades: 05.02.01 Success

00:00:28.571 -   Executing Application Upgrades: 05.02.02 Success

00:00:28.571 -   Executing Application Upgrades: 05.02.03 Success

00:00:28.571 -   Executing Application Upgrades: 05.03.00 Success

00:00:29.983 -   Executing Application Upgrades: 05.03.01 Success

00:00:29.983 -   Executing Application Upgrades: 05.04.00 Success

00:00:30.824 -   Executing Application Upgrades: 05.04.01 Success

00:00:30.824 -   Executing Application Upgrades: 05.04.02 Success

00:00:30.824 -   Executing Application Upgrades: 05.04.03 Success

00:00:30.824 -   Executing Application Upgrades: 05.04.04 Success

00:00:30.834 -   Cleaning Up Files: 05.00.01 Success

00:00:30.854 -   Cleaning Up Files: 05.01.00 Success

00:00:30.864 -   Cleaning Up Files: 05.01.01 Success

00:00:30.874 -   Cleaning Up Files: 05.01.02 Success

00:00:30.874 -   Cleaning Up Files: 05.01.03 Success

00:00:30.874 -   Cleaning Up Files: 05.01.04 Success

00:00:30.874 -   Cleaning Up Files: 05.02.00 Success

00:00:30.874 -   Cleaning Up Files: 05.02.01 Success

00:00:30.874 -   Cleaning Up Files: 05.02.02 Success

00:00:30.874 -   Cleaning Up Files: 05.02.03 Success

00:00:30.874 -   Cleaning Up Files: 05.03.00 Success

00:00:30.904 -   Cleaning Up Files: 05.03.01 Success

00:00:30.904 -   Cleaning Up Files: 05.04.00 Success

00:00:30.904 -   Cleaning Up Files: 05.04.01 Success

00:00:30.904 -   Cleaning Up Files: 05.04.02 Success

00:00:30.904 -   Cleaning Up Files: 05.04.03 Success

00:00:30.904 -   Cleaning Up Files: 05.04.04 Success

00:00:30.904 -   Updating Config Files: 05.00.01 Success

00:00:30.914 -   Updating Config Files: 05.01.00 Success

00:00:30.934 -   Updating Config Files: 05.01.01 Success

00:00:30.934 -   Updating Config Files: 05.01.02 Success

00:00:30.934 -   Updating Config Files: 05.01.03 Success

00:00:30.934 -   Updating Config Files: 05.01.04 Success

00:00:30.934 -   Updating Config Files: 05.02.00 Success

00:00:30.974 -   Updating Config Files: 05.02.01 Success

00:00:31.004 -   Updating Config Files: 05.02.02 Success

00:00:31.004 -   Updating Config Files: 05.02.03 Success

00:00:31.004 -   Updating Config Files: 05.03.00 Success

00:00:31.024 -   Updating Config Files: 05.03.01 Success

00:00:31.024 -   Updating Config Files: 05.04.00 Success

00:00:31.024 -   Updating Config Files: 05.04.01 Success

00:00:31.024 -   Updating Config Files: 05.04.02 Success

00:00:31.034 -   Updating Config Files: 05.04.03 Success

00:00:31.034 -   Updating Config Files: 05.04.04 Success

00:00:31.034 - Performing General Upgrades











Server Error in '/' Application. 




Runtime Error 

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 



Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".





    
        

            
            
<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="Off"/> </system.web> </configuration>

            		
        

    




Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.





    
        

            
            
<!-- Web.Config Configuration File --> <configuration> <system.web> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/> </system.web> </configuration>

            		
        

    


										

									

										 
									

								

							

						

					

						
					

						

							

								

									

										New Post

											7/30/2010 12:18 AM
										
 
									

								

							

						

					

						

							

								

									

										Scott Turner
									

								

							

								
Joined: 3/22/2007

									Posts: 9
								

							

						

							

								

									

										
									

										

											

												

													

														
													

												

											

										

									

								

							

								

									

										

											The problem with the installation referenced in the original post was due to a SQL Server version issue. It turned out that one of the database servers at our hosting partner had not been upgraded and was still running SQL Server 2000 (which was the database being used for the respective installation). SQL Server 2000 is only supported with DNN 5.1.4 and earlier. Post DNN 5.1.4 requires SQL Server 2005 or later.
										

									

										 
									

								

							

						

					

				

			

				

					

						

							

								

									 Page 1 of 1
								

							

						

					

				

			

				
			

				

					

						

							

								

									

										Previous
									

								
 

									

										Next
									

								

							

						

					

						
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...New Install of DNN 5.4.4 consistently failsNew Install of DNN 5.4.4 consistently fails

					

						

							
    

							

						

					

						
					

						

					

				

			

				

			

		

	









	

	
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. 
    
  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. 
    
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
    4. 
    
  4. No Flaming or Trolling. 
    5. 
    
  5. 
    No Profanity, Racism, or Prejudice. 
    6. 
    
  6. 
    Site Moderators have the final word on approving / removing a thread or post or comment.
    7. 
    
  7. 
    English language posting only, please.
    8. 












  

    

    

    

    

    

    

    

  

  

  
  

  

  	

		
	

	
What is Liquid Content?

  	Find Out
  

  

  	

		
	

	
What is Liquid Content?

  	Find Out
  

  

  	

		
	

	
What is Liquid Content?

  	Find Out