| Previous | Next |
| PLA_E_DC_ALREADY_EXISTS | PLA_E_DC_START_WAIT_TIMEOUT |
PLA_E_DCS_START_WAIT_TIMEOUT
A start timeout does not prove that every collector failed
PLA_E_DCS_START_WAIT_TIMEOUT means the caller waited for the Data Collector Set to reach its started state and the notification window expired. Startup may still be blocked on credentials, provider activation, output creation, or a child collector that has not reported readiness.
Query the set status after the timeout instead of immediately starting it again. Inspect the PLA operational channel, child collector errors, ETW session state, and output folder creation. A second start can turn a slow startup into an in-use conflict, so distinguish delayed completion from rollback before retrying.
Timeout evidence to gather
- Elapsed wait interval and final set status.
- Per-collector start results and timestamps.
- PLA Operational events around the request.
- ETW sessions or files created despite the timeout.
References
Looking for a different code? Search another status or error code.