Windows / Code / 0xb000020b
0xb000020b
Decimal: 2952790539 · Signed: -1342176757
As HRESULT:- S: 1 (Failure)
- C: 1 (Customer-defined)
- N: 1 (Wraps an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x020b (523)
As NTSTATUS:- Sev: 2 (STATUS_SEVERITY_WARNING)
- C: 1 (Customer-defined)
- N: 1 (Reserved, must be clear in a well-formed NTSTATUS)
- Facility: 0x000 (Default)
- Code: 0x020b (523)
Associated Modules
| Module | Found in | Description |
|---|
| ActiveSyncProvider.dll | 1011 | PeopleSync: Ignoring server response with invalid type (command: %1, status: %2, server id: %3, client id: %4) |
| AppXDeploymentServer.dll | 11 | error %2: Failed to open package manifest file %1 due to reason %3. |
| MFCore.dll | 1011 | AudCaptureStream_Pump_Stop_Enter |
| Microsoft-Windows-AppModelExecEvents.dll | 1011 | BM: ActivateDeferredWorkItem discarded WorkItem: %1 because of Status: %2 |
| SyncController.dll | 1011 | Finished GalSearchWork for account %1. |
| dmpushroutercore.dll | 1011 | DmWapPushService: Service handler invoked. Opcode: (%1), Current state: (%2). |
| ptpprov.dll | 11 | The timestamp settings on the NICs in this system are ambiguous, with a combination of different kinds of timestamping enabled. The resulting timestamps may not be translated correctly, resulting in sub-optimal time sync accuracy. There could also be path asymmetry due to the use of different kinds of timestamp types on different NICs in the system. For best results, enable a single kind of timestamping on all NICs in the system.
Current Tick Count:%1
For more information, see https://go.microsoft.com/fwlink/?linkid=873491. |
| 7 entries |
Associated Headers