Troubleshooting SCCM Error: ExecStaticMethod Failed (80070016) SMS_DistributionPoint, AddFile

When managing software distribution in Microsoft System Center Configuration Manager (SCCM), encountering errors in the PkgXferMgr.log file can be frustrating. One common issue is the error:

ExecStaticMethod failed (80070016) SMS_DistributionPoint, AddFile.

This article provides a detailed overview of this error, its causes, and effective troubleshooting steps. By the end, you’ll be equipped to resolve this issue and ensure smooth package transfers in SCCM.

What Does Error 80070016 Mean?

In SCCM, the error 80070016 typically occurs when attempting to transfer a package or file to a distribution point. Here’s a breakdown:

• ExecStaticMethod failed: Indicates a failure in invoking a method within SCCM’s internal processes.
• 80070016: This HRESULT error code translates to “The device does not recognize the command” or may indicate a file access issue, such as the file being locked or inaccessible.
• SMS_DistributionPoint, AddFile: Specifies that the failure happened during the process of adding a file to the distribution point.

Common Causes of Error 80070016

Several factors can trigger this error, including:

1. File Locking Issues: The file being transferred is locked or in use by another process.
2. Permissions Problems: The SCCM service account lacks the necessary permissions to access the file or write to the distribution point.
3. Low Disk Space: The distribution point has insufficient storage for the incoming files.
4. Corrupt Package or File: One or more files in the package may be corrupted.
5. Distribution Point Configuration Errors: The distribution point might be offline, misconfigured, or experiencing network connectivity issues.

How to Fix SCCM Error 80070016

Here’s a step-by-step guide to troubleshoot and resolve the error:

1. Check the Log Files for Details

• Open PkgXferMgr.log and distmgr.log on the SCCM server.
• Look for error messages related to file transfer or distribution point communication. Identify the file or package causing the issue.

2. Verify File Locking

• Use a tool like Process Explorer to check if the problematic file is locked or in use by another process.
• If locked, terminate the process holding the file or retry the operation after ensuring no processes are using it.

3. Check Permissions

• Ensure the SCCM service account has Full Control permissions on the source folder and the distribution point destination.
• Verify that these permissions are correctly propagated to all subfolders.

4. Inspect Disk Space

• Log in to the distribution point and check the available disk space.
• Clear unnecessary files or extend the volume if space is insufficient.

5. Redistribute the Package

• In the SCCM console:
  • Navigate to Monitoring > Distribution Status > Content Status.
  • Right-click the affected package and select Redistribute to trigger the transfer again.

6. Validate the Distribution Point

• Confirm that the distribution point is online and reachable.
• Use the Distribution Point Configuration Status node in SCCM to identify any misconfigurations.

7. Repair or Rebuild the Package

• If the error persists, remove the problematic package from the distribution point, recreate it, and redistribute.

Advanced Troubleshooting Tips

If the above steps do not resolve the issue, consider these additional tips:

Test Network Connectivity

• Use commands like ping or tracert to test connectivity between the SCCM server and the distribution point.

Review SCCM Boundaries

• Ensure that the distribution point falls within a properly configured boundary group in SCCM.

Update SCCM

• Outdated SCCM versions or hotfixes can sometimes lead to errors. Ensure your SCCM environment is updated to the latest supported version.

Preventing Future Issues

To minimize the chances of encountering errors like 80070016 in the future:

1. Monitor Distribution Points Regularly:
   • Use SCCM’s built-in monitoring tools to proactively track the status of distribution points.
2. Schedule Regular Maintenance:
   • Regularly check for disk space, permissions, and network connectivity.
3. Keep SCCM Updated:
   • Apply the latest cumulative updates and hotfixes from Microsoft.

Conclusion

The ExecStaticMethod failed (80070016) SMS_DistributionPoint, AddFile error in SCCM can disrupt package distribution but is often resolved by addressing file locking, permissions, or disk space issues. By following the steps outlined above, you can diagnose and fix the root cause effectively.