Hi All,

I'm new for dotnetnuke, but have some experience in ASP.NET and administration. I got some issues during installation of dotnetnuke portal on hosting platform. Maybe you can suggest me how to solve them. On local computer I pass installation without any problems.

Issue #1: Can not setup permissions for root folder.

1&1 hoster provides web and ftp access to folder where can be uploaded DNN files. I successfully did it. When I try to setup DNN I got problem with permissions. Root folder permissions, where placed all DNN files, can not be changed. All sub-folders permissions can be changed easily. After some playing with hosting settings, I place DNN files into subfolder dnn-v5.02.02, setup sub folder permissions, setup DB connection string... So now my folder structure looks like:

• \ [root]
  
• dnn-v5.02.02
  
  • DNN files....
    
• logs
  

My questions are:

1. Can be DNN setuped without changing root folder permissions? Maybe DNN can be configured  to apply all file system changes into subfolder instead of root folder?
2.  I try to change web domain home folder to dnn-v5.02.02, but all the time got error (error text below).
   1. When I try access by full path everything starts works: http://**.com/dnn-v5.02.02 - OK; Looks like domain home directory means something differ for 1&1 then I expecting.

The resource cannot be found.

1. And question related to this error - can someone give me a small example of minimal URLRewriter.config and web.config that will redirect all my domain requests to dnn subfolder (best solution will be to hide subfolder existance)? How i understand into root folder should be placed web.config, urlrewrite.config and bin folder with urlrewriter assembly.

 Issue #2: DNN hangs on Sql server database installation wizard step.

What to do? SQL Server web console shows that tables, views etc were created...

I am also on 1and1 hosting and am just getting started.  Do you happen to have a step by step tutorial for which buttons on admin.1and1.com that you could offer?  It took me forever to find the "application settings" under webfiles!  I've still got a few errors and am sure I missed something.  On my local computer, I know exactly where to push the buttons adn make the changes, but the interfaces with 1and1.com limit administrative abilities.

Thanks...

Folder redirection solution found! Tested today on IIS7 (Windows 7) and IIS5.1 (Windows XP).

Easy installation steps:

1. goto FTP root folder
2. create there empty files:
   1. default.aspx
   2. web.config
3. create folder App_Code
   1. create inside App_Code folder empty file: HostRootUrlRedirector.vb

Web.config content:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <!-- THIS PART FOR IIS6 ONLY -->
  <system.web>
    <httpModules>
      <add name="HostRootUrlRedirector" type="HostRootUrlRedirector"/>
    </httpModules>
  </system.web>
  <!-- THIS PART FOR IIS 7 ONLY -->
  <system.webServer>
    <modules>
      <add name="HostRootUrlRedirector" type="HostRootUrlRedirector"/>
    </modules>
  </system.webServer>
</configuration>
 

HostRootUrlRedirector.vb content:

Imports System
Imports System.Web

Public Class HostRootUrlRedirector
  Implements IHttpModule

  Public Sub Init(ByVal TheApp As HttpApplication) Implements IHttpModule.Init
    AddHandler TheApp.BeginRequest, AddressOf Me.Application_BeginRequest
  End Sub

  Public Sub Dispose() Implements IHttpModule.Dispose
  End Sub

  Private Sub Application_BeginRequest(ByVal Source As Object, ByVal e As EventArgs)
    Dim oApp As HttpApplication = CType(Source, HttpApplication)

    Dim strRequestUri As String
    strRequestUri = oApp.Request.Url.AbsoluteUri.ToLower()

    If Not strRequestUri.Contains("/dnn/") Then
      oApp.Response.Redirect("~/dnn/Default.aspx")
    End If
  End Sub
End Class

Now a little update web.config inside DNN folder:

        <httpModules><remove name="HostRootUrlRedirector"/> ... </httpModules>

And into one more section

    <system.webServer>
        <modules>
          <remove name="HostRootUrlRedirector"/> ...
        </modules>
    </system.webServer>

Description:

• solution use http module technic of ASP.NET
• web.config on root level attaching our own http handler that implements redirection
• due to inheretence nature of web.config's we have to update web.config inside DNN. We remove in it inhereted handler, which after first redirection not needed to us.
• Difference between IIS6 and IIS7 is in sections that attaching httpmodule. Only one section needed for each iis version. So simply choose according to own server configuration.

Solution works for me. Enjoy.