Trying to install DNN 4.5.1 on Win XP Pro, IIS5.1, MSSQL.

I was using my own user/password for the database, but that didn't work (see my infinite loop post). So, I reverted back to using built-in authentication with the ASPNET user.  This went better, but now have this error:

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

The log file name does not exist.  I can see in the database that lots of table have been succesfully created.  Does this ring a bell to anyone?

thanks in advance,

-daveb

No, but I am currently looking for the same answer. This log file does not exist. This is a clean install of 4.5.1.

"Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See D:\Domains\rightwingtavern.com\ROOT\Inetpub\wwwroot\www\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See D:Domains%0dightwingtav" to type 'Integer' is not valid."

Well, thanks Tamara. I checked the collation of the db, and it was CS (case sensitive). That explains the errors in the DotNetNuke.schema.log file (in the Providers\DataProviders\SqlDataProvider folder.  Then I created a new database, with CI (insensitive). Removed the 'installdate' item in the web.config, and tried again. Got the same error result.
But I knew my whole Sql Server collation had to change anayway. So uninstalled sql server, reinstalled sql 2000 sp2 and sp3a, this time with our standard Latin1_General_CI_AS. Made a new database for DNN (with this same collation). Now, everything was ok, no errors.
Normally I would say: reinstall of sql server fixed some errors. But the only thing I did before getting the Failure 400 Dnn install the first time was installing the sql 2005 tools.
My conclusion: The collation of the Dnn-db must be CI.  And the collation of the SqlServer must be CI too.

Can you maybe check if my conclusion is ok? What is your server collation, and the collation of the tempdb?

Thanks again,
Jaap.