Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...New Installation gone badNew Installation gone bad
Previous
 
Next
New Post
5/27/2008 3:44 PM
 

Hi all

Here is the error I am getting when I try to open http://my.domain.com/DotNetNuke

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".

Has anyone encountered and available for solutions?

Thank you so much for any help out there?!

 
New Post
5/27/2008 11:28 PM
 

In web.config, change <customErrors mode="RemoteOnly" /> to <customErrors mode="Off" /> in order to see a detailed error.


Tom Kraak
SEO Analyst
R2integrated
 
New Post
5/28/2008 9:32 AM
 

I changed the web.config and it does not seem to do anything different.  I am on a remote installation of DotNetNuke.  I uploaded, uncompressed and edited the web.config file to point at the database that I manually created in mssql.  The web hosting I have is windows with asp.net framework 1.1 and mssql 2000.8

Is there something I am missing in the process?

 
New Post
5/28/2008 11:30 AM
 

DotNetNuke 4.x requires ASP.NET 2.0


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...New Installation gone badNew Installation gone bad


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out