| Previous | Next |
| UI_E_TIME_BEFORE_LAST_UPDATE | UI_E_INVALID_DIMENSION |
UI_E_TIMER_CLIENT_ALREADY_CONNECTED
The scope of UI_E_TIMER_CLIENT_ALREADY_CONNECTED is Windows Animation Manager: a timer client attempted a second connection without disconnecting the first. Preserve 0x802A010A beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the boundary first
When it is returned, Windows Animation is a stateful COM subsystem. During a this result investigation, animation variables, transitions and storyboards are created under a manager, scheduled against a monotonic animation time, updated before drawing, and eventually sealed or released. A visible glitch can therefore be downstream of a lifecycle, ownership, timeline, callback, or numeric contract failure.
During a this result investigation, the animation timer maintains a client relationship and callback routing. Duplicate registration often signals repeated initialization or cleanup that failed to remove the previous handler.
The first owner to inspect is the animation manager, storyboard, transition, timer, or callback that returned the HRESULT.
Keep neighboring conditions separate
When it is returned, UI_E_DIFFERENT_OWNER is object-domain mismatch; this code is duplicate timer-client registration.
Do not create more timers merely to bypass a leaked client registration.
Incident record for this HRESULT
| Capture | Diagnostic value |
|---|---|
| Timer and client identities for it. | This provides a stable comparison across retries or another machine and helps test the Windows Animation Manager boundary. |
| First connection result for it. | This identifies the exact object or resource generation involved and helps test the Windows Animation Manager boundary. |
| Second initialization path for it. | This places the failure on the lifecycle or transaction timeline and helps test the Windows Animation Manager boundary. |
| Disconnect or release history for it. | This separates caller input from environment and service state and helps test the Windows Animation Manager boundary. |
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: Make connection ownership single and explicit.
- Next: Disconnect before replacing a client.
- Then: Guard initialization with a lifecycle state.
- Finally: Test reopen after complete teardown.
Three useful controls
- Fresh storyboard or animation object: for it, a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: for it, keep the timeline, transitions, and manager version fixed.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: for it, retain timer and client identities and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: make connection ownership single and explicit. Hold constant: for it, keep the original this result sample available for the final regression test.
Definition of done
Closure for it requires one client is connected per timer generation and reconnect succeeds after verified disconnection; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
- Microsoft: Windows Animation error codes
- Microsoft: IUIAnimationTimer interface
- Microsoft: Windows Animation overview
- Microsoft: Schedule a storyboard
Looking for a different code? Search another status or error code.