Windows 2003 Enterprise English and IIS6 with enabled ASP2.0 for MOSS logic.2 Windows 2003 Enterprise English with MSSQL2005 SP1 in a MS-Cluster. The setup of MOSS is devided in too parts. The first part, the setup that terminates successfully. The 2nd part is the "SharePoint Products and Technologies Configuration Wizard" where you tell MOSS where to install the configuration databases. I point from my webserver where the MOSS setup was running to the cluster DB name and the "Configuration Wizzard" creates the DB's and the tables but then it stopps with the error message: An exeption of type "Microsoft.SharePoint.SPException" (unable to connect to DB) has occured. 02/28/2007 10:52:23 9 INF Creating connection string for config db SharePoint_Config server CHWQV00402/28/2007 10:52:23 9 INF Creating connection string for admin content db SharePoint_AdminContent_56cbdf91-e059-4fe5-9191-ba6855a4123d server CHWQV00402/28/2007 10:52:23 9 INF Using NTLM for sql connection string02/28/2007 10:52:23 9 INF Creating a new farm with config db SharePoint_Config content db SharePoint_AdminContent_56cbdf91-e059-4fe5-9191-ba6855a4123d server CHWQV004 for farm mode02/28/2007 10:53:49 9 ERR Task configdb has failed with an unknown exception 02/28/2007 10:53:49 9 ERR Exception: Microsoft.SharePoint.SPException: Unable to connect to database. Check database connection information and make sure the database server is running. ---> System.Runtime.InteropServices.COMException (0x81020024): Unable to connect to database. Check database connection information and make sure the database server is running. at Microsoft.SharePoint.Library.SPRequestInternalClass.CreateSite(Guid gApplicationId, String bstrUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrWebTemplate, String bstrOwnerLogin, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName) at Microsoft.SharePoint.Library.SPRequest.CreateSite(Guid gApplicationId, String bstrUrl, Int32 lZone, Guid gSiteId, Guid gDatabaseId, String bstrDatabaseServer, String bstrDatabaseName, String bstrDatabaseUsername, String bstrDatabasePassword, String bstrTitle, String bstrDescription, UInt32 nLCID, String bstrWebTemplate, String bstrOwnerLogin, String bstrOwnerName, String bstrOwnerEmail, String bstrSecondaryContactLogin, String bstrSecondaryContactName, String bstrSecondaryContactEmail, Boolean bADAccountMode, Boolean bHostHeaderIsSiteName)******** There are 11 lines with the error message in the 13844 lines long logfile that I am not posting here :-) If I run the "Configuration Wizard" and point to a none clustered MSSQL Server 2005, i works fine. I hope someone else have a MSSQL luster running and can give me some hints.

Solution ! Create the MOSS configuration-DB with PSCONFIGC:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>Psconfig -cmd configdb -create -server CHWQV004 -database SharePoint_Config -user BBVACH\portal-sharepoint -password123456 -admincontentdatabase SharePoint_AdminContent Change the DB Collation to Latin1_General_CI_AS_KS_WS in the Microsoft SQL Server Management Studio for the DBs:SharePoint_ConfigSharePoint_AdminContent

Hi Markus, I read your solution. One interesting point is that DB Collation "Latin1_General_CI_AS_KS_WS" for MOSS DB. I could not find any document regarding to this collation. Is it something new? In my MOSS farm, the SQL 2005 Box collation by default is "SQL_Latin1_General_CP1_CI_AS". Just do not understand why MOSS 2007 database collation is different.

For farm deployment on single server, if you use alias for SQL server instance do not specify «.» as server name. Use hostname instead.