Failed to create the configuration database
I will tell you what my problem is as quickly al possible (sorry for my poor English!):A few weeks ago I ordered dedicated windows 2003 server (brand new) with win2003 sp1.First I upgraded to sp2 and installed .net framework 3.0After a few days I installed SQL Express 2005And then about a week ago i installed SharePoint Services 3.0The install went well but then you have to rund configuration wizard and there i got this message for the first time:"Failed to create the configuration databaseAn Exception of type Microsoft.SharePoint.SPException was thrown. Additional Exception: unable to connect to database. Check database connection information and make sure the database server is running."My first install was BASIC so it installed SQL Embeded as well.After that i tried to uninstall SQL, SPS3.0 - uninstalling and reinstalling in all possible ways (with SQL, Without SQL on server, BASIC, ADVANCED, FARM, ...) I went through all of this and many more Forums, blogs, KB, ... tried installing and upgrading and updating and hotfixing ...Every time i have the same error at step 2!Funny thing is that wizard creates SharePoint_Config and SharePoint_Admin databases in SQL but somewhere in the middle of the proces something happens - and i dont know what!!! I guess that some connection must be lost or something but why ... that is beyond me!Any of you know how to solve it? I am thinkig of ordering format&clean install to the hosting compay.
November 24th, 2007 1:33am

My advice wold be to do a completely new re-install but this time don't install SQL Server 2005 Express. That has a 4GB limit for the databases. The version of it installed by the WSS 3.0 Basic install (=Windows Internal Database / WID) does not have this limit. Not only will you have a more appropriate database system, but you also will have a much simpler (and working WSS installation) as you will be able to select the Basic installation which in my experience always works. (I presume this is a single-server installation) Mike Walsh
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2007 10:14am

Is there any other solution to this problem? Since my server is "dedicated hosting" i have to ask that company that hosts my server to do that for me and that can take a lot of time before they do reinstall of the system.
November 25th, 2007 8:19pm

I would try to uninstall SQL Express 2005 and uninstall Window Internal Database using following steps: For 32 bit: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe in general: Start Registry Editor, and then locate the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches Microsoft SQL 2005 embedded Edition. When you see a display name that matches the name, copy the value of the Key named UninstallString Open a Command-Window (Start->run->cmd) Paste the Copied string. Append CALLERID=OCSETUP.EXE the the end of the pasted text Reboot. Then try to reinstall WSS 3.0 using Typical installation method again.
Free Windows Admin Tool Kit Click here and download it now
November 29th, 2007 2:56am

I have had this before (on several occassions) Ensure that the account you are logged in with is a localAdministrator on the MOSS box and has the SYSADMIN role on SQL On the odd occassion I have just ended up installing MOSS running as the SQL account, by granting it temporary admin rights on my MOSS server. Good luck.
November 29th, 2007 11:58am

Uninstall WSS is not cleaning all as it created things. SO whenever you reinstall try to change Database name. By default it will show Sharepoin_Config, try to change that name and continue.ThanksS.Venkata Appaji
Free Windows Admin Tool Kit Click here and download it now
January 15th, 2009 1:16am

Even if you are running SQL with TCP/IP configured, which will connect by default to the instance name, you need to specify the instance name in the setup wizard otherwise it will fail on the connection even though the database creations are successful.
September 2nd, 2011 10:05am

You cannot install wss 3.0 with Basic setting if SQL server already installed on the same box. You have 2 choices - 1. You may install WSS 3.0 with Farm setting if you want to keep SQL sever installed on the box. This will install your content databases on the SQL server. 2. You can uninstall the both SQL server and WSS 3.0 and then install only WSS 3.0 with Basic setting. This will install an embedded database for SharePoint server. Hope this help. -Ankit Nigam | MCITP SQL Server 2005
Free Windows Admin Tool Kit Click here and download it now
September 3rd, 2011 4:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics