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
6/12/2006 11:09 PM
 

There is hope.  The workaround has worked... 

I will write up the instructions, hope to have them done for Wednesday.  They are a little complicated and lengthy, I will try to simplify the process as much as possible.

 
New Post
6/13/2006 12:54 AM
 
i would like to say thank you for figureing out the workaround!

however, i pray that your instructions are a little more n00b friendly, because i really had no idea what to do with the previous version.  that possibly had to do with the fact that i didn't know what i needed to download from dotnetnuke (install, source, or starterkit), what i needed to ftp to my site, and where to put what i was to ftp up.  i'm guessing that the file you originally had posted up there for download included only the needed files.  oh well, i'm eager to see your solution because i really need to get my site up and running.

again, thank you very much!

(in fact, if you need a guinea pig to give feed back on the instructions, i would be more than happy to!  my profile should have the info you need to contact me, if you so desire)
 
New Post
6/13/2006 7:59 AM
 
For those newbies at GoDaddy (like me) it is possible to access the MSSQL files and the DNN files in the GODaddy installed version of DNN. There is a post here somewhere (will see if I can find it again) that uses WexLite that details how to do it. Until someone can figure out all the errors (I did it 6 times and a different error each time) this is the next best thing to a manual install. I have no idea what I am doing when I look at the files but hey its a start, and now I have to learn how best to backup my files using the GoDaddy SQLServer Administration Tool - yeech does it ever end. (Even using the Visual Web DNN template didn't give an error free install. This is one mean product. Keep talking guys it has to get easier.)
 
New Post
6/13/2006 11:12 AM
 

Hi Michael,

I am another DNN sufferer...love the application but hate the DNN installation, that too with goDaddy !

OK so I setup my GD account. I create SQL server database. Got the SQL server d/b info-Servername, d/b name, uid and pwd.

I change release.config to web.config and change ConnectionString to the following:

<connectionStrings>
    <!--  This is commented as I am using SQL server
   
    Connection String for SQL Server 2005 Express
    <add
      name="SiteSqlServer"
      connectionString="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"
      providerName="System.Data.SqlClient" />
   
    -->
    <!-- Connection String for SQL Server 2000/2005-->
    <add
      name="SiteSqlServer"
      connectionString="Server=whsql-v02.prod.mesa1.secureserver.net; Database=DB_68228;uid=myUID;pwd=myPass;"
      providerName="System.Data.SqlClient" />
  
  </connectionStrings>

 

and the appsettings are:

<appSettings>
    <!-- This is commented

Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules  
    <add key="SiteSqlServer" value="Data Source=.\SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Database.mdf;"/>

-->
    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules
    <!-- <add key="SiteSqlServer" value="Server=(local);Database=DotNetNuke;uid=;pwd=;"/>-->
    <add keyServer=whsql-v02.prod.mesa1.secureserver.net; Database=DB_68228;uid=myUID;pwd=myPass;"
      providerName="System.Data.SqlClient" >
   
    <add key="InstallTemplate" value="DotNetNuke.install.config" />
   ..........

..............

</appSettings>

I get the following error :

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

When I remove the web.config file I get the following error :

DotNetNuke Configuration Error

Could not find file 'd:\hosting\rajanhans\web.config'.Access to the path 'd:\hosting\rajanhans\web.config' is denied.Access to the path 'd:\hosting\rajanhans\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

Tried everything ! Cant get it to work...

 
New Post
6/13/2006 1:27 PM
 

First Things First,

The issue with Asp.Net 2.0 at Go Daddy has been resolved.  I just received word and tested to confirm.  So the current instructions on my site are once again applicable.

I will put the work around on the back burner for the time being and return to updating the installation instructions.

Now to Rajan's problem. 

Go Daddy does not allow for writing to the root of your system.  Check to make sure that the siteurls.config file has been copied from the Config folder to the root.  If not you can do this manually through FTP and then everything should work fine.

 
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