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 ...GoDaddy InstallationGoDaddy Installation
Previous
 
Next
New Post
10/8/2009 11:23 PM
 

Ok, here is the deal. I have a GoDaddy windows hosting account and I have been trying to install DNN. I was successful when I used the GoDaddy quick installation, but it installs DNN v4.9. I plan on making some mods to the source code and developing some custom modules so I want to work with the latest and greatest DNN v5.01.04. I have the site running on my local machine connected to the SQL Server database that I setup through GoDaddy. So this makes me confident that my web.config is gold. When I FTP all my website files up to a sub directory in the godaddy account and set the directory permissions to allow web read and write then I go to the web browser and throw in the web address for my new DNN site all I get is an error message,

In researching CMS systems I have played with DotNetNuke, mojoPortal and Umbraco. I have had all of these apps running on my local machine. For some reason everytime I FTP them up to the GoDaddy I only get a server error message. Any help would be greatly appreciated. Here is the generic error I get that tells you absolutely nothing. I have changed the customerrors value to false in the web.config, but I still get the same error.

 

Server Error in '/ross/test' 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>

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>

 
New Post
10/9/2009 8:54 AM
 

To get the actual error, in your web.config, set customErrors to "Off". This will allow you to see exactly what error is going on. I have setup on GoDaddy as well. I did the quick install then the upgrade to 5.1.4.

Once that is done, post the error and someone can help troubleshoot.

 
New Post
10/12/2009 11:11 PM
 

This appears to be the exact same error I had yesterday. What I learned was that you will need to go in to your hosting control center and go to File Manager, then check the domain you are working with and set the "Permissions" to "Write".  If you are encountering the same problem that I had, this should fix it.

        Hope that works, Jeff,,,

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...GoDaddy InstallationGoDaddy Installation


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