Sorry I have a lot of posts in different areas this lists some of the problems I've been having

http://dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/107/threadid/63402/scope/posts/Default.aspx

So summarize as I've been working long/late hours on this without success.

Since I was having those [DROPDOWNACTION] container problems I thought I'd revert to 4.0.3, the same as my internal site. Still the export wouldn't work so I worked on re-creating ALL the pages again, this is a large site. Last night was the last straw out of nowhere I get another server configuration error

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>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

Surely there is a way to create a dotnetnuke site and simply have do a restore database. I'm thinking that would have been a great feature.

Glad to receive help today!

• IIS is running 2.0.50727
• I created a new application pool and pointed to it.

I get the exact same error.

this is the site - http://209.217.91.7/

Here's a little bit of history on the problems I've been having. First it started with exporting the internal site to the live server.

I downloaded lastest dotnenuke 4.3.4 install. I unzipped it on my computer then uploaded all the files to the new site. - first mistake?

I edited the dotnetnuke.install.config file as per your configuring tutorial and uploaded the file to the install file. The only difference is you call it dotnetnuke.install.resources.

I edited the config file for sql connections.

I get a 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>

And have the customErrors mode="Off" in the config file.

I've been searching all day and it looks like an IIS issue and have set all the correct permissions but no chance of the site loading.

Did I go drastically wrong somewhere I don't know where else to check for errors.

_______________

I have done all I should and going through Wizard. It seems to stall there. When I go in a peak using another browser it's like it only gets a portion of the downloads - lots of pages missing etc.
I then expanded the config executionTimeout =600 and maxRequestLength=81920 and I got more files downloaded but the page doesn't give me a final complete. And if I go in there's lots of pages/files/images that haven't been uploaded.

I really did a lot of work on my internal site and would hate to have to go page by page and replace but is that my only alternative cause I'm getting no joy out of the wizard.

________________

I have worked nearly 30 hours solid on getting my live site working. This morning I decided to go back to 4.03 since it's been fine on my testing server. I got the basic site working and since export feature doesn't work for me (before and after new installation) I spent the day creating and populating my pages once again from scratch again.

I was doing great then all of a sudden I get a runtime error that tells me to set my config file -
the same error I got yesterday. the same fault I've seen on dotnetnuke. I haven't funny enough seen it on this site that's why I still have little faith in dotnetnuke. That and my internal site is working fine.

The worst is I don't even know how to solve the problem. There's got to be some difference in my settings between the servers. That's why I thought I'd do a fresh installation and I wsa doing great until without a word of warning I get an error. Is dotnetnuke that unstable?

It would really be nice to be able to create a clean site then simply update databases with all your information on. Believe me I've tried that also to no avail.

__________________________

Please let me know if there's any further specs I can give you. You can see that I've really been trying every avenue with little success but I do appreciate your assistance.

Since my site works without problem on my internal server it must have something to do with a setting that I'm overlooking.

<add name="SqlDataProvider" type="DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider" connectionStringName="SiteSqlServer" upgradeConnectionString="" providerPath="~\Providers\DataProviders\SqlDataProvider\" objectQualifier="" databaseOwner="MyDBONameIsNowHere" />

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>