Install Error:

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See c:\hosting\branded\client\dnn450a\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See c:hostingbranded" to type 'Integer' is not valid.

Steps to Reproduce:

1. Created subdomain portal.clientdomain.com  >>>  c:\hosting\branded\client\dnn450a
2. Set subdomain .NET application to 2.0
3. Unzipped and copied install package to server
3. Edit and renamed release.config to web.config
       a.  Utilizing an existing SQL dB with DNN 3.x already installed.
       b.  Edited Connection Strins to point to existing DB  and set object qualifier to DNN450A
4. Opened site with IE7  >>> Redirected to Install wizard
5. selected Typical and English
6. SQL COnnection picked up from web.config
7. Received error listed above:  No 04.04.00.log file exists
8. Clicked Back with browser twice and forward once which continued the install wizard script resulting in:

Upgrading DotNetNuke
Current Assembly Version: 04.05.00
Current Database Version: 04.04.00
Upgrade Status Report
00:00:00.020 - Upgrading to Version: 4.5.0
00:00:00.040 -   Executing Script: 04.04.01.SqlDataProvider Success
00:00:00.180 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:02.173 - Performing General Upgrades
Upgrade Complete
Click Here To Access Your Portal

At which point received a new error:
DotNetNuke Error: - Version 04.05.00
Domain Name portal.clientdomain.com Does Not Exist In The Database

This installation test was to see if a single SQL DB can be utilized to serve multiple DNN host installs (3.x and 4.5) with just a change of object qualifier.  

On Saturday, I did a new install with  version 4.5 on my laptop with Windows XP and SQL Server 2005 (no service packs) and everything worked fine.  Today I tried to install it on Windows Server 2003  (SP2 I think) and I tried the database server with both SQL Server 2005 (SP2) and SQL Server 2000 (SP4) and got the error message you posted above.  For me however, I was not able to progress past the failure and had the frustrating task of having to kill a good number of processes that it left running on the server, before I could delete the damaged database.  I can't help but think that the problem is with the environment, since I was able to install it successfully on my laptop, which runs a different OS, a different IIS, and an older version of Sql Server 2005.  Except for these environment differences, everything else was the same.

I'm stuck at the same error as originally posted, I can't get past that Run Database Installation Scripts page.  Stuck in an infinite look and the error mentions looking for the 04.04.00.log which doesn't exist.  Has anyone found a workaround for this?  I'm installing on a Windows Server 2003 box connecting to a full SQL Server 2005 DB. (Not SQL Express)