Hi, I developped one DotNetNuke application of version 5.01.01 and hosted in my web server, when browsing the dotnetnuke site i am getting the below error message, Please help me to resolve the problem...

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>

Server Error in '/' Application.

---

Runtime Error

The most common cause of this is not changing the connection string to match the hosting environment.

Jeff

Hello fellows,

I have installed DNN many times since v4.5.x and have gone through all settings mistakes and learning. However, I am standing now with no explanation to the error DNN shows up.

1. It is a Shared Hosting (unfortunately), but it hosted up until 10 hours ago a DNN v4.8.0 with no problems (WS 2003, SQL Server 2005).

2. I deleted it and started from scratch, new DB, new DB users (with dbOwner rights), with DNN v4.9.5

3. I am getting the exact same error depicted in the 1st post of this thread.

4. CustomErrors is set to Off.

5. Both Connection Strings have been triple-checked.

6. .NET Framework is 2.0.

7. Full permissions have been granted from root 'public_html' and recursively down for NETWORK SERVICE and ASPNET users.

Yes, I know, move to Dedicated Hosting. I have. But this is a special case... Thanks for the patience and ideas ;-)

Saludos!