SEARCH
Knowledgebase: Third Party Applications
DotNetNuke (DNN) Installation using "Typical" install option stuck on "Running Database Installation Scripts" [Fix+Workaround]
Posted by on 02 February 2011 02:04 AM

This issue is often caused by issues related to permissions or wrong ASP.NET version set.Two things to try:

 

1) The most likely issue is that you have not set ASP.NET to 2.0 in your control panel for the specific site. This can be done from the website properties(click on the website, then click on Extensions). The default is 2.0(Integrated Pipeline), that is not the same as 2.0 so switch it to just 2.0 with no Integrated Pipeline.

 

2)If that doesn't fix the issue, and research doesn't point to the exact issue, you can use the following Workaround:

 

Simply choose "Typical" setup, then fill in the proper database name, user, pass(choose to not run as owner). Then, click next. It will start the "Running Database Installation Script" but nothing will happen like before. Simply refresh the page, you will then be given the choices:

-Custom

-Typical

-Auto

 

As you may have noticed, "Auto" was previously blurred out. It is now an available choice(because the Typical option updated the web.config with the proper database user/pass). Choose Auto and it will work.

(9 vote(s))
Helpful
Not helpful
Comments (2)
Stasi
13 June 2011 09:03 AM
ok, will give that a try....otherwise, can i just install via FTP and unzip, run it manually as if i were installing it locally to my own pc?
Arvand Sabetian
14 June 2011 09:54 AM
Yes but you still need to set the extension to 2.0 through the control panel. (Or 4.0 if the latest version supports .NET 4.0)
Post a new comment
 
 
Full Name:
Email:
Comments:
CAPTCHA Verification 
 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).