What's new
Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

PENDING SCCM 2309 update stuck in install loop

  • Thread starter Thread starter gman2024
  • Start date Start date
  • Replies Replies 8
  • Views Views 2K
G

gman2024

Member
Messages
5
Reaction score
0
Points
1
Hi Everyone,

Am having errors in the CMUpdate.log as follows:

Code: 
This running on active site server XXX.wan.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:23 PM    4700 (0x125C)
Inbox source is local on XXX.wan    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:23 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
ExecuteSqlCMUpdateInitScripts: Can't get SQL connection    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
ERROR: Can not get InstallationType from SetupInfo    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
Failed to initialize.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
CMUpdateSvc failed to initialize, sleeping for 5 minutes.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)

Wondering if anyone has come across this error and has resolved it.

Thanks.
 
Sort by date Sort by votes
gman2024 said:
Hi Everyone,

Am having errors in the CMUpdate.log as follows:

Code: 
This running on active site server XXX.wan.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:23 PM    4700 (0x125C)
Inbox source is local on XXX.wan    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:23 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
ExecuteSqlCMUpdateInitScripts: Can't get SQL connection    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_XXX" requested by the login. The login failed.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
ERROR: Can not get InstallationType from SetupInfo    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
Failed to initialize.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)
CMUpdateSvc failed to initialize, sleeping for 5 minutes.    CONFIGURATION_MANAGER_UPDATE    15/04/2024 1:53:27 PM    4700 (0x125C)

Wondering if anyone has come across this error and has resolved it.

Thanks.
Click to expand...
the log snipit clearly shows that it can't logon to the database.
 
Upvote 0 Downvote
Thanks for the reply Garth. I am trying to find out why? As part of the prerequisites check, I had to install the latest ODBC driver which I did - V18.3.2.1, the rest of the check was uneventful. I noticed in Control Panel, two other ODBC versions are present, V17 and V13 from the original SQL server installation by my predecessor prior to upgrading to SQL server 2022, not sure if this would have an impact?
 
Upvote 0 Downvote
gman2024 said:
Thanks for the reply Garth. I am trying to find out why? As part of the prerequisites check, I had to install the latest ODBC driver which I did - V18.3.2.1, the rest of the check was uneventful. I noticed in Control Panel, two other ODBC versions are present, V17 and V13 from the original SQL server installation by my predecessor prior to upgrading to SQL server 2022, not sure if this would have an impact?
Click to expand...
ODBC has nothing to do with being able to logon. Clearly the site server account is not SA within SQL.. https://www.recastsoftware.com/resources/how-to-create-a-sql-server-computer-account-login/
 
Upvote 0 Downvote
Thanks again Garth. I noticed you had replied with the same solution to another post with a similar issue recently. The SQL server is on the same virtual machine as the SCCM site server. The Computer account for the VM is SA within SQL.

As a test, I followed your other article - https://askgarth.com/blog/updated-how-to-create-a-sql-server-computer-account-login/ to ensure correct permissions, and was able to confirm correct access as shown below.

NTSystem Login.png
 
Upvote 0 Downvote
gman2024 said:
Thanks again Garth. I noticed you had replied with the same solution to another post with a similar issue recently. The SQL server is on the same virtual machine as the SCCM site server. The Computer account for the VM is SA within SQL.

As a test, I followed your other article - https://askgarth.com/blog/updated-how-to-create-a-sql-server-computer-account-login/ to ensure correct permissions, and was able to confirm correct access as shown below.

View attachment 6107
Click to expand...
Do you have two SSRS site on your server?
 
Upvote 0 Downvote
No, only 1 which was setup last year after the original SSRS site had expired. The original site's databases were not deleted from SQL.
 
Upvote 0 Downvote
As
gman2024 said:
No, only 1 which was setup last year after the original SSRS site had expired. The original site's databases were not deleted from SQL.
Click to expand...
As Long XXX.wan is the Site server in question, then I have no idea as it could be a million things. you will need to dig deeper.
 
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • What's new in Microsoft Intune: December 2025
  • PENDING How to Activate Windows 11 with Intune, Local Active Directory, and SCCM
  • PENDING Clients not reporting in to WSUS Server
  • PENDING SCCM Capture media error 0x80070091
  • PENDING Fresh SCCM Server 2022 Install – Reuse Same Site Code Without Reinstalling All Clients?

    • Forum statistics

    Threads
    7,138
    Messages
    27,878
    Members
    18,166
    Latest member
    fritz

    Latest posts

    Trending content
    Back
    Top