| Previous | Next |
| PLA_E_DCS_NOT_RUNNING | PLA_E_NETWORK_EXE_NOT_VALID |
PLA_E_CONFLICT_INCL_EXCL_API
API tracing filters must resolve each function to one unambiguous decision
PLA_E_CONFLICT_INCL_EXCL_API is specific to IApiTracingDataCollector. A function selected in both IncludeApis and ExcludeApis has contradictory filter semantics, so PLA rejects the collector rather than relying on list order.
Normalize module and function names before comparing the lists, including aliases introduced by configuration generation. Decide whether the include list is an allowlist narrowed by modules or whether the exclusion list removes noisy calls from the default set. Keeping both lists minimal also reduces tracing overhead and avoids collecting sensitive or irrelevant API activity.
Filter data to compare
- Normalized function names in both SAFEARRAY values.
- Included module list and default traced modules.
- Template expansions that add APIs more than once.
- Whether the intended policy is allowlist or denylist based.
References
- IApiTracingDataCollector
- IApiTracingDataCollector::ExcludeApis
- IApiTracingDataCollector::IncludeModules
Looking for a different code? Search another status or error code.