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
5/2/2008 11:04 PM
 

I also encountered this same set of errors while setting up a fresh install with my remote host.

Bombed on ERROR 400, try to reinstall via install wizard URL, it appeared to upgrade from 4.4 to current version.... then I tried to hit the site and received the DOES NOT EXIST IN THE DATABASE ERROR.  Tried to rerun installer again via URL and it stated it was on the current version.

This workaround seemed to work for me...

Possible workaround (USE WITH CAUTION - my install was fresh) and I'm new with DNN platform

1)  Locate the Version SQL table and select all records to file.

2)  Delete all records from Version table

3)  Run upgrade URL:  http://www.mydomain.com/DotNetNuke_2/Website/Install/Install.aspx?mode=upgrade

No guarantees here... but it got me going again.

NOTE:  in the event this workaround is successful  for anyone experiencing this issue - BE SURE TO UPDATE/CHANGE YOUR HOST AND ADMIN PASSWORDS MANUALLY, as you will be bypassing the initial configuration wizard with this workaround.  If you do not manually update these passwords, you'll be left with default credentials.

~Cheers

 
New Post
5/12/2008 11:59 AM
 

I'm pretty sure I figured this out from looking at the error logs.

Many of the scripts don't match the case sentativity of the schema, most of them are conflicting on "ID" vs "Id"

So you either need to set you DB to be case-insensative, or modify the schema, scripts to match.

 
New Post
5/12/2008 1:59 PM
 

I've completely gone past all install errors, figured I'd share the solution:

1. Make sure you DB has collation set to "SQL_Latin_General_Cp1_CI_AS

That will solve the case sensitive issue with the tables/columns

2. Go through the sql files in the dataprovider folder to do a search and replace on all parameters that have mismatched case. The files that had mismatched case in params I found were

Schema

04.04.01

04.05.00

04.06.00

04.07.00

I found all of the errors by running the "Auto" installtion the other installs didn't seem to be providing the necessary logs. Once the auto installation ran, I wrote down which files failed, looked up their logs in the data providers and read the erros, it will tell you very plainly which parameters need to be fixed. Once you fix them in the sql files delete you db and redo the install.

 

 
New Post
5/21/2008 5:09 AM
 

Hello all,
Having problems like everyone else, I let you know my case:
In my local computer at home (Windows XP) I´ve installed VS2005 professional, then SQL 2005 Express. Everything works fine.
Then I executed the DotNetNuke_04.08.02_StarterKit.vsi
I created a new web site on VS2005 and choose DotNetWeb Application.
In the App_Datat I created a DBname.mdf
Ctrl+F5 opens http://localhost:1146/websitename/Install/InstallWizard.aspx to set web site configuration in a few steps:
1) DotNetNuke Installation Wizard - Version 04.08.02
 Typical selected
 English selected
2) Checking File Permissions
 Test permission: Your site passed the permissions check.
3) Configure Database Connection
 - Selected DataBase=SQL Server 2005 (Express) File
 - Server=.\SQLExpress
 - Filename=DBname.mdf
 - Integrated security=checked
 - Run as db Owner=checked
 - Object Qualifier: (Empty)
 When test databaseconection=Connection Success

 Now I click on next

4) Run Database Installation Scripts
 This page has a javascript Error and stop loading.

What´s wrong? Any solution?

 
New Post
6/10/2008 3:11 AM
 

Hello,

I have the same kind of problem (no error 400), but when performing an upgrade from DNN 4.8.2 to DNN 4.8.3, I run the install http://www.mysite.com/install/install.aspx?mode=install (mode=upgrade give the same error) / I also tried Nina advice without success.
And then I have immediately the Dotnetnukeconfiguration error:

DotNetNuke Configuration Error

Domain Name "mydomain.com/Install" 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 ( Common.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://xxx.xx.xxx.xx/default.aspx = Domain Name: xxx.xx.xxx.xx
      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://xxx.xx.xxx.xx/DotNetNuke/default.aspx
      PortalAlias: localhost/DotNetNuke,MACHINENAME/DotNetNuke,xxx.xx.xxx.xx/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.

 

 

Any advice ???

  1.  

 
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