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 ...how hard can it be...how hard can it be...
Previous
 
Next
New Post
8/2/2007 1:18 PM
 

Hi,

I've been trying for days now installing the latest versions of DNN on a remote server. I've successfully installed the 3.5.4 version on a local server earlier and on my local machine... so how hard can it be i thought.

One of my problems is that i cannot see the errors causing my installation to fail. I have tried to set the "customErrors mode" to Off , On and RemoteOnly but it still does not work.

I've tried setting the "UseInstallWizard" to both true and false.... doesn't work.

I've tried configuring the connection strings in all possible ways that i can imagine after reading the various posts on how to.... still won't work.

I contacted the guys who host the site .... event sent them the installation wizard .... and they tell me that they followed it to the letter.

I've tried the Install version, Source version and StarterKit..... none of them work for me......

HOW HARD CAN IT BE???!!!

Any comments, guiding and help is greatly appreciated. Please please help.

All I get is the following.....
 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>

Server Error in '/' Application.

Runtime Error

 

 
New Post
8/2/2007 2:39 PM
 

It is very simple....the error is due to the remote servers IIS setting telling it to run under ASP.NET 1.1  DNN 4.x requires ASP.NET 2.0

If you change the ASP.NET version you will be set to go!

The reason I know that is because your change to the web.config didn't cause any change in function.


-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
 
New Post
8/2/2007 2:47 PM
 

If you change the customErrors mode="Off" making sure to use proper case on the word "Off" and nothing changed then you are most not editing the correct web.config file.

Mitchel,
I'm pretty sure the error he would get if not using the correct fromework would be "requiredPermission" attribute not recognized.


DotNetNuke Modules from Snapsis.com
 
New Post
8/2/2007 2:53 PM
 

Nope...because by default customerrors is set to remoteonly

If you are installing locally you are correct, however, if on a hosting provider there is NO way possible to see the actual error.

It is a built in "security" feature of ASP.NET.  I have dealt with this on many hosting providers.


-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
 
New Post
8/3/2007 5:52 AM
 

Mitchel Sellers.... you were 100% right...

Now i can at least work on the errors i get :-)

Thanx for your promt replies guys.... really means a lot.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...how hard can it be...how hard can it be...


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