Dear Admin,

         My site is hosted by datapacket.net. As i am new to DNN installed V 3.2.2 and since my service provider does not include installing DNN in their application packages, i have installed it manually after going through the video tutorials of "Installing DNN v 3.2 to a hosting provider".

After I uploaded all the files to my ftp i got the following 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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

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

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 configuration tag to point to a custom error page URL.

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

How to solve this problem......please help me out

Thanks in advance........

Regards

Hey cicerone. Unfortunately, the above error is very general, caused by the fact that you are calling the dnn site remotely (as opposed to locally, from your own pc or server).

I haven't seen the tutorial you mention, and Lee is on vaca. Have you installed the DNN instance you mention above locally and got it running? Or are you trying to install from scratch remotely? I wouldn't recommend the latter at all, since you've no idea whether the install was correct or not until you've done it locally, and then moved it to your ISP servers.

Here's a bit more info:



To provide your end users with custom, user-friendly error messages, you can set the mode attribute of this section to On. If you set it to RemoteOnly, custom errors will be shown only to remote clients, while local host users will see the ugly but useful ASP.NET errors -- clearly, this is helpful when debugging. Setting the mode attribute to Off will show ASP.NET errors to all users.

If you supply a relative (for instance, /error404.html) or absolute address (http://yourdomain.com/error404.html) in the defaultRedirect attribute, the application will be automatically redirected to this address in case of an error. Note that the relative address is relative to the location of the Web.config file, not the page in which the error takes place. In addition you can use tags to provide a statusCode and a redirect attribute:






At the very least, what you can do is open your web.config file on your ISP server, and search for the following:



Change this to look like this:



Per the above description, this will at least give you a more specific error message.