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
6/1/2006 5:28 PM
 

Well...

Here's what I've done so far:

  • Created a local DNN setup and configured it first... both in 4.0.2 and 4.0.3
  • Went ahead and copied these files up to the GoDaddy FTP server (used an external FTP program... not the one built into IE).
  • Created the virtual directory permissions.
  • Created the SQL database.
  • Edited the web.config file to point to the SQL database
  • Browsed to the Install folder and I got as far as what I previously posted above... where it runs through the install process, but then proceeds to fail on one section.

I also tried a straight "out of the box" DNN install... straight from the ZIP file and expanded it onto the FTP account. I followed the same steps as above to create the virtual directory permissions, configured the SQL database... and when I browsed to install, I get even less than before:

DotNetNuke Configuration Error

Could not find a part of the path 'd:\hosting\<username here>\Config\Backup_2006611421\web_.config'.Access to the path 'd:\hosting\<username here>\web.config' is denied.Access to the path 'd:\hosting\<username here>\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 

Still haven't been able to do a successful install. I have a GoDaddy Deluxe account. Before much longer, I'm going to need to simply resort to using the automated package solution and find a crafty way to mask the subdirectory... either that or just suck it up and deal with it being in a subdirectory.

- Andre

 
New Post
6/1/2006 8:06 PM
 
Andre,

I've had a very similar experience installing 4.0.2. Firstly, the error which mentions

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.

then when attempting to view the portal, the 'object reference not set to an instance of an object' error.

As Michael suggested, I had a look into the Portals and DesktopModules folders. Interestingly, the Portals\0 folder had not been created, and the DesktopModules folder was empty.

I tried copying across the contents of those folders from my local installation, then recreating the folder permissions (as per Michael's original instructions) but still received the 'object reference not set to an instance of an object' error.

However, there is a part of the stack trace:

DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +125

which gives us a clue.

I began to compare the GoDaddy SQL Server tables with my local versions, looking for anything related to PortalSettings and discovered that a number of tables are missing vital data which has not been written to the database during the installation, specifically:

Roles, Portals and UserRoles, as well as aspnet_Roles and aspnet_UsersInRoles. The Modules table also has rows missing, but this isn't vital because these could added manually later from within the site.

There are relatively few rows that need to be added to each table, so I've begun working on a sql script that would insert the missing data and could be run in the GoDaddy database manager.

I'm not even sure that this will work, and I have some concerns about the uniqueidentifier columns in the 'aspnet_xxxx' tables, but I'll try to test this out over the weekend.

I've got to say though, given the intricacy of the workarounds that we're trying to come up with, I can't help feeling that perhaps GoDaddy don't want us to do this on their shared hosting servers.

 
New Post
6/1/2006 8:08 PM
 

I installed 4.0.3

Are you doing a clean install? Thats the error I got the first time I tried to install, and I deleted everything off the site, and the sql database, and all virtual directories, and uploaded like I posted earlier and it worked.... who knows though.

Also I didnt have to move my web_.config to the root, some people were having to do that. So you might want to try that if you haven't already.

 
New Post
6/1/2006 10:49 PM
 

Hello folks,

I will have the instructions for the workaround to the latest issue up tomorrow.  So far as I can tell the only entry missing is the PortalAlias but we will see for sure.

 
New Post
6/2/2006 10:16 AM
 

Hi David,

That is interesting information you have uncovered. I initially thought I was looking for a piece of code causing the object reference error... it did not occur to me to check for the existence of all the SQL tables.

Too bad there isn't a simple import wizard of a database you can perform from the Web SQL admin tool. Probably by replicating a working local install and copying the SQL database as-is along with all the files, it would make installation much easier.

I agree, it appears GoDaddy is purposely not making this easy. What I'm wondering though is, what is the advantage for them to use the "automated install" approach of version 4.0.2? And also what I'm wondering is, if GoDaddy updates their DNN installation available (hopefully they would be putting 4.1 on the automated install package list soon), does it automatically update a version I've already installed with the older version... or would I be forever stuck using the version I have deployed?

With all these unknown questions in the air, it makes all the more sense to try and deploy a manual DNN installation for absolute full control.

I plan to make extensive use of DNN for my CMS solution both for myself and my customers, and I'd hate to be at the whim of whatever GoDaddy decides to do.

On the plus side though, I have been playing with the automated install solution of DNN, and it does work great... provided you access everything in your DNN solution through the DNN web interface.

I look forward to your next posting... as well as Michael's next post too for the latest manual install instructions.

- Andre

 
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