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/15/2006 6:52 AM
 

rajan,

Copy and paste this into your web.config.  Jetjam got me going with this the very first time. If you like, email me and I will send you my config, and you can just change your connection string info.

make it look like this.....

  </configSections>
  <connectionStrings
>
    <!-- Connection String for SQL Server 2000/2005 -->
    <
add
      name
="SiteSqlServer"
      connectionString
="Server=whsql-v02.prod.mesa1.secureserver.net;Database=DB_xxxxx;uid=xxxxx;pwd=xxxxx;"
      providerName
="System.Data.SqlClient" />
  </connectionStrings>
  <appSettings
>
   
<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules   -->
    <add key="SiteSqlServer" value
="Server=whsql-v02.prod.mesa1.secureserver.net;Database=DB_xxxxx;uid=xxxxx;pwd=xxxxx;"/>
    <add key="InstallTemplate" value
="DotNetNuke.install.config" />

and little down change "RemoteOnly"   to   "Off"

    <!-- permits errors to be displayed for remote clients -->
    <customErrors mode="RemoteOnly"/>
    <!-- Forms or Windows authentication -->


If God does not live in Colorado, I bet he visits there a lot!!
 
New Post
6/15/2006 10:28 AM
 

mg,

My best guess is your connection string in your web.config has an error. I kept getting that error also. Check out my previous post ... copy and paste it, and try again.

 


If God does not live in Colorado, I bet he visits there a lot!!
 
New Post
6/15/2006 10:51 AM
 

JPW,

did exactly what you said...still getting the error  as below. BTW, the URL changes from www.mywebsite.com to http://www.mywebsite.com/Install/Install.aspx?mode=Install

 

 

The page cannot be displayed

You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed.


Please try the following:

  • Contact the Web site administrator if you believe this directory should allow execute access.

HTTP Error 403.1 - Forbidden: Execute access is denied.
Internet Information Services (IIS)


Technical Information (for support personnel)

  • Go to Microsoft Product Support Services and perform a title search for the words HTTP and 403.
  • Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Configuring ISAPI Extensions, Configuring CGI Applications, Securing Your Site with Web Site Permissions, and About Custom Error Messages.
  • In the IIS Software Development Kit (SDK) or at the MSDN Online Library, search for topics titled Developing ISAPI Extensions, ISAPI and CGI, and Debugging ISAPI Extensions and Filters.
 
New Post
6/15/2006 12:10 PM
 

Here what exactly what I did to get my dotnetnuke to install. Start from scratch and delete EVERYTHING on your host site.

 

Follow these instructions step by step. It should install.

 

read carefully and take your time.

1.   No FrontPage extensions.

2.   go to your control panel on Godaddy, under Content click Directory Management, click Create Directory and make the following folders with permissions.

bin --- with Read and Write permissions.

Config --- with Read and Write permissions.

DesktopModules --- with Read, Write and Web permissions.

Install --- with Read, Write and Web permissions.

Portals --- with Read, Write and Web permissions.

3.   also in the control panel under Databases click SQL Server. click Create New Database, enter your choice of name and password. I did click DSN and the ASP.NET Schema Features.

4.   refresh page after a few mins and click view connection strings under Actions (where you made the database). copy or write down the ODBC string, it look like (Driver={SQL Server};Server=whsql-v02.prod.mesa1.secureserver.net;Database=XXXXXXXX;Uid=XXXXX;Pwd='your password'; ) take the highlighted part and paste or replace in the release.config file that is renamed to web.config. also change <customErrors mode="RemoteOnly"/> to Off.

5.   upload your files to Godaddy. all but the web.config file. The folders you made will show in your ftp, open each one and upload folder to folder. Example(files in bin folder on computer to open bin folder on server) also make sure all of the files are uploaded.

6. Config your web.config like this.

Highlight and delete:

</configSections>

  <connectionStrings>

    <!-- 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=(local);Database=DotNetNuke;uid=;pwd=;"

      providerName="System.Data.SqlClient" />

   -->

  </connectionStrings>

  <appSettings>

    <!-- 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 key="InstallTemplate" value="DotNetNuke.install.config" />

Highlight and insert:

</configSections>

  <connectionStrings>

    <!-- Connection String for SQL Server 2000/2005 -->

    <add

      name="SiteSqlServer"

      connectionString="Server=(your server info here);Database=DB_xxxx;uid=loginid;pwd=loginpassword;"

      providerName="System.Data.SqlClient" />

  </connectionStrings>

  <appSettings>

    <!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules   -->

    <add key="SiteSqlServer" value="Server=(your server info here);Database=DB_XXXX;uid=loginid;pwd=loginword;"/>

    <add key="InstallTemplate" value="DotNetNuke.install.config" />

Change:

<customErrors mode="RemoteOnly"/> to Off.

7.   now here is the trickery, (read slow) upload the web.config file in to the config folder. now from the config folder on the server drag both the SiteUrls.config and web.cofig over to your root with the main files(they should leave the folder). This seems to keep the permissions set to them when put in the config folder that you set permissions on. Now upload SiteUrls.config and web.cofig again in to config folder.

.

8.       now go to your site and it should install. When you go to your website to start the install practice your URL will change from www.mywebsite.com to http://www.mywebsite.com/Install/Install.aspx?mode=Install

BTW, whenever I copied the files from my computer to godaddy, I copied them one folder at a time. Not sure if that means anything.

This process worked great for me, hope it helps you.


If God does not live in Colorado, I bet he visits there a lot!!
 
New Post
6/15/2006 2:34 PM
 
rajan_hans wrote

JPW,

did exactly what you said...still getting the error  as below. BTW, the URL changes from www.mywebsite.com to http://www.mywebsite.com/Install/Install.aspx?mode=Install

 

 

The page cannot be displayed

You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed.


Please try the following:

  • Contact the Web site administrator if you believe this directory should allow execute access.

HTTP Error 403.1 - Forbidden: Execute access is denied.
Internet Information Services (IIS)


Technical Information (for support personnel)

  • Go to Microsoft Product Support Services and perform a title search for the words HTTP and 403.
  • Open IIS Help, which is accessible in IIS Manager (inetmgr), and search for topics titled Configuring ISAPI Extensions, Configuring CGI Applications, Securing Your Site with Web Site Permissions, and About Custom Error Messages.
  • In the IIS Software Development Kit (SDK) or at the MSDN Online Library, search for topics titled Developing ISAPI Extensions, ISAPI and CGI, and Debugging ISAPI Extensions and Filters.

Check if your folder permissions are set right.

 

 
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