The SMS Executive Service (SMSExec.exe) terminates unexpectedly when reassigning distribution points in System Center Configuration Manager current branch, version 1802.
This issue may occur when multiple distribution points are reassigned in rapid succession, or during the resultant migration process. There is no crash dump log generated. However, in Event Viewer, you may see an "Event 1000, Error 0xc0000374" entry. This typically indicates a heap corruption code.
If the service continues to terminate to the point of preventing installation of this update, follow these steps:
- Determine whether this update (KB 4342419) is listed in the Ready to install state in the Updates and Servicing node of the Configuration Manager console. If it is not listed, select Check for Updates. For service connection points that are in offline mode, download and then import the update by using the Service Connection Tool
- Stop the SMS Site Component Manager and SMS Executive services, if they are running.
- Copy the file hman.dll from the service connection point that is listed under the (<SMSRoot>\EasySetupPayload\e3f4733c-2a9c-47a9-bd20-3c776f795ae1\smssetup\BIN\X64\hman.dll) folder to any site server that has the crash issue (<SMSRoot>\BIN\X64\hman.dll).
- Restart the SMS Site Component Manager and SMS Executive services.
- Apply this update from the Updates and Servicing node of the console to make sure that the correct status of Installed is shown.
Update information for System Center Configuration Manager, version 1802
This update is available for installation in the Updates and Servicing node of the Configuration Manager console on sites that satisfy the following condition:
- KB 4163547 is installed
Note If the update is not listed for a given site, it is not required.
If the service connection point is in offline mode, you must reimport the update so that it is listed in the Configuration Manager console. To check for update 4163547 in offline mode, check the Updates and Servicing node.
See Install Updates for System Center Configuration Manager for detailed information.
After you install this update on a primary site, pre-existing secondary sites must be manually updated. To update a secondary site in the Configuration Manager console, click Administration, click Site Configuration, click Sites, click Recover Secondary Site, and then select the secondary site. The primary site then reinstalls that secondary site by using the updated files.
Configurations and settings for the secondary site are not affected by this reinstallation. The new, upgraded, and reinstalled secondary sites under that primary site automatically receive this update.
Run the following SQL Server command on the site database to check whether the update version of a secondary site matches that of its parent primary site:
select dbo.fnGetSecondarySiteCMUpdateStatus ('SiteCode_of_secondary_site')
- If a value of 1 is returned, the site is up-to-date, with all the hotfixes applied on its parent primary site.
- If a value of 0 is returned, the site does not have all the fixes that were applied to the primary site installed. In this case, you should use the Recover Secondary Site option to update the secondary site.
There are no perquisites to install this update.
You do not have to restart the computer after you apply this update.
Update replacement information
This update does not replace any previously released update.