DotNetNuke

Re: Local or not local (Domain name does not exist in the database)

hooligannes97 — Sun, 28 Mar 2004 03:22:05 GMT

Anyone got this working on a remote server???

Re: Local or not local (Domain name does not exist in the database)

JakeJeck — Fri, 02 Jan 2004 02:14:22 GMT

Thanks guys. I went into my db and fixed it in the Portals table.

Re: Local or not local (Domain name does not exist in the database)

Tom.Smith — Fri, 02 Jan 2004 01:30:22 GMT

The easiest fix would be to go into the portals table and change the name there, in the PortalAliases field.

Re: Local or not local (Domain name does not exist in the database)

christoc — Fri, 02 Jan 2004 01:20:17 GMT

You'll probably have to get into your database portals table and modify the alias column.

Do you have access to the database to do that?

Did you make it OPP

or
localhost/OPP ?

Re: Local or not local (Domain name does not exist in the database)

JakeJeck — Fri, 02 Jan 2004 01:00:09 GMT

I had this same problem as the first poster described.

However before reading any posts I went in as host and changed the portal alias from
localhost/DNN

to

OPP

Now I lost my entire portal!!! How do I get it back?

Re: Local or not local (Domain name does not exist in the database)

christoc — Fri, 12 Dec 2003 22:10:11 GMT

from the local machine, login as host and click on the SIte settings for that site, in the Portal Alias: field add the names that will be referencing that portal, try adding 213.171.224.12:81/DotNetNuke in there

Local or not local (Domain name does not exist in the database)

PatrickStirn — Fri, 12 Dec 2003 21:40:58 GMT

I installed DotNetNuke on a local server, with no problems, the portal is working fine used on local computer
when I call the database, I use local for the database connection string.

I try to access the portal from another computer and I have this message error:

--------------------------beginning message error------------------------------

DotNetNuke Configuration Error
Domain Name "213.171.224.12:81/DotNetNuke" 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. Application_BeginRequest ( globals.asax.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.
-----------------------------------------------------------end message error---------

what do I have to do to configure the portal so I can access it from others external computer?
Thanks