While installing the db scripts:

Installing Database - Version 4.4.0...Upgrading Database to Version ERROR: See C:\Inetpub\wwwroot\com.artemis-staging.sandbox\Providers\DataProviders\SqlDataProvider\04.04.00.log for more information...FAILURE 400 - Conversion from string "ERROR: See C:Inetpubwwwrootcom" to type 'Integer' is not valid.

I'm having a similar problem. I get loads of errors when creating the database an example from the 04.04.01.log:

System.Data.SqlClient.SqlException: Must declare the scalar variable "@PortalID".
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at DotNetNuke.Data.SqlDataProvider.ExecuteADOScript(String SQL)
   at DotNetNuke.Data.SqlDataProvider.ExecuteScript(String Script, Boolean UseTransactions)

CREATE procedure dbo.[dnn_GetModuleByDefinition]
      @PortalId int,
      @FriendlyName nvarchar(128)
AS
 SELECT dnn_vw_Modules.*  
 FROM dnn_vw_Modules
  INNER JOIN dnn_ModuleDefinitions as MD ON dnn_vw_Modules.ModuleDefID = MD.ModuleDefID
 WHERE ((PortalId = @PortalId) or (PortalId is null and @PortalID is null))
    AND MD.FriendlyName = @FriendlyName
    AND IsDeleted = 0

I am installing DotNetNuke on a database server (MS SQL 2003 64bit)  that has been set to be case sensitive, and this looks like what is causing the problem. If I update the SQL above and run it in a SQL query window it creates the above procedure.

It must be a collation problem. I have tried to install dotnetnuke to a winsrv2003 sql server 2005 with server collation Latin1 general bin.

Although I set that the database collation shall be in-case sensative the installation fails. The installation probably fails because the server collation is case sensitive and the database scripts tries to write to tempdb...

How can this be solved? I cannot change the collation on the server due to other databases.. Changing the scripts by hand don't seem lika  a good option either...