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 ...Manual Installation on GodaddyManual Installation on Godaddy
Previous
 
Next
New Post
2/3/2006 11:50 AM
 
After installing 4.02 to the Root of my GoDaddy site, I get the following permission errors. 

Could not find a part of the path 'd:\hosting\a538cubs\Config\Backup_200623944\web_.config'.Access to the path 'd:\hosting\a538cubs\web.config' is denied.Access to the path 'd:\hosting\a538cubs\SiteUrls.config' is denied.

1. Do I need a virtual folder for Config with WRITE rights?
2. Do I need to move SiteUrls.config from Config to the root?
3. web.conf is there.  Why would access be denied?

Since I'm currently stumped, I'm going to try the whole process with 3.2.2

<<Dan>>
 
New Post
2/3/2006 2:16 PM
 

smartd wrote
I'm assuming:
1. Your instructions installs the files to the web root directory, rather than a "portal" directory as described in the ASP.net instructions.
2. Installing DNN 4.x using Install package.
3. Mods to web.config include uncommenting the SQL server 2000/2005 section and commenting the SQL Express 2005 section (by moving the --> ) in BOTH the *AND* sections. 
4. Database connect string is needed in BOTH sections.

<>

The installation is to the web root directory, as stated. Not www.yourdomain.com/Portals.  The rest of your points do not apply to the instructions I have made.  Please keep this topic to setting up the hosting account.  There are plenty of good instructions and resources for configuring your site.  The instructions provided are for configuring the hosting account.  There should be nothing requiring a specific DotNetNuke Framework usage in the instructions, they are generic and can be used for 1.x, 2.x, 3.x or 4.x. 

 
New Post
2/3/2006 4:42 PM
 

A bit of further clarification for DotNetNuke hosted on GoDaddy.com....

If you are on a "Shared Hosting Plan", you cannot install DNN to the root. GoDaddy will not change the root permissions to allow DNN to work properly.

You will have to install it to a folder (ie. www.yourdomain.com/dnn ). Before doing so, you need to go to the hosting control panel and create that folder in "directory management" with the appropriate permissions.

I believe the instructions for installing to the root of a GoDaddy hosting account were performed originally on a "Virtual Server Hosting Plan" which gives you full permission control of your root folder.

It is still better, in my opinion, to install DNN yourself on GoDaddy versus using their "Value Application" install of DNN. If you use their install of DNN, you will not have FTP access to the folder; the folder they set up for you is not in your domain space. It is on another shared app server and they do not give FTP access to it.

I hope this helps clear up some confusion.

Regards,

Patrick

 
New Post
2/4/2006 7:29 PM
 
muldune6910 wrote

A bit of further clarification for DotNetNuke hosted on GoDaddy.com....

If you are on a "Shared Hosting Plan", you cannot install DNN to the root. GoDaddy will not change the root permissions to allow DNN to work properly.

You will have to install it to a folder (ie. www.yourdomain.com/dnn ). Before doing so, you need to go to the hosting control panel and create that folder in "directory management" with the appropriate permissions.

I believe the instructions for installing to the root of a GoDaddy hosting account were performed originally on a "Virtual Server Hosting Plan" which gives you full permission control of your root folder.

It is still better, in my opinion, to install DNN yourself on GoDaddy versus using their "Value Application" install of DNN. If you use their install of DNN, you will not have FTP access to the folder; the folder they set up for you is not in your domain space. It is on another shared app server and they do not give FTP access to it.

I hope this helps clear up some confusion.

Regards,

Patrick

This "clarification" is incorrect.  The instructions are for insalling DotNetNuke to the root directory.  No modification of the root directory permissions are needed.  You only need create the three folders refered too and assign the appropriate permissions.  Again, no modicifaction of root folder permissions is required.  There is no reference to modifying the root directory.

I have setup the site on a shared hosting plan, not on a virtual server.

 
New Post
2/4/2006 10:25 PM
 

Michael.

Maybe you got lucky. Maybe GoDaddy slipped and has the shared server you are on set up differently.

I spent a entire day doing what you did and I followed your instructions to the letter and got this error...

(From DNN source 403-3.htm...)

DotNetNuke has extensive file upload capabilities for content, modules, and skins. These features require custom security settings so that the application is able to create and remove files in your website.

Using Windows Explorer, browse to the root folder of the website ( C:\DotNetNuke by default ). Right-click the folder and select Sharing and Security from the popup menu ( please note that if you are using Windows XP you may need to
Enable Simple File Sharing before these options are displayed ). Select the Security tab. Add the appropriate User Account and set the Permissions.

If using Windows 2000 - IIS5
- the {Server}\ASPNET User Account must have Read, Write, and Change Control of the virtual root of your website

If using Windows 2003 - IIS6
- the NT AUTHORITY\NETWORK SERVICE User Account must have Read, Write, and Change Control of the virtual root of your website

I spoke with GoDaddy support and they flat out told me that they don't support it and they won't change the permissions to allow it due to security reasons.

They told me the only way I could get what I wanted was to upgrade to a Virtual Server hosting plan.

How many other people out there have had success like Michael?

Please speak up if you have! I WANT to have my DNN on the ROOT. If I would have known GoDaddy did not allow it, I would have hosted someplace else.

If others have it, then I will call GoDaddy and fight until I get it set right or get a refund.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Manual Installation on GodaddyManual Installation on Godaddy


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