| Previous | Next |
| ERROR_APPEXEC_INVALID_HOST_STATE | ERROR_APPEXEC_HOST_ID_MISMATCH |
ERROR_APPEXEC_NO_DONOR
No required resource donor was available.
ERROR_APPEXEC_NO_DONOR is Win32 error 3065 (0xBF9). AllStat describes a host operation that could not complete because a required resource donor was not found. “Donor” is owner-specific terminology; the code does not publicly define which process, package, state, or resource must supply it.
Why donor selection fails
- the expected donor process or host instance exited, restarted, or never registered
- identity, package, session, architecture, generation, or capability filters exclude all candidates
- a race consumes or invalidates the candidate between discovery and assignment
- policy or isolation prevents sharing the required resource with the target host
- client routing asks the wrong host pool or uses stale donor inventory
Selection evidence
Record the exact operation, target host ID/generation, donor requirement name, candidate count and rejection reasons, app/package/user/session and architecture, policy/capability results, resource availability, selection timestamps, and owner event logs. Do not expose private donor memory or tokens.
Diagnostic sequence
Use the owning component’s diagnostics to list eligible candidates and why each was rejected. Verify registration, liveness, generation, identity boundaries, and resource compatibility. A simple “process exists” check is insufficient if the donor must satisfy additional host policy.
Correlate candidate loss with restart, cleanup, update, or concurrent allocation. Refresh inventory from the authoritative broker rather than reusing a cached donor ID. Test whether starting or registering the documented prerequisite creates an eligible candidate.
Recovery and capacity planning
Restore or create an eligible donor through supported lifecycle operations, then rebuild the request against current host state. If donor absence is a valid capacity condition, queue or reject work explicitly instead of tight-loop retry.
Schedulers should track donor ownership and generation, reserve candidates atomically, expose rejection reasons, and release reservations on cancellation. Administrators should investigate repeated 3065 results as capacity, policy, registration, or host-stability problems.
Difference from invalid host state
ERROR_APPEXEC_INVALID_HOST_STATE says the target host itself cannot accept the request. Error 3065 identifies the missing external or peer resource donor required for that host operation.
Example
An execution broker tries to prepare a host after the only eligible donor process restarted. The cached donor ID yields 3065. Refreshing registration and selecting the new donor generation allows the request to proceed.
References
Looking for a different code? Search another status or error code.