Consider the following scenario: When running setup for System Center 2012 Configuration Manager (ConfigMgr 2012), in the Setup window you receive the following warnings:
<A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL Server instance hosting the site database. Setup cannot continue.>
You will also see the following error messages in ConfigMgrPrereq.log:
INFO: Computer Account is <DOMAIN\SiteServerCOMPUTERNAME$>
ERROR: Connected to SQL Server but failed to execute query IF NOT EXISTS (select * from master.sys.server_principals where name=' DOMAIN\SiteServerCOMPUTERNAME$') BEGIN CREATE LOGIN [DOMAIN\SiteServerCOMPUTERNAME$] FROM WINDOWS; SELECT 1; END ELSE SELECT 0
save to ini file SQLCONNECT:SQLFQDN\INSTANCE.
ERROR: Failed to connect to SQL Server Site Server FQDN.
SiteServer FQDN; Site System to SQL Server Communication; Warning; A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL Server instance hosting the site database. Setup cannot continue.
In the ConfigMgrSetup.log you will get these error messages:
CWmiRegistry::GetValues: Failed to connect to registry on machine SQL FQDN. Error code: 2
INFO: File \\SiteServerFQDN\admin$\sms_get_ADPERMS_svc.exe does not exist. No zapping needed.
CSql Error: Cannot find type data, cannot get a connection.
INFO: File C:\Windows\sms_account_test_svc.exe does not exist. No zapping needed.
INFO: Connected to ROOT\CIMV2 WMI namespace on SQL Server
INFO: SQL Server version detected is 10.50, 10.50.2811.0.
INFO: File \\SiteServerFQDN\admin$\sccm_sysroletosql_connect_test.exe does not exist. No zapping needed.
CSql Error: Cannot find type data, cannot get a connection.
*** IF NOT EXISTS (select * from master.sys.server_principals where name= ‘DOMAIN\SiteServerCOMPUTERNAME$') BEGIN CREATE LOGIN [DOMAIN\SiteServerCOMPUTERNAME$] FROM WINDOWS; SELECT 1; END ELSE SELECT 0
*** [42000][15401][Microsoft][ODBC SQL Server Driver][SQL Server]Windows NT user or group ‘DOMAIN\SiteServerCOMPUTERNAME$' not found. Check the name again.
In this case, although you may have created a domain group where you have added the Site Server System Account and gave this group sysadmin rights on the SQL instance dedicated for ConfigMgr 2012, you might still receive these error messages.
In this case, you will most probably have to add the Site System account (computer name) with admin rights in SQL:
If you try to add the computer name you will see that with advanced search you are not able to select Computers (only users or groups):
To add a computer as an admin in SQL, you will have to type in the Login Name: DOMAIN\COMPUTERNAME$ and press OK. If the computer name is not found in AD you will receive an error similar to the one below:
With a remote SQL server, you will need to make sure that the site system account has admin rights for the SQL instance, dedicated for ConfMgr.
Adding computers to SQL Logins individually can be done using the syntax DOMAIN\COMPUTERNAME$, or by using groups.
Other means of troubleshooting:
1. Check if 1433 port is configured for TCP Port for every IP section (including IP All) and TCP Dynamic Ports fields are empty as bellow:
1433 is the default port that is used and should not be changed to another or a dynamic port.
2. Create a UDL file to test connectivity between machines (See http://msdn.microsoft.com/en-us/library/e38h511e(v=VS.71).aspx for more information):
Radu Tomoiaga
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/