Products

Solutions

Resources

Partners

Community

About

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
5/29/2006 10:14 AM
 

Hi

I have followed all your steps from your website (northern star solutions) and I have ran into several errors

After trying several times, I fixed the error that was saying it couldn't connect to the database (probly a connection string error)

However, now i get the same error as Robirt:

DotNetNuke Configuration Error

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

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 checked and I don't have the folder in Config :  \Backup_2006529659\web_.config'

As for the other two.. SiteUrls and Web.config, they are both in the root (i moved SiteUrls into the root as someone on the forums suggested)

Like I said, I have followed all your steps, I created all the virtual folders with the correct permissions and I am on a Deluxe GoDaddy Hosting.

Thank you for helping.

 


 
New Post
5/29/2006 4:19 PM
 

This error is just a pain.  What has happened is that the site did not complete installation properly.  Then once you corrected the initial error it attempted the installation again.  Unfortunately your web.config showed it as already being installed so it tried to perform an update instead. 

As long as the config file has the proper permission assigned (in the virtual folder area) it shouldn't be a problem.  But sometimes something else causes it to not co-operate, this could be a number of things since the site did not install correctly.

Best solution if possible is to wipe clean (database and file structure) then re-create the database, re-upload everything and re-assign the folder permissions.  It is a bit of work but much easier than diagnosing the multiple of issues that will undoubtedly present themselves.  Just make sure to insert the new connection string information into the web.config file (this should be a new one too).

 
New Post
5/30/2006 11:04 AM
 
I have just finished debuging the error "unable to access path...".  I will post the instructions for the work around shortly.
 
New Post
5/30/2006 6:51 PM
 

The Mistery Solved:

razzy911 wrote

DotNetNuke Configuration Error

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

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

Once I clued into what was happeining I was able to work around this error.   Yes, work around.  The issue is actually with Go Daddy.  For some reason the Asp.Net runtime is being blocked from updating the web.config file.  When you install the DNN Framework on your host it makes two modifications to the webconfig file.  The first is the alteration of the MachineKey, this is the encryption and decryption key used by some processes and methods.  Next it adds the <Installed Date> element.  Since these changes are being blocked the DNN framework reports that it cannot access the web.config or siteurls.config files. 

The work around I used is this.  In did a proper install on my local machine, this created a random machine key within the config file and added the install date element.  I then edited the web.config file and added the proper connection string information for the database on the live site.  Then I uploaded the new web.config file and ran the installation.

There is another important step that needs to be followed these days that was not required before.  Every time you upload your site or folders the virtual folder association is broken.  You absolutely must remove and re-create the virtual folders with the proper permissions.  If you don't you will run into other problems and the portal will not install.

 
New Post
5/31/2006 2:29 PM
 

Michael, wouldn't the following scenario work:

  • Install web site locally on your own machine so that the web.config makes the appropriate changes where someone has full control.
  • Set up the SQL database on GoDaddy.com and modify the web.config to match the SiteSqlServer settings.
  • Copy the resulting configured files over to GoDaddy.com.
  • Apply the virtual folder permissions.
  • Browse to the page to install the site.

I ask because I tried doing it this way, but did not get anywhere. I get as far as the site installing itself, then a Permission error:

Installing DotNetNuke

Version: 04.00.03



 

Installation Status Report

00:00:00.031 - Installing Version: 3.1.0
00:00:00.031 - Installing Script: DotNetNuke.SetUp.SqlDataProvider
00:00:00.046 - Installing Script: DotNetNuke.Schema.SqlDataProvider
00:00:02.156 - Installing Script: DotNetNuke.Data.SqlDataProvider
00:00:05.078 - Installing MemberRole Provider:
00:00:05.078 - Executing InstallCommon.sql
00:00:05.578 - Executing InstallMembership.sql
00:00:06.031 - Executing InstallProfile.sql
00:00:06.203 - Executing InstallRoles.sql
00:00:06.609 - Upgrading to Version: 3.1.1
00:00:08.140 - Upgrading to Version: 3.2.0
00:00:08.250 - Upgrading to Version: 4.0.0
00:00:08.531 - Upgrading to Version: 4.0.1
00:00:08.609 - Upgrading to Version: 4.0.2
00:00:08.625 - Upgrading to Version: 4.0.3
00:00:08.640 - Performing General Upgrades
00:00:08.906 - Loading Host Settings:
00:00:09.031 - Configuring SuperUser:
00:00:09.156 - Installing Desktop Modules:
00:00:09.171 - Installing Modules:
00:00:09.187 - Executing Additional Scripts:
00:00:09.203 -   Creating Portal: My Website
00:00:09.375 -   Error: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
00:00:09.375 -   Portal failed to install:
00:00:09.375 - Installing Optional Resources:

Installation Complete

When I refresh, I just get a runtime error.

So far I haven't been successful in the manual installation, and unfortunately I'm going to need to use the "automated" solution for my customers at the moment, as the holdups can't go on for much longer. I'm going to try doing a forward with masking to make it appear everything is originating from the top level.

I'm still on the lookout to get this to work. I appreciate everyone's hard work in documenting the potential solutions.

 
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