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 StartedNew to DNN Plat...New to DNN Plat...DotNetNuke errorDotNetNuke error
Previous
 
Next
New Post
2/15/2012 10:22 PM
 

I successfully installed DotnetNuke with SQL Server 2008 Express.  When I clicked a Go To Site link I received this message:

Domain Name Does Not Exist In The Database

DotNetNuke supports multiple portals from a single database/codebase. It accomplishes this by converting the URL of the client browser Request to a valid PortalID in the Portals database table. The following steps describe the process:

  1. Web Server Processing
    • When a web server receives a Request from a client browser, it compares the file name extension on the target URL resource to its Application Extension Mappings defined in IIS.
    • Based on the corresponding match, IIS then sends the Request to the defined Executable Path ( aspnet_asapi.dll in the case of ASP.NET Requests ).
    • The aspnet_isapi.dll engine processes the Request in an ordered series of events beginning with Application_BeginRequest.
  2. HttpModule.URLRewrite OnBeginRequest ( UrlRewriteModule.vb )
    • The Request URL is parsed based on the "/" character
    • A Domain Name is constructed using each of the relevant parsed URL segments.

      Examples:

      URL: http://www.domain.com/default.aspx = Domain Name: www.domain.com
      URL: http://209.75.24.131/default.aspx = Domain Name: 209.75.24.131
      URL: http://localhost/DotNetNuke/default.aspx = Domain Name: localhost/DotNetNuke
      URL: http://www.domain.com/virtualdirectory/default.aspx = Domain Name: www.domain.com/virtualdirectory
      URL: http://www.domain.com/directory/default.aspx = Domain Name: www.domain.com/directory

    • Using the Domain Name, the application queries the database ( Portals table - PortalAlias field ) to locate a matching record.

      Note: If there are multiple URLs which correspond to the same portal then the PortalAlias field must contain each valid Domain Name in a comma seperated list.

      Example:

      URL: http://localhost/DotNetNuke/default.aspx
      URL: http://MACHINENAME/DotNetNuke/default.aspx
      URL: http://209.32.134.65/DotNetNuke/default.aspx
      PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,209.32.134.65/DotNetNuke

      Note: If you are installing the application to a remote server you must modify the PortalAlias field value for the default record in the Portals table according to the rules defined above.

 

 I don't know what to do now.  Thanks for any help and God Bless,

 

Mark A. Sam

 

 

 
New Post
2/15/2012 10:54 PM
 

Here is some new information  This returned when I added Full Control to wwwroot to DefaultAppPool

Error Summary

HTTP Error 401.3 - Unauthorized

You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server.

Detailed Error Information
Module IIS Web Core
Notification AuthenticateRequest
Handler StaticFile
Error Code 0x80070005
Requested URL http://localhost:80/DotNetNuke/
Physical Path C:\inetpub\wwwroot\DotNetNuke\
Logon Method Anonymous
Logon User Anonymous
Most likely causes:
  • The user authenticated by the Web server does not have permission to open the file on the file system.
  • If the resource is located on a Universal Naming Convention (UNC) share, the authenticated user may not have sufficient share and NTFS permissions, or the permissions on the share may not match the permissions on the physical path.
  • The file is encrypted.
Things you can try:
  • Open Windows Explorer and check the ACLs for the file that is being requested. Make sure that the user accessing the Web site is not being explicitly denied access, and that they do have permission to open the file.
  • Open Windows Explorer and check the ACLs for the share and the physical path. Ensure that both ACLs allow the user to access the resource.
  • Open Windows Explorer and check the encryption properties for the file that is being requested. (This setting is located in the Advanced attribute properties dialog.)
  • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
Links and More Information The user trying to access the page was successfully logged on, but the user does not have permission to access the resource. This means the access control list (ACL) for the resource either does not include the user or explicitly denies the user. Check the ACL for the resource and add the user to the ACL. If the content is located on a share, ensure both NTFS and share permissions allow the user access. It is also possible that the user is part of a group that is denied access.

View more information »

Microsoft Knowledge Base Articles:

  • 907273
  • 332142
 
New Post
3/3/2012 1:47 AM
 
Hi Sam,

Answer to you first question: When DNN shows "Domain Name Does Not Exist In The Database" Error that means the url you are using to access the website does not exists inside portalalias table. For example if the url is http://www.example.com the in portalsalias table there should be an entry of example.com for portal id 0 (main website).

For assigning permissions to your website as far as I know you need to give full control to NetworkServices and ASP. This is enough for a DNN website to work. Hope this helps.

Thanks,
Vikas Saxena
www.zventech.com
 
New Post
3/3/2012 6:03 AM
 
Hello Vikas,

Thanks for the input, but this is resolved by installing DNN on a hosted server. I had a problem with that also, but resolved it so now I am up and working without problems so far.

God Bless,

Mark
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedNew to DNN Plat...New to DNN Plat...DotNetNuke errorDotNetNuke error


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