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!

SOLVED SCCM Version 1710 Keep showing installing.

  • Thread starter Thread starter Rahul Sapke
  • Start date Start date
  • Replies Replies 16
  • Views Views 8K
Status
Not open for further replies.
R

Rahul Sapke

Member
Messages
23
Reaction score
2
Points
3
Hello Friends, I have SCCM 1706 installed in my environment and I wanted to start Windows 10 1809 Deployment using SCCM but I have found out that it could only happen with SCCM 1902 installation.
Hence I have decided to upgrade my SCCM version to 1710 and eventually I would upgrade it to 1802,1806,1810 & finally 1902.
However my version upgrade stuck on 1710 & it keep shows "Installing.." in console.

Under HMAN.log, it shows
Failed to read update.map C:\Program Files\Microsoft Configuration Manager\CMUStaging\CF9F7AC7-0B01-4781-BC80-246023CA6548\SMSSetup\update.map.

Under cmupdate.log it shows:-

CONFIGURATION_MANAGER_UPDATE service is starting... CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Microsoft System Center Configuration Manager v5.00 (Build 8692) CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Process ID: 1384 CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Worker thread ID: 1508 CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Inbox source is local on SCCM.Domain.COM CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Set inbox to \\SCCM.Domain.COM\SMS_IN1\inboxes\cmupdate.box CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
This running on active site server SCCM.Domain.COM. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
Inbox source is local on SCCM.Domain.COM CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:02 1508 (0x05E4)
*** [08001][2][Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_IN1" requested by the login. The login failed. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
*** [08001][2][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_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
ExecuteSqlCMUpdateInitScripts: Can't get SQL connection CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:23 1508 (0x05E4)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_IN1" requested by the login. The login failed. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
*** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'NT AUTHORITY\SYSTEM'. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
*** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "CM_IN1" requested by the login. The login failed. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
*** Failed to connect to the SQL Server, connection type: SMS ACCESS. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
ERROR: Can not get InstallationType from SetupInfo CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
Failed to initialize. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)
CMUpdateSvc failed to initialize, sleeping for 5 minutes. CONFIGURATION_MANAGER_UPDATE 2019-04-01 18:22:25 1508 (0x05E4)

We don't have MS Support available. Please advise.
 
Sort by date Sort by votes
The error is clear, you can't login to SQL. Make sure that you and the site server are SA on the SQL server.
 
Upvote 0 Downvote
I would fix the login issue. Before worrying about the install.
 
Upvote 0 Downvote
As per your instruction I have verified SQL Access to my SCCMADMIN account and it was in place, the only I thing I changed is, changed the service account for all SCCM Services from Local System to SCCMADMIN.

Then, I was able to remove "1710 Installing..." status from SCCM Console by removing GUID record for 1710 from DB. Then I restarted server.

After that I have started Installation of SCCM 1806 as I could see this version available to install, so I skipped 1710 and 1710 Hotfix.

However it is stuck with following lines in CmUpdate.Log & HMAN.Log:

Both files are attached. Please advise what exactly I should try.
 

Attachments

Upvote 0 Downvote
Rahul Sapke said:
As per your instruction I have verified SQL Access to my SCCMADMIN account and it was in place, the only I thing I changed is, changed the service account for all SCCM Services from Local System to SCCMADMIN.

Then, I was able to remove "1710 Installing..." status from SCCM Console by removing GUID record for 1710 from DB. Then I restarted server.

After that I have started Installation of SCCM 1806 as I could see this version available to install, so I skipped 1710 and 1710 Hotfix.

However it is stuck with following lines in CmUpdate.Log & HMAN.Log:

Both files are attached. Please advise what exactly I should try.
Click to expand...

What exactly do you mean that you change the service account to SCCM Admin? If you are talking about the smsexec service for example, this will not be supported. It must stay local system account.
 
Upvote 0 Downvote
I have changed this service account to Local System log on, following is the screenshot.

1840

1841

All SQL Server Configuration Manager Protocol are "Enabled"

1842

And this is how my console looks under Administration -> Update & Servicing,
1843
 
Upvote 0 Downvote
It not supported to change the CMCB service accounts, they need to be reset back to their defaults.

It is also important how you change the service accounts for SQL server too. You must be changed using SQL Server tool and not the Service MMC.
 
Upvote 0 Downvote
The SCCMADMIN account is already a member of SysAdmin under SQL
1845

Do you have any special instructions for me? As I have checked everything.
Probably you can share any link or something?
 
Upvote 0 Downvote
and what about the site server computer account? did you grant it sa?
 
Upvote 0 Downvote
We have SCCMADMIN Domain account which has Admin rights on SCCM Server and in SQL Server DB installed for SCCM. I don't know what else is needed. I am confused :)
 
Upvote 0 Downvote
Upvote 0 Downvote
Now, I am unable to Sync with updates, as soon as I click on Software Library -> All Software Updates my CCM console crashes.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

  • PENDING How to handle duplicate "x86/x64 unknown computer" listings within same site code
  • PENDING KB5077744 update deployment via SCCM
  • PENDING Managing MTU on network machines through SCCM Compliance
  • CM 2509 - AdminService now rejects NTLM authentication
  • Service Connection Tool improvements in SCCM 2509

    • Forum statistics

    Threads
    7,165
    Messages
    27,965
    Members
    18,264
    Latest member
    markmumford

    Latest posts

    Trending content
    Back
    Top