FIX SCCM Update Download Issue with Update Reset Tool

Let’s try to FIX SCCM Update Download Issue with Update Reset Tool. Have you faced SCCM CB update getting stuck in the “Downloading” state?

I have seen SCCM CB updates are getting stuck in downloading stage. But, in most of the scenarios, a service restart resolves this issue. In this post, we will see “CM Update Reset Tool Fixes SCCM CB Update Download Issue.”

[Related Post –  Fix SCCM Updates and Servicing Redist Download Issue]

Patch My PC

The other issue I encountered is REDIST prerequisite files were not getting downloaded. I could see errors related to the REDIST file download in the ConfigMgrSetup.log. I was getting the Error: Failed to download redist as discussed in the following section of the post.

Beginning with version 1706, SCCM primary sites and CAS include the Configuration Manager Update Reset Tool and CMUpdateReset.exe. The use of the tool is to fix issues when in-console updates have problems downloading or replicating. The device is found in the \cd.latest\SMSSETUP\TOOLS folder of the site server.

Issue Statement – SCCM CB Update Stuck in Downloading state

Let’s check the Issue Statement here. The SCCM CB Update is Stuck in Downloading state, and I’m trying to find the solution to fix the issue.

I checked the size of the folder C:\Program Files\Microsoft Configuration Manager\EasySetupPayload. And the size was over 1 GB. I tried to restart the SMS Executive service couple of times without any luck.

DMPDownloader.log

Let’s quickly check the log files to understand the FIX SCCM Update Download Issue.

ERROR: HasIntuneSubscription has failed to run query fn_HasIntuneSubscription with following exception : System.Data.SqlClient.SqlException (0x80131904): Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was – [Pre-Login] initialization=4997; handshake=15872; —> System.ComponentModel.Win32Exception (0x80004005): The wait operation timed out~~ at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity ERROR: Failed to download redist for c410f586-cf7a-4279-b963-139606fc25be with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=855656 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=855641 /RedistVersion 201710 /NoUI “\\SCCMTP1.INTUNE.COM\EasySetupPayload\c410f586-cf7a-4279-b963-139606fc25be\redist”

What is a CMUpdateReset.exe tool? CM Update Reset Tool

CMUpdateReset.exe is the Configuration Manager Update, Reset Tool. This is the free tool provided by Microsoft for SCCM customers. This tool is part of the CD. Latest folder and Tools folder. 

The CM Update Reset Tool is a command-line tool that should be run from the topmost server in the SCCM hierarchy.

This is the tool to help SCCM admins to fix issues when SCCM CB in-console updates have problems downloading or replicating.

The CM Update Reset tool is in the following folder \cd.latest\SMSSETUP\TOOLS. We should run this tool from CAS or a standalone primary SQL server.

More details Video Tutorial to Fix SCCM CB updates stuck in Downloading

FIX SCCM Update Download Issue with Update Reset Tool

Prerequisites – FIX SCCM Update Download Issue with CM Update Reset Tool

The account you use to run the tool (CM Update Reset Tool) requires the following permissions:

  • Read and Write permissions to the site database of the central administration site and each primary site in your hierarchy. To set these permissions, you can add the user account as a member of the db_datawriter and db_datareader fixed database roles on the Configuration Manager database of each site. The tool does not interact with secondary sites.
  • Local Administrator on the top-level site of your hierarchy.
  • Local Administrator on the computer that hosts the service connection point.

The tool (CM Update Reset Tool) must be run on the top-level site of the hierarchy.

When you run the tool, use command-line parameters to specify:

  • The SQL Server is at the top-tier site of the hierarchy.
  • The site database name at the top-tier site.
  • The GUID of the update package you want to reset.

NOTE! – Latest information https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/update-reset-tool#prerequisites

Run the CMUpdateReset.exe tool from?

From where can you run this Configuration Manager Update, Reset Tool?

  1. CAS/SQL server
  2. standalone primary/SQL server

The SCCM download reset tool (CMUpdateReset.exe) must be run on the top-level site (CAS or standalone primary) of the hierarchy. When you run the tool, use the CM Update Reset tool command-line parameters to specify:

  • The CAS/Primary SQL Server at the top-tier site of the hierarchy
  • The CAS/Primary site database name at the top-tier site
  • The GUID of the update package you want to reset

What are the SCCM Update Reset Options?

There are two options to fix SCCM Updates and Servicing Issues using the CMUpdateReset.exe tool.

  1. Reset an update and restart the download
  2. Force deletion of the problematic update package

What is the Use Case for CM Update Reset Tool?

Let’s understand the scenarios where you have to use CM Update Reset Tool to FIX the SCCM Update Download issue.

  • The update is stuck in downloading state for more than an hour
  • The update is stuck, and the EasySetupPayload folder size is not increasing at all
  • Update package replication to SCCM child primary sites are stuck for a long time
  • Update package replication to child primary server is failed
FIX SCCM Update Download Issue with Update Reset Tool
FIX SCCM Update Download Issue with Update Reset Tool

First Try – SCCM Update Reset

If you want to reset an update with download problems, you can run the following command from the topmost SQL server.

In the background, the tool will reset some SQL table entries to remove the update entry from the console. But, this action won’t delete the folders and files in C:\Program Files\Microsoft Configuration Manager\ EasySetupPayload.

CMUpdateReset.exe -S SCCMTP1.Intune.com -D CM_TP1 -P c410f586-cf7a-4279-b963-139606fc25be

The above command didn’t resolve my issue in the scenario explained in this post. I ran the command, and the update of SCCM CB 1710 got removed from the SCCM console.

Restarted the SMS Executive service, and the update came back in the console. But, the update was again stuck in downloading stage.

SCCM Update Reset Force Delete Option

Once the above command line doesn’t resolve the download or replication issue, we need to force delete the updates. This is an extreme scenario; you want to force deletion of the problematic update package.

High-Level Process of CMUpdateReset.EXE -FDELETE

  • Add all activities stored in CM_UpdatePackageSiteStatus_HIST table
  • Delete Package distribution list for update package
  • Delete update package from EasySetupSettings table
  • Delete update package from cm_updatepackageSiteStatus table
  • Delete update package from CM_UpdatePackage_MonitoringStatus table
  • Delete update package from cm_updatepackages table
  • Verify the table entries for package is deleted from CM_UpdatePackage_MonitoringStatus
  • Delete the CAB files from \SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\ folder
  • Delete the folders from \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\ folder
FIX SCCM Update Download Issue with Update Reset Tool
FIX SCCM Update Download Issue with Update Reset Tool

CM Update Reset Tool Command Line

CM Update Reset Tool command line to FIX SCCM Update Download Issue.

ParameterDescription
-S <FQDN of the SQL Server of your top-tier site>Required
Specify the FQDN of the SQL Server that hosts the site database for the top-tier site of your hierarchy.
-D <Database name>Required
Specify the name of the database at the top-tier site.
-P <Package GUID>Required
Specify the GUID for the update package you want to reset.
-I <SQL Server instance name>Optional
Identify the instance of SQL Server that hosts the site database.
-FDELETEOptional
Force deletion of a successfully downloaded update package.
CM Update Reset Tool Command Line FIX SCCM Update Download Issue with Update Reset Tool
CMUpdateReset.exe -FDELETE -S SCCMTP1.Intune.com -D CM_TP1 -P c410f586-cf7a-4279-b963-139606fc25be

Another Example – In a typical scenario, you want to reset an update that has download problems. Your SQL Servers FQDN is server1.htmd.com, the site database is CM_MEM, and the package GUID is 61F16B3C-F1F6-4F9F-8647-2A524B0C802C. You run: CMUpdateReset.exe -S server1.htmd.com -D CM_MEM -P 61F16B3C-F1F6-4F9F-8647-2A524B0C802C

Results of Command Line

FIX SCCM Update Download Issue with Update Reset Tool results are given below.

C:\Program Files\Microsoft Configuration Manager\cd.latest\SMSSETUP\TOOLS\CMUpdateReset>CMUpdateReset.exe -FDELETE -S SCCMTP1.Intune.com -D CM_TP1 -P c410f586-cf7a-4279-b963-139606fc25be
[Warning]
You can use this tool when an in-console update has not yet installed and is in a failed state. A failed state can mean the update download remains in progress but is stuck and taking an excessively long time, perhaps hours longer than your historical expectations for update packages of similar size. It can also be a failure to replicate the update to child primary sites. When you run the tool, it runs against the update that you specify. If the package is in pre-installation state, it will delete it. If package is in replicating state, it will reinitiate replication. Are you sure you want to run the tool? Enter Y for Yes and N for No.
Y
Running CMUpdateReset.exe tool ...
Verified that the SQL server FQDN belongs to the top level site.
Verified that the site servers run version 1606 or later.
Verified that replication is active.
Package is in pre-installation state. Attempting to clean up the package.
Verified that the service connection point is installed on the top level site.
Verified that the account has permission to service connection point share.
Verified that the account has permission to the inboxes\hman.box folder.
Service SMS_EXECUTIVE is Running on machine SCCMTP1.Intune.com.
Verified that service SMS_EXECUTIVE is running on machine SCCMTP1.Intune.com.
Service CONFIGURATION_MANAGER_UPDATE is Running on machine SCCMTP1.Intune.com.
Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine SCCMTP1.Intune.com.
Verified that the package is not in post-replication state for all the child sites (if any).
Marking package in the package distribution list as deleted.
(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Marked package in the package distribution list as deleted.
Deleting update package c410f586-cf7a-4279-b963-139606fc25be from EasySetupSettings table on site server SCCMTP1.Intune.com.
(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from EasySetupSettings table.
Deleting update package c410f586-cf7a-4279-b963-139606fc25be from cm_updatepackageSiteStatus table on site server SCCMTP1.Intune.com.
(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.
Deleting update package c410f586-cf7a-4279-b963-139606fc25be from CM_UpdatePackage_MonitoringStatus table on site server SCCMTP1.Intune.com.
(0 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from cm_updatepackageSiteStatus table.
Deleting update package c410f586-cf7a-4279-b963-139606fc25be from cm_updatepackages table on site server SCCMTP1.Intune.com.
(1 row(s) affected.)
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Update package is deleted from CM_UpdatePackage_MonitoringStatus table.
Verifying whether the table entries for package c410f586-cf7a-4279-b963-139606fc25be is deleted on site server SCCMTP1.Intune.com.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\c410f586-cf7a-4279-b963-139606fc25be.cab.
Deleted \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\c410f586-cf7a-4279-b963-139606fc25be.cab.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\Offline\c410f586-cf7a-4279-b963-139606fc25be.cab.
\\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\Offline\c410f586-cf7a-4279-b963-139606fc25be.cab does not exist to delete.
Deleting \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\Offline\ConfigMgr.Update.Manifest.cab
\\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\Offline\ConfigMgr.Update.Manifest.cab does not exist to delete.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\c410f586-cf7a-4279-b963-139606fc25be.
Deleted \\SCCMTP1.Intune.com\sms_TP1\EasySetupPayLoad\c410f586-cf7a-4279-b963-139606fc25be.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting cmupdate notifications.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
[Success]Successfully ran the CMUpdateReset.exe tool. If the tool deleted the package (check Updates and Servicing to see if the package is listed), you must restart the SMS_EXECUTIVE service on the top level site. Or, use Check for Update in console to redownload the package.
If the package is reinitiating replication or installation, DO NOT restart the SMS_EXECUTIVE service. You can use the flowchart at (https://docs.microsoft.com/sccm/core/servers/manage/update-replication-flowchart) to troubleshoot additional issues..

Success – SCCM CB Update Downloaded

After running the tool, I restarted the SMS Executive service. The updated entry for SCCM 1710 has been created, and it was ready “Available to Download” state.

I started the download, and it finished downloading the update. Now the update state is “Ready to Install.”

Log entries of Successful completion of SCCM CB update Download 

EasySetupDownloadSinglePackage finishes downloading c410f586-cf7a-4279-b963-139606fc25be.
Successfully Dropped the state message 13
Generating state message: 13 for package c410f586-cf7a-4279-b963-139606fc25be
Generating state message: 13 for package c410f586-cf7a-4279-b963-139606fc25be~~ $<SMS_DMP_DOWNLOADER><11-05-2017 11:40:30.480-330><thread=5984 (0x1760)>
Write the state message in C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\high\___CMUvx2u44jq.SMX~~ $<SMS_DMP_DOWNLOADER><11-05-2017 11:40:30.500-330><thread=5984 (0x1760)>
Successfully Dropped the state message 13~~ $<SMS_DMP_DOWNLOADER><11-05-2017 11:40:30.533-330><thread=5984 (0x1760)>
EasySetupDownloadSinglePackage finishes downloading c410f586-cf7a-4279-b963-139606fc25be. ~~ $<SMS_DMP_DOWNLOADER><11-05-2017 11:40:30.557-330><thread=5984 (0x1760)>
Get Easy Setup installed Packages to delete payload~~ $<SMS_DMP_DOWNLOADER><11-05-2017 11:40:30.577-330><thread=5984 (0x1760)>

SCCM Update Download Issues is Not Fixed by CM Update Reset Tool?

What if SCCM Update Download Issues are not Fixed by CM Update Reset Tool?? The following are the steps to download SCCM updates. The command-line tool CMUpdateReset.exe didn’t help to fix it; what next? 

You can check this download status from the SCCM monitoring workspace. More details are in the log file ConfigMgrSetup.log.

  1. Process update package
  2. Download the updated package cab file
  3. Extract update package payload
  4. Download redist
  5. Report package as downloaded

FIX SCCM CB Download Stuck at REDIST prerequisite files

In my scenario, REDIST prerequisite files were not getting downloaded. I could see errors related to the REDIST file download in the ConfigMgrSetup.log.  If you have problems downloading redist files, then, ConfigMgrSetup.log is the best place to get the root of the issue.

As I explained in my previous post, I downloaded the prerequisite files separately using SETUPDL.EXE, “Learn How to Download SCCM ConfigMgr CB Prerequisite Files“.

Once the prerequisite files are downloaded then, copy those files to D:\Program Files \Microsoft Configuration Manager\EasySetupPayload\<Update PackageGUID >\Redist folder.

I don’t recommend doing this in your production environment. Thanks to Robert Marshall’s tip, which helped me to resolve the issue. I have mentioned this in the tweet

FIX SCCM CB Redist Files Download Issue FIX SCCM Update Download Issue with Update Reset Tool
FIX SCCM CB Redist Files Download Issue – FIX SCCM Update Download Issue with Update Reset Tool

SCCM Download Issues

The above section of the post “CMUpdateReset.exe Tool Fixes SCCM CB Update Download Issue” has more details. But it didn’t work for me this time. I was getting the following error in the DMPDownloader.log.

I struggle to complete the download of the SCCM CB version in my test lab. I had gone through my previous posts to fix the download issue.

  • ERROR: Failed to download redist for 51d629d3-c355-4b80-ad6f-ba44b27f84ed with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=860262 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=860266 /RedistVersion 201712 /NoUI “\SCCMTP1.INTUNE.COM\EasySetupPayload\51d629d3-c355-4b80-ad6f-ba44b27f84ed\redist”
  • Failed to download redist for 51d629d3-c355-4b80-ad6f-ba44b27f84ed.

I could see the actual download of the SCCM update had happened on the following path “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload”.

But the status is not changing from Downloading to Ready to Install. The fix Fix to the SCCM Redist download issue has been explained below.

FIX SCCM CB Redist Files Download Issue
FIX SCCM CB Redist Files Download Issue FIX SCCM Update Download Issue with Update Reset Tool

Following are the 5 high-level processes in the background when the SCCM CB updates will get downloaded to your server.

  1. Process update package
  2. Download the updated package cab file
  3. Extract update package payload
  4. Download redist
  5. Report package as downloaded

References

Author

Anoop is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is Blogger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

17 thoughts on “FIX SCCM Update Download Issue with Update Reset Tool”

  1. My update is stucked in checking prerequisites, its been for more than a day now. i don’t see anything in monitoring as well. What shall i do next ?

    Reply
  2. Hi Anoop,

    I am getting “failed to extract the payload cab of package tp \\<LAB01.lab.com\EasySetupPaload\” error. In order to resolve, I tried method describe above, however, I am getting following error:

    0x80131904 – Subquery returned more than 1 value.

    Any suggestions ?

    Reply
  3. Installed update / hotfix KB4490434 but after installation showing full version showing 5.00.8740.1033 but client version showing blank why it is showing blank it should show same version…

    any idea why ?

    Reply
  4. Question 1
    Installed hotfix KB4490434 and after installation showing full version as 5.00.8740.1033 but client version showing blank, why it is showing blank it should show same version…
    any idea why ?

    Question 2
    Any idea about meaning of below error showing in dmpdownloder.log file
    ERROR: Failed to download Admin UI content payload with exception: The underlying connection was closed: Could not established trust relationship for the SSL/TLS secure channel.
    Failed to call AdminUIContentDownload. error = Error -2146233079

    Reply
  5. Any advice for when this happens:

    Running CMUpdateReset.exe tool …
    Verified that the SQL server FQDN belongs to the top level site.
    Verified that the site servers run version 1606 or later.

    Verified that replication is active.

    Package is in pre-installation state. Attempting to clean up the package.

    Verified that the service connection point is installed on the top level site.
    Verified that the account has permission to service connection point share.
    Verified that the account has permission to the inboxes\hman.box folder.

    Service SMS_EXECUTIVE is Running on machine cas.mydomain.org.
    Verified that service SMS_EXECUTIVE is running on machine cas.mydomain.org.

    Service SMS_EXECUTIVE is Running on machine site2.mydomain.org.
    Verified that service SMS_EXECUTIVE is running on machine site2.mydomain.org.

    Service SMS_EXECUTIVE is Running on machine site1.mydomain.org.
    Verified that service SMS_EXECUTIVE is running on machine site1.mydomain.org.

    Service CONFIGURATION_MANAGER_UPDATE is Running on machine cas.mydomain.org.
    Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine cas.mydomain.org.

    Service CONFIGURATION_MANAGER_UPDATE is Running on machine site2.mydomain.org.
    Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine site2.mydomain.org.

    Service CONFIGURATION_MANAGER_UPDATE is Running on machine site1.mydomain.org.
    Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine site1.mydomain.org.

    [Error]
    0xSystem.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred dur
    ing the login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.) —> Syste
    m.ComponentModel.Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted
    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCred
    ential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionStr
    ing userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)

    at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroup
    ProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
    at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOpti
    ons options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)
    at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInterna
    l oldConnection)
    at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionIn
    ternal oldConnection)
    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean al
    lowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
    at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOption
    s userOptions, DbConnectionInternal& connection)
    at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectio
    nOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
    at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFa
    ctory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
    at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
    at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
    at System.Data.SqlClient.SqlConnection.Open()
    at Microsoft.ConfigurationManagement.ResetTool.DatabaseProxy.GetPackageSiteState(String packageGuid)
    ClientConnectionId:df154402-6826-439a-87cf-707bcd7572f1
    Error Number:-2146893019,State:0,Class:20 – A connection was successfully established with the server, but then an error occurred during the
    login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.)
    Verified that the package is not in post-replication state for all the child sites (if any).
    Marking package in the package distribution list as deleted.

    (1 row(s) affected.)
    Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
    [Error]
    0x80131904 – Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, , >= or when the subquery
    is used as an expression.
    The statement has been terminated.

    Reply
  6. Hi Anoop, i am facing the similar issue getting the latest 1910 update, tried both standard and FDELETE still stuck at downloading and dmpdownloader.log has the below error:

    ERROR: Failed to download redist for e2f7b2f9-4828-4650-9144-5dc7956781b7 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=2057682 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=2057571 /RedistVersion 201910 /NoUI “\\SERVERNAME\EasySetupPayload\e2f7b2f9-4828-4650-9144-5dc7956781b7\redist” .

    However i see that EasySetupPayload (3.45GB) has got a e2f7b2f9-4828-4650-9144-5dc7956781b7.cab file and extracted folder e2f7b2f9-4828-4650-9144-5dc7956781b7

    i have tried restart the server, restarting the SMS_EXECUTIVE service and also check for updates option. Any suggestions?

    Regards, Abhi

    Reply
  7. Hi Anoop,

    thanks for you website and videos.

    i’m trying to launch ‘CMUUpdateReset.exe -S ‘with elevating credentials, and I encountered an [error 25 : connection string is not valid]

    [Error]
    0x80131904 – A network-related or instance-specific error occurred while establi
    shing a connection to SQL Server. The server was not found or was not accessible
    . Verify that the instance name is correct and that SQL Server is configured to
    allow remote connections. (provider: SQL Network Interfaces, error: 25 – Connect
    ion string is not valid)
    I checked the SQL database with sccm sql credentials into SQL Management studio and it works well.

    Every port is open (firewalls like 1433 )
    sql services are all running, this is very strange.
    Do you have an idea?

    Thanks a lot.

    Reply
  8. Hello, So I am working on this exact issue, I attempted to upgrade to 2006 via updates and servicing. It has been stuck at Checking prerequisites for a few days now. So trying to fix this issue, I see that the configuration_Manager_update Service has stopped. When I try to start it I get: Error 2: The system Cannot find the file specified. And i find out that in C:\Program Files\Microsoft Configuration Manager\bin\X64 I am missing the CMUPDATE.exe file. If i do a site system repair will i get this file back or do you suggest a different fix?

    Reply
  9. I know this is an old thread, but if it would be helpful to anyone else facing this issue.

    Please check for the CMUPDATE.EXE inside CD.latest folder and you can copy it here.

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.