Is the SQL server running on the same server as ConfigMgr?. Also, in the command, can you enter the FQDN of the server and try?.
Your question is the answer, because a wrote failure the FQDN !
After corrected the command successfully ran:
D:\SCCM\cd.latest\SMSSETUP\TOOLS\CMUpdateReset>CMUpdateReset.exe -S RP-CSQL04.GRPS.LOCAL -D CM_KER -P A682F854-A8AF-4F25-83B0-D9CFDFAFE659
[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 rp-vsccm01.grps.local.
Verified that service SMS_EXECUTIVE is running on machine rp-vsccm01.grps.local.
Service CONFIGURATION_MANAGER_UPDATE is Running on machine rp-vsccm01.grps.local.
Verified that service CONFIGURATION_MANAGER_UPDATE is running on machine rp-vsccm01.grps.local.
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 A682F854-A8AF-4F25-83B0-D9CFDFAFE659 from EasySetupSettings table on site server RP-CSQL04.GRPS.LOCAL.
(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 A682F854-A8AF-4F25-83B0-D9CFDFAFE659 from cm_updatepackageSiteStatus table on site server RP-CSQL04.GRPS.LOCAL.
(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 A682F854-A8AF-4F25-83B0-D9CFDFAFE659 from CM_UpdatePackage_MonitoringStatus table on site server RP-CSQL04.GRPS.LOCAL.
(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 A682F854-A8AF-4F25-83B0-D9CFDFAFE659 from cm_updatepackages table on site server RP-CSQL04.GRPS.LOCAL.
(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 A682F854-A8AF-4F25-83B0-D9CFDFAFE659 is deleted on site server RP-CSQL04.GRPS.LOCAL.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\A682F854-A8AF-4F25-83B0-D9CFDFAFE659.cab.
\\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\A682F854-A8AF-4F25-83B0-D9CFDFAFE659.cab does not exist to delete.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting \\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\Offline\A682F854-A8AF-4F25-83B0-D9CFDFAFE659.cab.
Deleted \\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\Offline\A682F854-A8AF-4F25-83B0-D9CFDFAFE659.cab.
Deleting \\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\Offline\ConfigMgr.Update.Manifest.cab.
\\rp-vsccm01.grps.local\sms_KER\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 \\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\A682F854-A8AF-4F25-83B0-D9CFDFAFE659.
\\rp-vsccm01.grps.local\sms_KER\EasySetupPayLoad\A682F854-A8AF-4F25-83B0-D9CFDFAFE659 does not exist to delete.
Adding entry in CM_UpdatePackageSiteStatus_HIST for history tracking.
(1 row(s) affected.)
Deleting cmupdate notifications.
Deleting \\rp-vsccm01.grps.local\sms_KER\inboxes\hman.box\CFD\2.ESC.
Deleted \\rp-vsccm01.grps.local\sms_KER\inboxes\hman.box\CFD\2.ESC.
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..
------------------------------------------------------------
I really like it, but doesn't disappeared the CM_2103 in the Updates and Servicing list:
I have restarted the SCCM-server, but it is still in the list.
So, what shell I do to clear it?
Can I remove the another CM update packs?
Thank U!
