top of page

Group

Public·18 members
Jordan Lopez
Jordan Lopez

CI Documents Download Timed Out: A Guide for Configuration Manager Administrators


How to Fix CI Documents Download Time Out Error in SCCM




If you are using SCCM (System Center Configuration Manager) to deploy applications to your devices, you may encounter an error that says "CI documents download timed out" or "CI version info timed out". This error means that the configuration item (CI) documents that contain the information about the application requirements, detection methods, and installation commands could not be downloaded from the distribution point within the specified time limit. As a result, the application deployment fails and does not show up in the Software Center for the affected devices.


This error can be frustrating and prevent you from installing the applications you need. In this article, we will explain what causes this error and how to fix it. We will also share some best practices for CI documents download to avoid this error in the future.




ci documents download time out



What is CI Documents Download Time Out Error?




CI documents are XML files that describe the configuration items (CIs) that are used by SCCM to manage applications, settings, and compliance. CIs are stored in the SCCM database and replicated to the distribution points. When an application is deployed to a device, the device downloads the CI documents from the distribution point to evaluate if it meets the application requirements, how to detect if the application is already installed, and how to install or uninstall the application.


However, sometimes the device may fail to download the CI documents within the time limit set by SCCM. This can happen due to various reasons, such as network issues, firewall settings, corrupted files, or misconfigured settings. When this happens, the device reports an error code 0x87D0027C (CI documents download timed out) or 0x87D00314 (CI version info timed out) to SCCM. The application deployment status shows as "Failed" or "Unknown" in the SCCM console and the Software Center.


Causes of CI Documents Download Time Out Error




There are several possible causes of CI documents download time out error, such as:



  • The network connection between the device and the distribution point is slow or unstable.



  • The firewall or antivirus software on the device or the distribution point is blocking or interfering with the CI documents download.



  • The CI documents are corrupted or missing on the distribution point.



  • The device has an outdated or incorrect policy or configuration.



  • The device has insufficient disk space or memory to download or process the CI documents.



  • The SCCM client on the device is not working properly or needs to be updated.



Solutions for CI Documents Download Time Out Error




Depending on the cause of the error, there are different solutions that you can try to fix it. Here are some common solutions that may work for you:


Solution 1: Re-run the Machine and App Deployment Cycles




One of the simplest solutions is to re-run the machine policy evaluation cycle and the application deployment evaluation cycle on the affected device. This will force the device to refresh its policy and configuration from SCCM and re-evaluate its application deployments. To do this, follow these steps:


How to fix ci documents download time out error in SCCM


SCCM application deployment fails with ci documents download time out


Troubleshooting ci documents download time out issue in Configuration Manager


What causes ci documents download time out error code 0x87D0027C


How to resolve ci documents download time out problem in Microsoft Intune


Ci documents download time out error reference and solutions


Best practices for avoiding ci documents download time out errors in application installation


Ci documents download time out and CI Version Info timed out errors in CIDownloader.log


How to increase ci documents download timeout value in SCCM


Ci documents download time out error when deploying Flash Player and Shockwave Player


How to decompress CI documents after ci documents download time out error


Ci documents download time out error due to DTS failure message


How to simulate CI documents download in system context to troubleshoot ci documents download time out error


Ci documents download time out error after applying SCCM 2012 SP1 CU1 update


How to use select-string cmdlet to search for CI documents download related errors in logs


Ci documents download time out error when targeting applications to tenant attached devices from Microsoft Intune admin center


How to use PSExec to test CI documents download command line and avoid ci documents download time out error


Ci documents download time out error when installing applications with MSI files


How to use CIAgent.log, CIDownloader.log, and DataTransferService.log to track CI documents download activity and errors


Ci documents download time out error when installing applications with scripts


How to check CI documents download status and progress in Configuration Manager console


Ci documents download time out error when installing applications with PowerShell scripts


How to use Configuration Manager SDK to troubleshoot CI documents download issues and errors


Ci documents download time out error when installing applications with WMI queries


How to use Configuration Manager Trace Log Tool (CMTrace) to view CI documents download related logs and errors


Ci documents download time out error when installing applications with Windows Update Agent


How to use Configuration Manager Support Center to collect CI documents download related data and logs


Ci documents download time out error when installing applications with Windows Installer (MSI)


How to use Configuration Manager Status Message Viewer to view CI documents download related messages and errors


Ci documents download time out error when installing applications with Windows Installer XML (WiX)


How to use Configuration Manager Service Manager to monitor CI documents download related services and components


Ci documents download time out error when installing applications with App-V packages


How to use Configuration Manager Resource Explorer to view CI documents download related properties and settings


Ci documents download time out error when installing applications with MSIX packages


How to use Configuration Manager SQL Server Reporting Services (SSRS) to generate CI documents download related reports and charts


Ci documents download time out error when installing applications with Chocolatey packages


How to use Configuration Manager PowerShell cmdlets to manage CI documents download related tasks and operations


Ci documents download time out error when installing applications with OneGet packages


How to use Configuration Manager Desired Configuration Management (DCM) to evaluate CI documents download compliance and settings


Ci documents download time out error when installing applications with ClickOnce packages


How to use Configuration Manager Software Center to view and install CI documents downloaded applications


Ci documents download time out error when installing applications with NuGet packages


How to use Configuration Manager Application Catalog to browse and request CI documents downloaded applications


Ci documents download time out error when installing applications with Ninite packages


How to use Configuration Manager Client Health Evaluation Tool (CCMEval) to check CI documents download related client health issues and errors



  • On the device, open Control Panel and go to System and Security > Configuration Manager.



  • On the Actions tab, select Machine Policy Retrieval & Evaluation Cycle and click Run Now.



  • Select Application Deployment Evaluation Cycle and click Run Now.



  • Wait for a few minutes and check if the application deployment status changes in SCCM console and Software Center.



S Solution 2: Remove the Deployment and Re-deploy




Another solution is to remove the application deployment from SCCM and re-deploy it to the affected device. This will clear any cached or corrupted data and create a new deployment with fresh CI documents. To do this, follow these steps:



  • In the SCCM console, go to Software Library > Application Management > Applications.



  • Select the application that is causing the error and click Deployments.



  • Select the deployment that is targeting the affected device and click Delete.



  • Confirm the deletion and wait for the changes to replicate.



  • Right-click the application and click Deploy.



  • Follow the wizard to create a new deployment with the same settings as before.



  • Wait for the new deployment to reach the affected device and check if the error is resolved.



Solution 3: Recreate the Package Deployment Type and Redeploy




A more advanced solution is to recreate the package deployment type for the application and redeploy it to the affected device. This will ensure that the CI documents are generated correctly and match the application content. To do this, follow these steps:



  • In the SCCM console, go to Software Library > Application Management > Applications.



  • Select the application that is causing the error and click Deployment Types.



  • Select the package deployment type and click Properties.



  • On the Content tab, note down the content location and version.



  • Click OK to close the properties window.



  • Right-click the package deployment type and click Delete.



  • Confirm the deletion and wait for the changes to replicate.



  • Right-click the application and click Create Deployment Type.



  • Follow the wizard to create a new package deployment type with the same content location and version as before.



  • Right-click the application and click Deploy.



  • Follow the wizard to create a new deployment with the same settings as before.



  • Wait for the new deployment to reach the affected device and check if the error is resolved.



Best Practices for CI Documents Download




To prevent CI documents download time out error from happening again, you should follow some best practices for CI documents download. Here are some tips that can help you:


Treat Your Infrastructure as Code




One of the benefits of using SCCM is that you can treat your infrastructure as code. This means that you can use scripts, templates, and version control to manage your configuration items, applications, settings, and compliance. This way, you can ensure consistency, reliability, and repeatability of your deployments. You can also automate your processes, test your changes, and troubleshoot your issues more easily. For example, you can use PowerShell scripts to create or update your CI documents, or use Git to track your changes and revert them if needed.


Read the Documentation




Another best practice is to read the documentation provided by Microsoft for SCCM. The documentation contains valuable information on how to use SCCM features, how to configure your settings, how to troubleshoot your problems, and how to optimize your performance. You can also find examples, tutorials, videos, blogs, forums, and other resources that can help you learn more about SCCM. For example, you can read this article on how to manage applications in SCCM, or this article on how to troubleshoot application deployments in SCCM. Reading the documentation can help you avoid common mistakes and resolve issues faster.


Optimize Pipeline Stages




A third best practice is to optimize your pipeline stages for CI documents download. A pipeline stage is a step in your deployment process that involves downloading or processing CI documents. For example, when you deploy an application to a device, there are three pipeline stages: downloading CI documents from distribution point (DP), processing CI documents on device (CD), and installing application on device (ID). Each pipeline stage has a time limit set by SCCM. If any stage exceeds its time limit, it will cause a time out error.


To optimize your pipeline stages, you should do the following:



  • Ensure that your network connection between your devices and distribution points is fast and stable. You can use tools like ping or traceroute to test your network latency and bandwidth.



  • Ensure that your firewall or antivirus software on your devices or distribution points is not blocking or interfering with your CI documents download. You can check your firewall or antivirus logs or settings to see if there are any issues.



  • Ensure that your CI documents are Ensure that your CI documents are not corrupted or missing on your distribution points. You can use tools like Content Library Explorer or Content Library Cleanup to verify and repair your content on your distribution points.



  • Ensure that your device has enough disk space and memory to download and process your CI documents. You can use tools like Disk Cleanup or Task Manager to free up some space and memory on your device.



  • Ensure that your SCCM client on your device is working properly and up to date. You can use tools like Client Center for Configuration Manager or Configuration Manager Support Center to check and fix your client issues.



  • Adjust the time limit settings for your pipeline stages in SCCM. You can use the registry keys or the client settings to increase or decrease the time limit for each stage. For example, you can use the registry key HKLM\Software\Microsoft\CCM\CcmEval\DownloadTimeOutSecs to change the time limit for downloading CI documents from distribution point. However, you should be careful not to set the time limit too high or too low, as it may affect your performance or cause other errors.



Conclusion




CI documents download time out error is a common error that occurs when a device fails to download the CI documents from the distribution point within the time limit set by SCCM. This error can prevent the application deployment from succeeding and cause frustration for the users and administrators. However, by following the solutions and best practices in this article, you can fix this error and ensure a smooth and successful application deployment.


FAQs




Here are some frequently asked questions about CI documents download time out error:



  • What is the default time limit for downloading CI documents from distribution point?



The default time limit for downloading CI documents from distribution point is 60 seconds. You can change this value by using the registry key HKLM\Software\Microsoft\CCM\CcmEval\DownloadTimeOutSecs.


  • What is the default time limit for processing CI documents on device?



The default time limit for processing CI documents on device is 120 seconds. You can change this value by using the registry key HKLM\Software\Microsoft\CCM\CcmEval\EvalTimeOutSecs.


  • What is the default time limit for installing application on device?



The default time limit for installing application on device is 120 minutes. You can change this value by using the client setting Maximum Run Time under Computer Agent in SCCM console.


  • How can I check the error code and message for a failed application deployment?



You can check the error code and message for a failed application deployment by using the SCCM console, the Software Center, or the log files. In the SCCM console, you can go to Monitoring > Deployments > Application Name > Deployment Status > Error Details. In the Software Center, you can go to Installation Status > Application Name > More Information. In the log files, you can go to C:\Windows\CCM\Logs\AppEnforce.log or C:\Windows\CCM\Logs\AppDiscovery.log on the device.


  • How can I troubleshoot other issues related to CI documents download?



You can troubleshoot other issues related to CI documents download by using various tools and methods, such as:


  • Using Content Library Explorer or Content Library Cleanup to verify and repair your content on your distribution points.



  • Using Client Center for Configuration Manager or Configuration Manager Support Center to check and fix your client issues.



  • Using ping or traceroute to test your network latency and bandwidth.



  • Using firewall or antivirus logs or settings to see if there are any blocks or interferences.



  • Using Disk Cleanup or Task Manager to free up some space and memory on your device.



  • Using PowerShell scripts or Git to manage your configuration items, applications, settings, and compliance.



  • Reading the documentation provided by Microsoft for SCCM.





About

Welcome to the group! You can connect with other members, ge...

Members

bottom of page