locked
Cannot install SCCM 2012 on the SQL named instance, custom port RRS feed

  • Question

  • Hello,

    We are installing SCCM 2012 with a database on a SQL remote named instance.

    Al prereq's are ok. but after the installation starts we get an error.

    In the logfile we see :

    CSql Error: Cannot find type data, cannot get a connection.      Configuration Manager Setup  25-5-2012 15:10:04          540 (0x021C)

    Also we can see that the SCCM server has an established connection with the SQL server on the custom port we have chosen.

    Any ideas?

    Thank you in advance!

    Tuesday, May 29, 2012 8:50 AM

Answers

  • Hi Jason,

    Due to lack of time I have installed a new dedicated SQL (using default instance) server and everything was perfect !

    This means that it was SQL issue anyway. The SCCM server has nothing to do with this problem.

    Anyhow, thank you for trying to help.

    Friday, June 1, 2012 6:08 PM

All replies

  • What version of SQL (SP+CU) are you using? Have you added the account performing the installation and the account of the site server to the local admins and sysadmins of the SQL server? Also make sure that SQL server is not using dynamic ports (which is default when using a named instance); you have to configure static ports manually.

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

    Tuesday, May 29, 2012 9:06 AM
  • Hi Torsten,

    It is SQL 2008 R2 SP1 with latest CU.

    SCCM server is member of local admins, local admins are sysadmins within SQL.

    There is a static port 1544 configured  and we can see the server establishes a connection on that port.

    Where to look now?

    Tuesday, May 29, 2012 9:35 AM
  • Is the Windows firewall enabled on the ConfigMgr site server (not SQL Server)?

    If so, you must enable multicastbroadcastresponse through the firewall also on the site server (I can't find a good link for this right now but it has to do with the way the SQL Browser service works).


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Tuesday, May 29, 2012 1:43 PM
  • yep, "allow all" from and to those two servers...
    Tuesday, May 29, 2012 2:21 PM
  • We usually see this when the user runnign setup is not a sysadmin on the SQL isntance. I know you verified above that the computer account was a member of the sysadmin role, but is the user running setup a sysadmin?

    Jason

    Tuesday, May 29, 2012 4:26 PM
  • "Allow all" is not good enough. The Windows firewall also blocks unicast responses to multicast and broadcast requests which is what happens when a SQL client uses the SQL Server Browser to locate a non-default instance of SQL Server.

    Reference: http://blogs.msdn.com/b/sqlsecurity/archive/2008/07/01/sql-server-and-the-windows-server-2008-firewall.aspx


    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Tuesday, May 29, 2012 4:41 PM
  • Yes, account running setup has sysadmin rights within the named instance.
    Tuesday, May 29, 2012 6:35 PM
  • I  have examinded the firewall log for "dropped" but did not see anything originating from the SQL server.

    Is it possible that this is not logged ?

    Tuesday, May 29, 2012 6:52 PM
  • Don't know. Easy way to see if it truly is the firewall or not is to disable it temporarily.

    Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

    Tuesday, May 29, 2012 7:48 PM
  • Hi Jason,

    I have just disabled the firewall ans run setup again.

    I still get the same:

    CSql Error: Cannot find type data, cannot get a connection. Configuration Manager Setup 30-5-2012 8:53:17 4804 (0x12C4)
    INFO: Connected to ROOT\CIMV2 WMI namespace on SQL Server Configuration Manager Setup 30-5-2012 8:53:25 4804 (0x12C4)
    INFO: SQL Server version detected is 10.50, 10.50.2811.0. Configuration Manager Setup 30-5-2012 8:53:25 4804 (0x12C4)

    ...

    ...

    AND:

    ...

    INFO: 'TST-SQLSV001-xxx' is a valid FQDN. Configuration Manager Setup 30-5-2012 8:53:44 4944 (0x1350)
    INFO: This is a named instance SQL Server. Configuration Manager Setup 30-5-2012 8:53:44 4944 (0x1350)
    INFO: SQL Server instance name (pSetupInf->SqlInstName): sccm2012sql Configuration Manager Setup 30-5-2012 8:53:44 4944 (0x1350)
    INFO: SQL Server master database (pSetupInf->SqlMasterDB): sccm2012sql\master Configuration Manager Setup 30-5-2012 8:53:44 4944 (0x1350)
    INFO: Site SQL Server database name (pSetupInf->SqlDatabaseName): sccm2012sql\CM_TIU Configuration Manager Setup 30-5-2012 8:53:44 4944 x1350)
    INFO: Site SQL Server computer name (pSetupInf->SqlServer): TST-SQLSV001.xxx Configuration Manager Setup 30-5-2012 8:53:44 4944 (0x1350)

    Wednesday, May 30, 2012 7:04 AM
  • There can be misleading logging in the Setup log with regards to SQL conenctions. Depending on whether the instance is local or remote we will cycle through connection strings, so you may see errors connecting followed by valid connections. We made the decision to expose all of the logging as a troubleshooting tool, as opposed to waiting for the final connection to occur and logging the final success or failure. In fact, there is a log line that indicates you can generally ignore all previous SQL conenction errors.

    What is the last line in the log proximate to the install failure?

    Jason

    Wednesday, May 30, 2012 4:59 PM
  • Hi Jason,

    See the end of the setup log lines below. I think it is going wrong at the moment the database need to be created. It does not happen.

    INFO: Verifying Configuration Manager Active Directory Schema Extensions.  $$<Configuration Manager Setup><05-30-2012 12:22:20.587-120><thread=736 (0x2E0)>
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=tst-xxx,DC=xxx,DC=xx~  $$<Configuration Manager Setup><05-30-2012 12:22:20.603-120><thread=736 (0x2E0)>
    INFO: Verifying Configuration Manager Active Directory Domain Function Level.  $$<Configuration Manager Setup><05-30-2012 12:22:20.618-120><thread=736 (0x2E0)>
    INFO: Found Domain Function level: 4~  $$<Configuration Manager Setup><05-30-2012 12:22:20.618-120><thread=736 (0x2E0)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~  $$<Configuration Manager Setup><05-30-2012 12:22:20.681-120><thread=736 (0x2E0)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001~  $$<Configuration Manager Setup><05-30-2012 12:22:20.681-120><thread=736 (0x2E0)>
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)~  $$<Configuration Manager Setup><05-30-2012 12:22:20.696-120><thread=736 (0x2E0)>
    CWmiRegistry::GetDWORD: Failed to get DWORD value DoNotAllowExceptions  $$<Configuration Manager Setup><05-30-2012 12:22:20.977-120><thread=736 (0x2E0)>
    CWmiRegistry::GetDWORD: Failed to get DWORD value DoNotAllowExceptions  $$<Configuration Manager Setup><05-30-2012 12:22:21.008-120><thread=736 (0x2E0)>
    INFO: File \\TST-xxx.xxx.xxx.xxx\admin$\sms_get_ADPERMS_svc.exe does not exist. No zapping needed.  $$<Configuration Manager Setup><05-30-2012 12:22:21.274-120><thread=736 (0x2E0)>
    CSql Error: Cannot find type data, cannot get a connection.  $$<Configuration Manager Setup><05-30-2012 12:22:29.979-120><thread=736 (0x2E0)>
    INFO: File C:\Windows\sms_account_test_svc.exe does not exist. No zapping needed.  $$<Configuration Manager Setup><05-30-2012 12:22:30.010-120><thread=736 (0x2E0)>
    INFO: Connected to ROOT\CIMV2 WMI namespace on SQL Server  $$<Configuration Manager Setup><05-30-2012 12:22:37.357-120><thread=736 (0x2E0)>
    INFO: SQL Server version detected is 10.50, 10.50.2811.0.~  $$<Configuration Manager Setup><05-30-2012 12:22:37.513-120><thread=736 (0x2E0)>
    INFO: File \\TST-xxx.xxx.xxx.xxx\admin$\sccm_sysroletosql_connect_test.exe does not exist. No zapping needed.  $$<Configuration Manager Setup><05-30-2012 12:22:37.716-120><thread=736 (0x2E0)>
    CSql Error: Cannot find type data, cannot get a connection.  $$<Configuration Manager Setup><05-30-2012 12:22:37.810-120><thread=736 (0x2E0)>
    Certificate is not configured on the website for SSL.  $$<Configuration Manager Setup><05-30-2012 12:22:45.501-120><thread=736 (0x2E0)>
    INFO: File \\TST-xxx.xxx-xxx.xxx.xxx\admin$\sms_client_test_svc.exe does not exist. No zapping needed.  $$<Configuration Manager Setup><05-30-2012 12:22:45.516-120><thread=736 (0x2E0)>
    INFO: TST-SCCMxx.xxx.xxx.xxx is a 64 bit operating system.  $$<Configuration Manager Setup><05-30-2012 12:22:53.239-120><thread=736 (0x2E0)>

    ~~===================== << Starting Configuration Manager 2012 Setup >> =====================  $$<Configuration Manager Setup><05-30-2012 12:22:54.611-120><thread=4500 (0x1194)>
    INFO: ConfigMgr2012 Setup was started


    • Edited by Hana_hanna Thursday, May 31, 2012 7:15 AM
    Thursday, May 31, 2012 7:01 AM
  • Are there any crashes reported in the Application logs on the OS? Based on this log, setup is either not ending (i.e. is still running) or is stopping suddenly. We should generate a final error and then log a line saying the setup has stopped.

    You may want to engage CSS and let them have a look at the system.

    Friday, June 1, 2012 5:45 PM
  • Hi Jason,

    Due to lack of time I have installed a new dedicated SQL (using default instance) server and everything was perfect !

    This means that it was SQL issue anyway. The SCCM server has nothing to do with this problem.

    Anyhow, thank you for trying to help.

    Friday, June 1, 2012 6:08 PM