Your company uses Public folders and Web Distributed Authoring and Versioning. The company asks
you to install Microsoft Windows SharePoint Services (WSS) as a server in a new server farm. You
plan to install WSS on a server that runs Windows Server 2008 R2. You start the Configuration
Wizard to begin the installation. You receive an error message as shown in the exhibit.
You need to configure WSS to start SharePoint Services 3.0 SP 2 Central Administration. What should
you do?
A.
Install the Windows Internal Database.
B.
Install a Microsoft SQL Server 2005 server.
C.
Install the Active Directory Rights Management Services role.
D.
Install the Active Directory Lightweight Directory Services role.
Explanation:
To resolve this problem, you need to install Microsoft SQL Server 2005 server on the farm. This error
message occurs when either the SQL Server does not exist or the SQL Server services id stopped. The
server farm account is used to access your configuration database. It also acts as the application pool
identity for the SharePoint Central Administration application pool, and it is the account under which
the Windows SharePoint Services Timer service runs. The SharePoint Products and Technologies
Configuration Wizard adds this account to the SQL Server Logins, the SQL Server Database Creator
server role, and the SQL Server Security Administrators server role. If SQL Server is not available then
the above mentioned error message will appear. Reference: Configuration Wizard – Failed to
Connect
http://blogs.msdn.com/neilth/archive/2008/04/25/failed-to-connect-or-database-name-doesnot-exist.aspx