| Previous | Next |
| PLA_E_NETWORK_EXE_NOT_VALID | PLA_E_EXE_PATH_NOT_VALID |
PLA_E_EXE_ALREADY_CONFIGURED
An executable should have one coherent API tracing definition
PLA_E_EXE_ALREADY_CONFIGURED indicates that PLA found another API tracing configuration for the same executable path. Duplicating the target could create overlapping instrumentation, ambiguous filters, and competing output ownership.
Enumerate existing Data Collector Sets and API tracing collectors, then compare canonical executable paths rather than display names. Update the established collector when the intent is to change API or module filters. If separate scenarios are required, run them sequentially or use clearly isolated definitions after removing the existing registration.
Existing configuration to locate
- Canonical ExePath stored in each API collector.
- Owning Data Collector Set and namespace.
- IncludeApis, ExcludeApis, and module restrictions.
- Whether an earlier deployment left a stale definition.
References
- IApiTracingDataCollector
- IDataCollectorSet::Query lookup semantics
- IDataCollectorCollection and collector creation
Looking for a different code? Search another status or error code.