locked
Connection to SQL Server on central administration site failed RRS feed

  • Question

  • I'm installing a SCCM 2012 primary site and during the Prerequisite Check I'm getting an error saying "Setup failed to establish a connection to the SQL Server for the central administration site, or the user running Setup does not have syadmin rights on the SQL Server."  Another error says "The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database collation."

    Installation of the CAS went fine.  SQL is installed locally on the CAS and the primary site server.  The account I'm using is a domain admin account and has sysadmin rights.  It's the same account I used to install SQL.  Firewalls are turned off.  Any ideas?

    Thursday, May 24, 2012 10:15 PM

Answers

All replies

  • Just being curious: is there really a need for a CAS? Why have you decided to install one? How many clients will be managed in total?
    Please have a look at the logfiles that can be found in C:\. You will get detailed information about the error.

    Torsten Meringer | http://www.mssccmfaq.de

    Friday, May 25, 2012 7:28 AM
  • Organization will be managing 150,000 clients.

    I looked at the log files but it hasn't helped me figure out what the problem is.  Below is a snippet of ConfigMgrPrereq.log and ConfigMgrSetupWizard.log:

    ConfigMgrPrereq.log :

    <05-24-2012 16:21:20> LAB02FE01.LAB02.LOCAL;    Administrative rights on site system;    Passed
    <05-24-2012 16:21:20> INFO: Verifying if user is administrator on CAS
    <05-24-2012 16:21:20> INFO: Checking administrative permissions on <lab02sql01.LAB02.LOCAL>.
    <05-24-2012 16:21:20> LAB02FE01.LAB02.LOCAL;    Administrative rights on central administration site;    Passed
    <05-24-2012 16:21:20> INFO: Testing connection to CAS
    <05-24-2012 16:23:23> ERROR: Failed to get SQL Server connection to CAS LAB02SQL01.LAB02.LOCAL (CM_JLA)
    <05-24-2012 16:23:23> LAB02FE01.LAB02.LOCAL;    Connection to SQL Server on central administration site;    Error;    Setup failed to establish a connection to the SQL Server for the central administration site, or the user running Setup does not have syadmin rights on the SQL Server.
    <05-24-2012 16:23:23> <<<RuleCategory: System Requirements>>>
    <05-24-2012 16:23:23> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
    <05-24-2012 16:23:23> INFO: Check Lanman service: <LAB02FE01.LAB02.LOCAL>.
    <05-24-2012 16:23:29> INFO:lanman test loop count:11.
    <05-24-2012 16:23:29> INFO: lanman Return result <1>
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Check Server Service is running;    Passed
    <05-24-2012 16:23:31> INFO: Target computer is a Windows server.
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Unsupported site server operating system version for Setup;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Domain membership;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Schema extensions;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Active Directory Domain Functional Level Check;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    FAT Drive on Site Server;    Passed
    <05-24-2012 16:23:31> INFO: Free disk space on target C:\. = 17150 MB
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Free disk space on site server;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Pending system restart;    Passed
    <05-24-2012 16:23:31> <<<RuleCategory: Dependent Components>>>
    <05-24-2012 16:23:31> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Microsoft XML Core Services 6.0 (MSXML60);    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    WSUS SDK on site server;    Warning;    Configuration Manager software update points require at least Windows Server Update Services (WSUS) version 3.0 SP2.  If using a remote software update point, the WSUS administration console must be installed on the site server.  For more information on WSUS installation see http://go.microsoft.com/fwlink/?LinkID=79477.
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Windows Server 2003-based schannel hotfix;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Windows Remote Management (WinRM) v1.1;    Passed
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Microsoft Remote Differential Compression (RDC) library registered;    Passed
    <05-24-2012 16:23:31> INFO: Checking Windows Installer version on LAB02FE01.LAB02.LOCAL.
    <05-24-2012 16:23:31> INFO: Path of Windows Installer is <C:\Windows\system32\msi.dll>.
    <05-24-2012 16:23:31> INFO: Msi.dll version is: <5.0.7601.17514> .
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Microsoft Windows Installer;    Passed
    <05-24-2012 16:23:31> INFO: Checking Firewall settings for SQL Server LAB02FE01.LAB02.LOCAL, dwSQLPort = 1433, dwSSBPort = 4022.
    <05-24-2012 16:23:31> INFO:  Windows firewall service is stopped.
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Firewall exception for SQL Server;    Passed
    <05-24-2012 16:23:31> INFO: SQL Server computer <LAB02FE01.LAB02.LOCAL>
    <05-24-2012 16:23:31> INFO: SQL Server named instance <>
    <05-24-2012 16:23:31> INFO: The running account for MSSQLSERVER/SQLEXPRESS service is LAB02\sqlsvc
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    SQL Server service running account;    Passed
    <05-24-2012 16:23:31> INFO: SQL Server computer <LAB02FE01.LAB02.LOCAL>
    <05-24-2012 16:23:31> INFO: SQL Server named instance <>
    <05-24-2012 16:23:31> LAB02FE01.LAB02.LOCAL;    Dedicated SQL Server instance;    Passed
    <05-24-2012 16:23:31> INFO: CheckSQLCollationPrimary
    <05-24-2012 16:25:34> ERROR: Failed to get SQL Server connection to CAS LAB02SQL01.LAB02.LOCAL (CM_JLA)
    <05-24-2012 16:25:36> INFO: Collation on <LAB02FE01.LAB02.LOCAL> <SQL_Latin1_General_CP1_CI_AS>
    <05-24-2012 16:25:36> LAB02FE01.LAB02.LOCAL;    Parent/child database collation;    Error;    The collation of the site database does not match the collation of the parent site's database.  All sites in a hierarchy must use the same database collation.
    <05-24-2012 16:25:36> INFO: Checking .NET framework versions 3.5...
    <05-24-2012 16:25:36> INFO: .NET is installed
    <05-24-2012 16:25:36> LAB02FE01.LAB02.LOCAL;    Minimum .NET Framework version for Configuration Manager site server;    Passed
    <05-24-2012 16:25:36> LAB02FE01.LAB02.LOCAL;    PowerShell 2.0 on site server;    Passed
    <05-24-2012 16:25:36> INFO:CheckSupportedFQDNFormat <LAB02FE01.LAB02.LOCAL>
    <05-24-2012 16:25:36> INFO: NetBIOS <LAB02FE01>
    <05-24-2012 16:25:36> INFO: FQDN <LAB02FE01.LAB02.LOCAL>
    <05-24-2012 16:25:36> LAB02FE01.LAB02.LOCAL;    Primary FQDN;    Passed
    <05-24-2012 16:25:42> INFO:get ADPERMS test loop count:11.
    <05-24-2012 16:25:42> INFO: SMS_GET_ADPERMS_SERVICE Return result <7>
    <05-24-2012 16:25:42> INFO: site server has access permission to AD
    <05-24-2012 16:25:44> LAB02FE01.LAB02.LOCAL;    Verify site server permissions to publish to Active Directory.;    Passed
    <05-24-2012 16:25:44> INFO: Testing connection to CAS
    <05-24-2012 16:27:47> ERROR: Failed to get SQL Server connection to CAS LAB02SQL01.LAB02.LOCAL (CM_JLA)
    <05-24-2012 16:27:47> LAB02FE01.LAB02.LOCAL;    Site code in use;    Passed
    <05-24-2012 16:27:47> INFO: Check required collation of Sql Server.
    <05-24-2012 16:27:47> INFO: LangID <409>
    <05-24-2012 16:27:49> INFO: Collation:<SQL_Latin1_General_CP1_CI_AS>
    <05-24-2012 16:27:49> LAB02FE01.LAB02.LOCAL;    Required SQL Server Collation;    Passed

    ConfigMgrSetupWizard.log:

       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.GetSqlConnection(String databaseName, String serverName, Boolean encrypt)].
    5/24/2012 2:34:38 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 2:35:38 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)], Exception details: [System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SystemCenter.ConfigMgr.Setup.DatabaseUtility.GetSqlConnection(String databaseName, String serverName, Boolean encrypt)].
    5/24/2012 2:37:22 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 2:37:24 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 2:37:24 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 2:37:24 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 2:37:33 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 2:37:33 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 2:50:49 PM: ConfigMgrSetupWizard Verbose: 1 : Report progress callback. Progress stage: 50, Progress state: 0.
    5/24/2012 2:50:49 PM: ConfigMgrSetupWizard Verbose: 1 : Received setup progress [Evaluating setup environment] from native code.
    5/24/2012 2:50:59 PM: ConfigMgrSetupWizard Verbose: 1 : Report progress callback. Progress stage: 50, Progress state: 1.
    5/24/2012 2:50:59 PM: ConfigMgrSetupWizard Verbose: 1 : Received setup progress [Evaluating setup environment] from native code.
    5/24/2012 2:50:59 PM: ConfigMgrSetupWizard Verbose: 1 : Report progress callback. Progress stage: 52, Progress state: 0.
    5/24/2012 2:50:59 PM: ConfigMgrSetupWizard Information: 1 : Removed Product Key from SetupScriptFile
    5/24/2012 2:50:59 PM: ConfigMgrSetupWizard Verbose: 1 : Received setup progress [Generating public key and SQL Server certificate] from native code.
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Verbose: 1 : Report failure callback. Failure: 18.
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Information: 1 : Cancelling asynchronous threads...
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Information: 1 : Notified monitoring threads to exit.
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Information: 1 : All monitoring threads have completed.
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Information: 1 : Released callback GC handle
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Verbose: 1 : Received error [Setup could not read CAS SQL information or register connection to it's database.] from native code.
    5/24/2012 3:02:32 PM: ConfigMgrSetupWizard Verbose: 1 : Completed the site installation thread.
    5/24/2012 3:12:17 PM: ConfigMgrSetupWizard Information: 1 : Cancelling asynchronous threads...
    5/24/2012 3:12:17 PM: ConfigMgrSetupWizard Information: 1 : Notified monitoring threads to exit.
    5/24/2012 3:12:17 PM: ConfigMgrSetupWizard Information: 1 : All monitoring threads have completed.
    5/24/2012 3:12:17 PM: ConfigMgrSetupWizard Verbose: 1 : Exiting SetupWPF.exe.
    5/24/2012 3:12:40 PM: ConfigMgrSetupWizard Verbose: 1 : Cannot not connect to SMS provider on local machine. Either it is not installed or access is denied.
    5/24/2012 3:12:42 PM: ConfigMgrSetupWizard Information: 1 : Cannot detect SMS Type because either SiteServer, SqlServer or SiteServerName is empty.
    5/24/2012 3:14:21 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:14:22 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 3:14:22 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:14:22 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 3:14:25 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:14:25 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 3:18:03 PM: ConfigMgrSetupWizard Verbose: 1 : Exiting SetupWPF.exe.
    5/24/2012 3:18:46 PM: ConfigMgrSetupWizard Verbose: 1 : Cannot not connect to SMS provider on local machine. Either it is not installed or access is denied.
    5/24/2012 3:18:47 PM: ConfigMgrSetupWizard Information: 1 : Cannot detect SMS Type because either SiteServer, SqlServer or SiteServerName is empty.
    5/24/2012 3:19:57 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:19:57 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 3:19:57 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:19:57 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.
    5/24/2012 3:20:01 PM: ConfigMgrSetupWizard Information: 1 : Creating SQL connection to database master on server LAB02FE01.LAB02.LOCAL.
    5/24/2012 3:20:01 PM: ConfigMgrSetupWizard Information: 1 : Sql connection is established.

    Thanks,

    Friday, May 25, 2012 2:13 PM
  • Please take a look if you are using the same collation on SQL. It's required to use the same collation.

    http://jthys.wordpress.com/2012/04/02/sccm-2012-required-sql-server-collation/


    Dennis de Roo

    Sunday, May 27, 2012 6:41 AM
  • What I have noticed when installing SQL server 2008 is that you will need to provision accounts to allow access to the SQL server.  the accounts may have domain admin access, and you would have set up the associated permissions aka "sccm security roles" inside config manager....  but inside SSMS you will need to map the computer account or user/AD group to the sysadmin role inside of SQL.  the only time i have seen this so far-- is when i was trying to do an automated push to create  a secondary site from the CAS...  looking into the SQL logs actually provided the insight into the resolution in saying that an account was trying to access and did not have the correct permissions...  in this case the computer account for the primary site did not have the permissions to install the database on the secondary site's sql DB.  bear in mind i did not install SQL express on the sec site as this was explicitly defined in the scope of work...
    Thursday, July 19, 2012 6:15 PM