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 ...installation probleminstallation problem
Previous
 
Next
New Post
3/25/2008 4:44 AM
 

Hi out there, I am a .Net Developer. Recently i tried installing DOTNETNUKE. I created the virtual directory, empty database and set security permissions for the content directory folder of DotNetNuke as mentioned in installation guide . I then tried to browse the site. But then i was directed to UnderConstruction.aspx page instead of InstallationWizard.aspx page. However i tried with complete url for installationwizard.aspx. I could start with installation this time.

I then set the data source name, database name and provided sql login credentials for the database i created. Then next the installation started in the next page, windows showed database scripts being executed out.But in a little while process stopped with a error as follows: Installing Database - Version 4.4.0...Upgrading Database to Version ERROR:

See D:\Inetpub\wwwroot\DotNetNuke\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See D:InetpubwwwrootDotNe" to type 'Integer' is not valid.

Actually i tried setting up dotnetnuke in my office system and i could complete installation successfully.But i am having this strange problem in my pc despite i followed the same step with same installer package. Is this problem spawned the moment i was directed to underconstruction.aspx in the initial step itself or there is different problem behind. Hope you guys would help out with solution.

Thanks and look forward to hear from you guys soon.

 
New Post
3/26/2008 9:15 AM
 

If you were able to install the package on one pc, you should be able to install it on another. Try starting over again on your pc and try to duplicate the steps you completed to get DNN installed on your office pc. Let us know the results.


John Eimer
 
New Post
3/27/2008 7:05 AM
 

Hello.. I have the same problem too. I've tried several times to do the instalation and I always get the above mentioned error. What seems to be the problem..? I have looked across the internet but i cannot find any clue for the appropriate diagnose.

Greetings

 
New Post
3/28/2008 8:01 AM
 

I am getting the same error / problem as well. I am installing remotely on a Win2003 server and SQL 2005 DB. I have 3 different DBs I am moving from another hosting company. I've tried installing 4.8.2 from scratch, I've tried restoring the backup DB and Files and then doing an upgrade. Nothing is working. Do I need to go with 4.7? I have to get all three sites up today and have been messing with this since Monday.

ASP.net v2.0.50727

 
New Post
3/28/2008 8:06 AM
 

In addition to my previous post, I am also getting an error like the one below on every site. Installation says it worked fine, except for the error 
[See D:\Inetpub\wwwroot\DotNetNuke\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See D:InetpubwwwrootDotNe" to type 'Integer' is not valid.]. 
However there are no records in any of the tables (Portal, etc) and I get an error like this:

DotNetNuke Error: - Version 04.08.02


 

Domain Name bennu.michaelcornelison.com 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 ( PortalAlias table - HTTPAlias field ) to locate a matching record.

      Note: If there are multiple URLs which correspond to the same portal then you can add multiple records to the PortalAlias table pointing to the same portal (PortalId).

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

 

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...installation probleminstallation problem


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