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.

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.