locked
Installing SharePoint 2007 On Windows 2008 R2 With Virtual Machines RRS feed

  • Question

  • My objective: Build and test a SharePoint 2007 environment with virtual machines on Windows Server 2008 R2.

     

    Host (DCSERVER)– Windows Server 2008 R2 Enterprise

                Roles: Domain Controller, Active Directory, DNS

                Domain Name: LDS

     

    Virtual Machines (NAMES)

                VM1 (SQL-SERVER)– Windows Server 2008 R2 Std.

                            Roles: SQL Server 2008 R2

     

                VM2 (WEB-SERVER)– Windows Server 2008 R2 Web.

                            Roles: IIS7

     

                VM3 (APP-SERVER)– Windows Server 2008 R2 Std.

                            Roles: Application Server

                                        SharePoint 2007

     

    Share point installation – used a slipstream installation by deleting contents of update folder and extracting WSS 3.0 SP2 and MOSS 2007 SP2 into the updates folder.

     

    Using SharePoint Productivity and Technology Configuration Wizard.

                1. Chose Create new server farm.

                2. Database Settings dialog box

                            Database Server: SQL-SERVER

                            Database Name: (default)

                            User Name: LDS\Administrator

                            Password: (domain controller password)

     

    Get Message “Failed to connect to the database server or the database name does not exist…”

     

    Any suggestions what to do from here?

    Thursday, July 1, 2010 12:28 AM

Answers

  • We would need more details as that is a very generic error message. There are alot of reasons for this including

    1. Firewall

    2. SQL Server is running on a named instance - ensure browser service is running and that you are specifying the named instance with the SQL Server Name Ex: SQLServerName\NamedINstanceName

    3. SQL Server is not config'd to accept remote connections

    4. SQL Server is running on a port other than the default

    5. SQL Server is using an Alias

    6. Any number of network connectivity issues

    So,

    1. Can you ping the SQL Server?

    2. Try creating a UDL file and connecting to your SQL Server (this usually doesn't tell you much but iit will at least verify that the SQL Server exists and accept connections.

    3. Pending all of the above is there anything in the log files located here:
    %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS > There should be logs prefixed - PSCDiagnostics_<DateTime>.log

     


    Tony Parker, MSCE . MCTP. MCITP "Anything worth doing, is worth doing right"
    • Marked as answer by Lily Wu Monday, July 12, 2010 2:04 AM
    Thursday, July 1, 2010 1:54 AM

All replies

  • Hi,

     

    Firstly, please ensure that the account you run the SharePoint configuration wizard have appropriate permission to the DB server.

    For the SharePoint setup account, you should be able to login the server running SQL database. It should also be a member of SQL Server securityadmin and dbcreator fixed server role.

     

    Please verify the setup account info based on the following planning tool.

    http://go.microsoft.com/fwlink/?LinkID=92883&clcid=0x409

     

    Additionally, it might be caused by SQL Server or network problem, please try the trouleshooting tips regarding this error from neilth:

    http://blogs.msdn.com/b/neilth/archive/2008/04/25/failed-to-connect-or-database-name-does-not-exist.aspx 

     

     

    Hope it helps.

     

    Thanks & Regards.

     

     

    Lily Wu

    TechNet Subscriber Support in forum

    If you have any feedback on our support, please contact tngfb@microsoft.com


    Lily Wu
    Thursday, July 1, 2010 1:52 AM
  • We would need more details as that is a very generic error message. There are alot of reasons for this including

    1. Firewall

    2. SQL Server is running on a named instance - ensure browser service is running and that you are specifying the named instance with the SQL Server Name Ex: SQLServerName\NamedINstanceName

    3. SQL Server is not config'd to accept remote connections

    4. SQL Server is running on a port other than the default

    5. SQL Server is using an Alias

    6. Any number of network connectivity issues

    So,

    1. Can you ping the SQL Server?

    2. Try creating a UDL file and connecting to your SQL Server (this usually doesn't tell you much but iit will at least verify that the SQL Server exists and accept connections.

    3. Pending all of the above is there anything in the log files located here:
    %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS > There should be logs prefixed - PSCDiagnostics_<DateTime>.log

     


    Tony Parker, MSCE . MCTP. MCITP "Anything worth doing, is worth doing right"
    • Marked as answer by Lily Wu Monday, July 12, 2010 2:04 AM
    Thursday, July 1, 2010 1:54 AM