Everyone has encountered an error message while deploying an application or updating an existing one, and the code that follows sometimes provides minimal context. The 0x87d00607 (-2016410105) error mainly occurs in the configurations of the Microsoft Endpoint Configuration Manager (MECM), formerly called System Center Configuration Manager (SCCM). If you have encountered this error, you can rest assured that this article will detail the causes and how to rectify the issue.
What Does Error Code 0x87d00607 Indicate?
The error message associated with this error code is ‘This operation has been cancelled due to an unspecified error’, while its numerical value, 0x87d00607, is interpreted as a content location error.
Possible causes of this error may include the following:
- Lack of proper content distribution: At times, the organization may have failed to distribute the software package to the right distribution points.
- Lack of connectivity: Hence the client machines may be unable to connect with the distribution point.
- Incorrect boundary and boundary groups: Clients cannot access the content if they are in the wrong boundary or boundary group.
- Corrupted or missing package content: Some of the contents that are supposed to be present in the distribution point might have been corrupted or omitted.
How to Fix Error Code 0x87d00607 (-2016410105)
Below are the mentioned steps to fix the problem:
1. Verify Content Distribution
Distribution Status: Open the Configuration Manager Console and go to Monitoring/ Distribution Status/ Content Status. Now, choose the affected package and ensure it is present in each distribution point that should receive it.
Redistribute Product: If the package’s status fails or if it is not available in all the distribution points, go to actions and click on Redistribute. After this, allow some time for the process to run and recheck its status.
2. Check on the Boundary and Boundary Group Configuration
Use the navigational menu: Administration > Hierarchy Configuration > Boundaries. However, ensure that depth includes the client’s IP address or subnet in a predetermined scope.
Check Boundary Groups: Under Administration> Hierarchy Configuration > Boundary Groups, ensure that the boundary with the specific client is included from the boundary groups. It is also essential that this group is connected to an appropriate distribution point if it will be issued.
Associate Distribution Points: Validate that the Distribution Points hosting the content are correctly linked with the correct Boundary Group. Thus, clients within the boundary group will not know where they can download the content if this link is not provided.
3. Test Network Connectivity
Ping the Distribution Point: Using any client machine, ping the distribution point to ascertain if the network connectivity is intact. Use the command:
ping <distribution_point_FQDN>
Internet connection: Make sure there are no firewalls or restrictions that may hinder the client’s internet connection to the distribution point.
4. Validate Package Integrity
Use Content Library Explorer: The Content Library Explorer tool can be obtained from the MECM toolkit and should be run. This tool can assist you in determining whether the package is available and well-inclosed on the distribution point.
Remove & Redistribute: In case of corruption, removing the package from the distribution point is recommended and then putting the package back. To do this:
- To uninstall the package, click its name in the Content Status section and select the Remove option from the context menu.
- Once removed, redistribute the content.
5. Review Logs for More Details
Client-Side Logs: Review the client-side log files stored at C:\Windows\CCM\Logs. The list of logs helpful in fixing this error is as follows:
Content download activity: This indicates the data transfer service log.
CAS.log: This file consists of the details about the content which had been accessed to which source.
Server-Side Logs:On the site server, the package should show that it is being distributed correctly in distmgr.log and PkgXferMgr.log.
6. Reinstall the Configuration Manager Client
If all else is inconclusive, issues underlying issues may be solved by reinstalling the Configuration Manager client. Use the following steps:
- Log into the infected client operating system using an administrative account and open an administrative command window.
- To uninstall the client use the following command:
ccmsetup.exe /uninstall
- Reinstall the client using:
ccmsetup.exe
A good parameter is to monitor the logs generated during the client’s installation, known as ‘Ccmsetup.log,’ to confirm that it has been properly reinstated.
Conclusion
MECM environments are not immune to error code 0x87d00607 (2016410105), yet it can be solved successfully using a detailed procedure. This type of error can be prevented by checking content distribution, validating boundaries, and even checking the device’s network connectivity. In case of further problems, external help is always available in the form of Microsoft support and community help.
, yet it can be solved successfully using a detailed procedure.){kind=link}