DotNetNuke failed install

Hello,

Long time user of DNN but first time installer, and I think I've got it just about as wrong as is possible.

I have a domain and uploaded all the install files to the ftp after editing the web.config file as instructed. First install got to the point where it began generating the site but then crashed. When attempting to access the site it said dnn was not installed properly.

I removed the files from the subfolder on ftp (for help purposes I'll say the subfolder is called DNNi) so then there was only the bin and _database folders.

Since this I have tried many things, ranging from uploading into the root, into another subfolder, but the furthest I have got is the sql scripts page, but it just kept generating rows of "undefined - success". After an hour or so of watching countless rows I cancelled this action.

Now when I upload the files to ftp and go to the directory I return error page of "set customerrors to Off" (which doesn't work)
Each time I have checked the IIS is set to 2.0 or higher and then enabled the application.

Can anyone come up with some ideas or suggestions of what I can do to resolve this.

Greatly appreciate any help

Jason

 

What's the full error message?

 

Server Error in '/' Application.

Runtime Error

[FONT=Arial, Helvetica, Geneva, SunSans-Regular, sans-serif]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>[/FONT]

 

You have custom error enabled. Turn off custom error on your applications configuration file so that we can see the true error message. From there we'll see what the next step will be to get your DNN up and running.