Automated Application Management for Microsoft Endpoint Manager

Simplify third-party application management

Knowledge Base ArticlesRequest Trial

Collecting Log Files for Patch My PC Support

enable verbose logging for third-party updates in microsoft sccmIn this article, we will review the logs files required to allow our support team to analyze and troubleshoot different scenario’s. Please review the different scenarios below.

When sending the logs files, please attach the logs as a ZIP file using our technical support form.

Server-Side Logs

Publisher - Enable Debug Logging

Enabling Debug logging is often helpful for troubleshooting unique issues with publishing. Follow the steps below to enable Debug logging:

 

  1. Open the Publisher
  2. Click on the General tab
  3. In the dropdown under Logging Options select Debug

  4. Close the Publisher
  5. Open Services.msc and locate the PatchMyPCService
  6. Right click and Restart the PatchMyPCService
  7. Debug Logging is now enabled
Software Updates - Automatic Deployment Rule Failing for Third-Party Updates

When troubleshooting automatic deployment rules failing for third-party updates, we will need the following server-side logs. In this example, we will assume the main SCCM installation directory is: C:\Program Files\Microsoft Configuration Manager

  • C:\Program Files\Microsoft Configuration Manager\Logs\ruleengine*.log
  • C:\Program Files\Microsoft Configuration Manager\Logs\PatchDownloader*.log (If exist)
  • C:\Program Files\SMS_CCM\Logs\PatchDownloader*.log (If exist)
Software Updates - Failing to Publish Updates Using Patch My PC's Publisher

When using the Patch My PC Publishing Service, we will need the following log files from the SUP/WSUS server where the service is installed.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log
Software Updates - Failing to Publish Updates Using SCCM In-Console Publishing

When using the SCCM in-console publishing, we will need the following log files from the SUP/WSUS server where the service is installed.

  • %SiteSystemLogsFolder%\SMS_ISVUPDATES_SYNCAGENT*.log
  • %ProgramFiles%\Update Services\LogFiles\SoftwareDistribution.log
  • %SiteServerLogsFolder%\wsyncmgr*.log
  • %SiteServerLogsFolder%\WCM*.log
Software Updates - Failing to Download Updates to Deployment Package using SCCM Console

When troubleshooting updates failing to download into a deployment package from the SCCM console, we will need the following log from the machine running the SCCM console:

  • %temp%\PatchDownloader*.log
    • Note: if you are using an RDP session the patchdownloader.log may be in a numbered sub-folder in your users %temp% folder.
SCCM Applications - Failing to Create or Update SCCM Applications Using Patch My PC's Publisher

When using the Patch My PC Publishing Service, we will need the following log files to troubleshoot applications failing to create.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv
  • %SCCMInstallFolder%\Logs\SMSProv*.log
Intune Applications - Fails to Create/Update Applications Using Patch My PC's Publisher

When using the Patch My PC Publishing Service, we will need the following log files to troubleshoot applications failing to create.

  • %PatchMyPCInstallDirectory%\PatchMyPC.log
  • %PatchMyPCInstallDirectory%\Settings.xml
  • %PatchMyPCInstallDirectory%\PatchMyPC-DownloadHistory.csv

Client-Side Logs

Intune Applications - Failing to Install/Detect on Client Devices

When troubleshooting application installation errors on a client, we will need multiple client logs. Please include the following logs:

  • %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-ScriptRunner.log
  • %ProgramData%\PatchMyPCIntuneLogs\PatchMyPC-SoftwareDetectionScript.log
  • %ProgramData%\Microsoft\IntuneManagementExtension\Logs\AgentExecutor.log
  • %ProgramData%\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.log
SCCM Applications - Failing to Install/Detect on Client Devices

When troubleshooting application installation errors on a client, we will need multiple client logs. Please include the following logs:

  • %WinDir%\CCM\Logs\AppDiscovery*.log
  • %WinDir%\CCM\Logs\AppEnforce*.log
  • %WinDir%\CCM\Logs\AppIntentEval*.log
  • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log
  • %WinDir%\CCM\Logs\PatchMyPC-SoftwareDetectionScript.log
Software Updates - Failing to Install on Client Devices

When troubleshooting update installation errors on a client, we will need the following client logs:

  • %WinDir%\CCM\Logs\ScanAgent*.log
  • %WinDir%\CCM\Logs\UpdatesDeployment*.log
  • %WinDir%\CCM\Logs\UpdatesStore*.log
  • %WinDir%\CCM\Logs\WUAHandler*.log
  • %WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
  • %WinDir%\WindowsUpdate.log