You can also review the Package Processing Queue and Packages Being Processed registry values under the following registry key to see how many packages are currently in the Processing Queue:. If this happens, capture a process dump of SMSExec. If there are many packages in the queue but the queue is moving, it may be necessary to review and change the thread configuration. Filtering the DistMgr. If necessary, reboot the DP to see if that helps. If the filtered DistMgr. If PkgXferMgr.

See Bandwidth control and threads for more information. If you see this in the log, it means that the DP is under bandwidth control and the address to the DP closed while content transfer was in progress. This happens if the site server and the site database servers are in different time zones.

The solution here is to ensure that the site server and site database servers have the same time zone set. PkgXferMgr runs the following query to check how many jobs are currently in an unfinished state on the pull DP. If the query returns more than 50 jobs, it will not send any more jobs to the pull DP. These jobs are removed from the DistributionJobs table when pull DP sends a Success state message or when the status polling stops based on configured values. This is a known issue because the signature files are not present on a Source DP that is colocated on a site server.

This issue only occurs when the distribution action is not redist. This issue may occur due to RPC port allocation failures caused by firewall.

It can also occur when Windows Firewall service is disabled. Check to see if there is a firewall between the site server and the affected server and find out if RPC ports are open. You can also capture a Network Trace from the pull DP as well as the source DP server while reproducing the error for review. In some instances normally after installation of a new pull DP when all content is sent to the pull DP , too many job failures on the pull DP can end up stalled processing of the jobs.

Although most of these issues are fixed in the recent releases of the product Configuration Manager version , some environmental factors can result in pull DP not processing jobs. In this scenario, it can be beneficial to remove all the job-specific items from WMI on the pull DP and distribute the content again to the pull DP in a controlled manner and investigate failures. This happens when the pull DP response is processed. Review steps in Distribute a package to pull DP to understand the flow and review the relevant logs to investigate why the state message is not getting processed.

There are times when you would notice content missing from the content library. To confirm that the content is missing from the content library, identify an affected package and track the package content from PkgLib to FileLib. Once you confirm that the required content for a Package is missing in the Content Library, see Resend compressed copy of a package to a site for information on how to re-populate the content.

In these cases, you can identify the content ID from the log and track the content from PkgLib to FileLib to ensure that the files exist. Can you please help me on this further?????

Thanks Amol Bhatt Reply. Thanks, Amol Reply. Hi Prajwal, Thanks for the troubleshooting Library. When i checked the log file dspooler. This is very critical for me. Very Informative.

Thank you Prajwal Reply. Thank you Sirisha. Hope this blog helped you.. Hello Prajwal, May be I am wrong but smsdbmon log not only limited for software updates.

Records activities that are related to the Mac client operations, including application management, inventory, and error logging. Records information that is related to client operations, including user sign in and sign out operations, and Mac computer activity.

Records activities that are related to Configuration Manager notifications displayed on the Mac computer. Records activities related to the Configuration Manager preferences dialog box on the Mac computer, which includes general status and error logging.

Records information about the progress of launching the secondary site installation process. Details of the actual setup process are contained in ConfigMgrSetup. Records information about the installation, use, and removal of a Windows service. Windows uses this service to test network connectivity and permissions between servers.

It uses the computer account of the server that creates the connection. Records details about the processing of XML files from the inbox for updating the Asset Intelligence catalog.

Records details about discovering software with an associated software identification tag. Also records activities related to hardware inventory. Records activities for authentication tokens, either from Azure Active Directory or site-issued client tokens. Site system server. Records activities related to client registration, such as validating certificates, CRL, and tokens. Records details about the conversion of XML. Records the registration of the management point with WINS.

Records the availability of the management point every 10 minutes. Records information about data synchronization between the site database and the data warehouse database. Records details about communications to the fallback status point from mobile device legacy clients and client computers.

Records details about when collections are created, changed, and deleted by the Collection Evaluator. Provides information about downloading, storing, and accessing assigned configuration baselines.

Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes. Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

The following sections provide details about the different log files available to you. Monitor Configuration Manager client and server logs for operation details, and view error information to troubleshoot problems. Compliance settings and company resource access. The following table lists the log files that contain information related to the installation of the Configuration Manager client.

The Configuration Manager client for Mac computers records information in the following log files on the Mac computer:. The following sections list log files that are on the site server or that are related to specific site system roles. The following table lists the log files that are on the Configuration Manager site server and site system servers.

The following table lists the log files that contain information related to the data warehouse service point. The following table lists the log files that contain information related to the fallback status point. The following table lists the log files that contain information related to the management point. The following table lists the log files that contain information related to the service connection point.

The following table lists the log files that contain information related to the software update point. The following table lists the log files that contain information related to application management. The following table lists the log files that contain information related to deploying packages and programs. The following table lists log files that contain information related to backup and recovery actions, including site resets, and changes to the SMS Provider.

The following table lists the Configuration Manager log files that contain information related to certificate enrollment. Along with the Configuration Manager log files, review the Windows Application logs in Event Viewer on the server running the Network Device Enrollment Service and the server hosting the certificate registration point.

For example, look for messages from the NetworkDeviceEnrollmentService source. The following table lists the log files that contain information related to the cloud management gateway. These are local Configuration Manager log files that cloud service manager syncs from Azure storage every five minutes. The cloud management gateway pushes logs to Azure storage every five minutes. So the maximum delay is 10 minutes. Verbose switches affect both local and remote logs.

The actual file names include the service name and role instance identifier. These log files are synced, so you don't need to RDP to the cloud management gateway to obtain them, and that option isn't supported. The following table lists the log files that contain information related to compliance settings and company resource access. The following table lists the log files that contain information related to the Configuration Manager console.

Use the following log files to help troubleshoot issues with Desktop Analytics integrated with Configuration Manager. The following table lists the log files that contain information related to processing inventory data. The following sections list the log files that contain information related to managing mobile devices.

The following table lists logs that contain information related to the mobile device legacy client. The following table lists the Configuration Manager log files that contain information related to reporting. The following table lists the log files that contain information related to managing role-based administration. For example, see CcmExec. The following table lists the log files that contain information related to Windows servicing.

Servicing uses the same infrastructure and process as software updates. For other logs applicable to the servicing scenario, see Software updates. The following table lists the log files that contain information related to the Windows Update Agent.

For more information, see Windows Update log files. Support Center OneTrace. Support Center log file viewer. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services.

Privacy policy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Is this page helpful? Yes No. Any additional feedback? Skip Submit. Submit and view feedback for This product This page. View all page feedback. Records Configuration Manager client status evaluation activities and details for components that are required by the Configuration Manager client. Records the Configuration Manager client status evaluation activities that are initiated by the evaluation scheduled task. This log file also includes information about enabling and disabling wake-up proxy.

Records activities related to the maintenance and capture of data related to client performance counters. This log is typically only used when you enable debug logging, or there's a problem with the component. The client health task ccmeval usually self-corrects problems with this component. Records information for Windows Hello for Business.

Records details about the process of remediation and compliance for compliance settings, software updates, and application management. Records changes in state for configuration items, such as compliance settings, software updates, and applications. Records information about configuration items, such as compliance settings, software updates, and applications. Records tasks for each application and deployment type, such as content download and install or uninstall actions.

Creates and maintains the client GUID and identifies tasks during client registration and assignment. Records information for client deployment state messages during auto-upgrade and client piloting. This tool checks whether computers have a public key infrastructure PKI client authentication certificate that can be used with Configuration Manager.

Records high-level information about the evaluation, conflict reporting, and remediation of configuration items and applications. Records information about reporting policy platform results into state messages for configuration items.

Records information about the download of express updates and updates downloaded using Delivery Optimization. Records information about the installation of the System Center Endpoint Protection client and the application of antimalware policy to that client.

Records details about enhanced detection methods that are used when verbose or debug logging is turned on. Records the history of Endpoint Protection malware detection and events related to client status. Records the activity of the Windows Management Instrumentation WMI provider for software inventory and file collection. Records the activity for state messages that are sent to the fallback status point by the client.

Records activities of hardware inventory, software inventory, and heartbeat discovery actions on the client.