question

SumnerAnn avatar image
0 Votes"
SumnerAnn asked HanyunZhu-MSFT commented

New MECM 2103 Standalone primary server installation [28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed.

We are trying to install a new MECM standalone primary server with a remote SQL Server.

SQL is SQL Server 2016
SQL Native Client is version 11.4.7462.6
SQL Auth is mixed mode

We are using the MECM 2103 Baseline but we are seeing the following issue when trying to install:

INFO: Setup downloader setupdl.exe: FINISHED $$<Configuration Manager Setup><06-22-2021 12:41:04.124-120><thread=11784 (0x2E08)>
INFO: Checking SQLNCli version on ServerName $$<Configuration Manager Setup><06-22-2021 12:43:23.629-120><thread=14168 (0x3758)>
INFO: Failed to open registry key SOFTWARE\Microsoft\SQLNCLI11 on
. Error = 2 $$<Configuration Manager Setup><06-22-2021 12:43:23.644-120><thread=14168 (0x3758)>
SQL native client is not installed. $$<Configuration Manager Setup><06-22-2021 12:43:23.676-120><thread=14168 (0x3758)>
INFO: Registered type MASTER for master $$<Configuration Manager Setup><06-22-2021 12:43:23.691-120><thread=14168 (0x3758)>
INFO: Registered type SMS Master for master $$<Configuration Manager Setup><06-22-2021 12:43:23.707-120><thread=14168 (0x3758)>
INFO: Registered type
CM_ for CM_ $$<Configuration Manager Setup><06-22-2021 12:43:23.722-120><thread=14168 (0x3758)>
INFO: Registered type SMS ACCESS for
CM_ $$<Configuration Manager Setup><06-22-2021 12:43:23.754-120><thread=14168 (0x3758)>
[28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. $$<Configuration Manager Setup><06-22-2021 12:43:23.801-120><thread=14168 (0x3758)>
[28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. $$<Configuration Manager Setup><06-22-2021 12:43:23.816-120><thread=14168 (0x3758)>
Failed to connect to the SQL Server, connection type: MASTER. $$<Configuration Manager Setup><06-22-2021 12:43:23.847-120><thread=14168 (0x3758)>
[28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. $$<Configuration Manager Setup><06-22-2021 12:43:23.879-120><thread=14168 (0x3758)>
[28000][18452][Microsoft][ODBC SQL Server Driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. $$<Configuration Manager Setup><06-22-2021 12:43:23.894-120><thread=14168 (0x3758)>
Failed to connect to the SQL Server, connection type: *** MASTER. $$<Configuration Manager Setup><06-22-2021 12:43:23.910-120><thread=14168 (0x3758)>


I have redacted the servername & sitecode with ***

Has anyone come across this before?

mem-cm-general
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HanyunZhu-MSFT avatar image
0 Votes"
HanyunZhu-MSFT answered

Hi @SumnerAnn,

Thanks for posting in Microsoft Q&A forum.

We could try the following steps to troubleshoot:
1) Confirm that the Firewall allows SQL Server Access.
We could add an inbound rule to enable TCP port 1433, which is the default port for SQL Server
For more details, please refer this article: Configure Windows Firewall - SQL Server | Microsoft Docs
2) Enable SQL Server and Windows Authentication mode:
Path: SQL Server Management Studio > Server Properties > Security > SQL Server and Windows Authentication mode
108506-security.png
3) Confirm that the SQL Server is allowed to remote connections
Path: SQL Server Management Studio > Server Properties > Connections > Allow remote connections to this server
108527-connections.png
4) Enable SQL Service to listen on TCP/IP
(Please restart the SQL Server Service if any changes are made)
108564-service.png

Hope the information above can be helpful to you.


If the response is helpful, please click "Accept Answer"and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


security.png (20.6 KiB)
connections.png (37.6 KiB)
service.png (21.0 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SumnerAnn avatar image
0 Votes"
SumnerAnn answered HanyunZhu-MSFT commented

Hi, we have now got a little further, it seems with MECM 2103 baseline we have had to install the SQL Native client on the primary server before we tried the MECM Install wizard. In previous baseline versions of MECM when using a remote database we have not had to do as and your documentation states (https://docs.microsoft.com/en-us/mem/configmgr/core/servers/deploy/install/list-of-prerequisite-checks#sql-server-native-client):

"SQL Server Native Client
When you install a new site, Configuration Manager automatically installs SQL Server Native Client as a redistributable component. After the site is installed, Configuration Manager doesn't upgrade SQL Server Native Client. Updating the SQL Server Native Client may require a restart, which can impact the site install process."

Yet I cant find any information anyway to state that using the MECM Baseline 2103 no longer installs the SQL Native Client and this must be installed beforehand?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
In the checking list for installing update 2103, Review SQL Server Native Client version is needed.
Please refer to this article:
https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/checklist-for-installing-update-2103#review-sql-server-native-client-version

0 Votes 0 ·