Log flags to set when troubleshooting deployment issues
Last updated: September 17th, 2025Description
- Author: Dan Hojecki
- Published: September 17th, 2025
Details:
On the GR node:
| Component | Log Flags |
| aaBootstrap | BootstrapRegister, CPlatformMapping |
| aaDCOMTransport | Trace |
| DComInterfaceAccess | Trace, BootstrapTrace |
| PlatformCategory | Trace, PlatformCategory |
| WWPackageServer | MultiThreadedDeploy, DeployProgress, LogAllFailures |
| WWPackageManager | Trace, LogAllFailures |
| FileCopyService | Trace |
| aaPIM | PimTraceOn |
On the remote node:
| Component | Log Flags |
| aaBootstrap | BootstrapRegister, PlatformMapping, FileVersion |
| aaDCOMTransport | Trace |
| aaPIM | PimTraceOn, PimTraceWarnErrorOn, FileRefCount, MsiDiagnostics |
| DComInterfaceAccess | BootstrapTrace, Trace |
| FileCopyService | Trace |
Give feedback about this article
Recommended articles
[ISS Support Case] Platform Deployment Failure
Client reached out as when user was attempting to deploy WinPlatform user was receiving the following error: "Cannot find the target PC on the network OR target PC can not communicate back to the Galaxy Repository using the NIC that is top in the binding order."
Read More[ISS Support Case] Platform deployment failure
Failed to deploy failed to find target platform aa bootstrap register platform failed.
Read More[ISS Support Case] Deployment Failure
Client reached out because after making configuration changes to multiple objects she had pending changes on objects in Galaxy. When trying to deploy the objects user was receiving engine communication failure message. This is a single node environment.
Read More