Jump to content


Alexandros

SCCM 1702 / SQL 2016 (All Server 2016) failing setup in weird way

By Alexandros, in System Center Configuration Manager (Current Branch)

Recommended Posts

Alexandros Newbie

Alexandros

Posted
Posted

Hello Noobs! 

Just joined to one of the best forums -as all previous posts show- for Microsoft technologies. I am a long standing Winadmin with many years of work in my back (like most here!).

So, I have the following issue when trying a fresh install for SCCM 1702.

CMServer

I provide the connection string to the db as:

  • Host: SQLServer.domain.com
  • Instance Name: SCCM

SQLServer

Named Instance listening on port 1460.
Port 1433 is deaf, noone lives there.

As I am monitoring the configinstall.log, I see the following (no other errors until that point.

CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:22:59.572+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:22:59.603+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:02.635+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:02.635+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:05.674+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:05.674+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:08.716+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:08.716+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:11.752+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:11.752+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:14.788+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:14.788+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:17.820+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:17.820+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:20.849+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:20.849+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:23.889+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:23.889+00><thread=5704 (0x1648)>
CSql Error: Cannot find data for connection type: CCAR_DB_ACCESS, cannot get a connection.  $$<Configuration Manager Setup><01-30-2018 10:23:26.930+00><thread=5704 (0x1648)>
INFO: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:26.930+00><thread=5704 (0x1648)>
ERROR: SQL Connection failed. Connection: CCAR_DB_ACCESS, Type: Secure  $$<Configuration Manager Setup><01-30-2018 10:23:29.961+00><thread=5704 (0x1648)>
Failed to get DB connection for turning off client piloting for CD upgrade.  $$<Configuration Manager Setup><01-30-2018 10:23:29.961+00><thread=5704 (0x1648)>

And later on in the log I get:

INFO: Adding a login for SMS Provider: IF NOT EXISTS (select * from master.sys.server_principals where ******************') CREATE LOGIN [******************* FROM WINDOWS  $$<Configuration Manager Setup><01-30-2018 10:15:57.783+00><thread=5704 (0x1648)>
INFO: Grant this login for SMS Provider to have View Server State permission: GRANT VIEW SERVER STATE TO *****************]  $$<Configuration Manager Setup><01-30-2018 10:15:57.814+00><thread=5704 (0x1648)>
INFO: Creating user for SMS Provider: IF NOT EXISTS (select * from sys.database_principals where ****************') CREATE USER ****************]  $$<Configuration Manager Setup><01-30-2018 10:15:57.830+00><thread=5704 (0x1648)>
INFO: Adding SMS Provider machine account to smsdbrole_siteprovider: EXEC sp_addrolemember N'smsdbrole_siteprovider', N'A***********'  $$<Configuration Manager Setup><01-30-2018 10:15:57.845+00><thread=5704 (0x1648)>
INFO: Getting SMS Provider version...  $$<Configuration Manager Setup><01-30-2018 10:24:18.777+00><thread=5704 (0x1648)>
ERROR: Failed to get SMS Provider version.  $$<Configuration Manager Setup><01-30-2018 10:24:59.127+00><thread=5704 (0x1648)>
INFO: Build version is 8498, loaded SMS Provider Version is .  $$<Configuration Manager Setup><01-30-2018 10:24:59.127+00><thread=5704 (0x1648)>

The final death of the deployment is comes much later as:

INFO: 'sqlserver.domain.com' is a valid FQDN.    Configuration Manager Setup    30/01/2018 08:27:48    5260 (0x148C)
*** [08001][10060][Microsoft]

TCP Provider: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.    Configuration Manager Setup    30/01/2018 08:28:51    5260 (0x148C)

	*** [HYT00][0][Microsoft][SQL Server Native Client 11.0]Login timeout expired    Configuration Manager Setup    30/01/2018 08:28:51    5260 (0x148C)

	*** [08001][10060][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.    Configuration Manager Setup    30/01/2018 08:28:51    5260 (0x148C)

	*** Failed to connect to the SQL Server, connection type: SQLSERVER.DOMAIN.COM SCCM\MASTER.    Configuration Manager Setup    30/01/2018 08:28:51    5260 (0x148C)

	INFO: SQL Connection failed. Connection: SQLSERVER.DOMAIN.COM SCCM\MASTER, Type: Secure    Configuration Manager Setup    30/01/2018 08:28:51    5260 (0x148C)

After some more time where some more work happens on the installer side, I get the following irrelevant screen:

"Setup failed to configure SQL Service Broker. Each Configuration Manager site must have its own SQL Server instance. Verify that the selected SQL server instance is not in use by another Configuration Manager site."

The Service Broker port is there and properly configured by SCCM installer so this is an erroneous message.

 

And all that, after the database is being properly created and multiple times earlier in the process I am getting SQL successful connections!

The only point of interest I found is below and in the same log file.

 

INFO: 'sqlserver.domain.com' is a valid FQDN.    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Read SQL Data and Log file Path from script file if specified.    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Validating correct drive letter.    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Validating correct drive letter.    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: This is a named instance SQL Server.    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: SQL Server instance name (pSetupInf->SqlInstName): sccm    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: SQL Server master database (pSetupInf->SqlMasterDB): sccm\master    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Site SQL Server database name (pSetupInf->SqlDatabaseName): sccm\CM_AP1    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Site SQL Server computer name (pSetupInf->SqlServer): sqlserver.domain.com    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Site SQL Server Data File Path (pSetupInf->SqlDataFilePath): F:\SCCM-Data\MSSQL13.SCCM\MSSQL\DATA    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Site SQL Server Log File Path  (pSetupInf->SqlLogFilePath): H:\SCCM-LOG    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C)
INFO: Site SQL Server service port : 1433    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C) <------------------- THIS IS NOT CORRECT. SERVICE PORT IS 1460, NOTHING LISTENS ON 1433
INFO: Site SQL Server SSB port : 4022    Configuration Manager Setup    30/01/2018 07:54:15    5260 (0x148C) <---- THIS IS CORRECT AND PROPERLY EXISTS AND LISTENING

 

Any ideas?

 

 

-

Alex

 

 

image.png

Share this post

Link to post
Share on other sites
Alexandros Newbie

Alexandros

Posted
Posted

It seems I found the problem was with the actual ISO of 1702!

https://social.technet.microsoft.com/Forums/en-US/242348d5-610e-4a8a-a9b6-66cbcbcc3363/core-setup-sccm-1702-failed?referrer=http://social.technet.microsoft.com/Forums/en-US/242348d5-610e-4a8a-a9b6-66cbcbcc3363/core-setup-sccm-1702-failed?forum=ConfigMgrCBGeneral

My reply and results are shown there.

--

Alex

Share this post

Link to post
Share on other sites
Alexandros Newbie

Alexandros

Posted
Posted (edited)

Yes! That did it.

But now, I still have a failing:

ERROR: Failed to execute spConfigureServiceBroker
ERROR: Failed to ExecuteConfigureServiceBrokerSp

Apparently because I had pre-configured the service broker port on 4022.

*** [42000][9692][Microsoft]

[SQL Server]The Service Broker endpoint cannot listen on port 4022 because it is in use by another process.

--

Alex

 

Edited by Alexandros

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to topic listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.