BÄREN-Wiki · öffentliche Vorschau

Windows, Fehlercodes und Gerätewissen

Öffentlich sichtbar sind Fehlerquelle und Grundeinstufung. Vollständige Diagnosen, Hersteller- und Praxishinweise sowie Reparaturroutinen erhalten ausschließlich angemeldete Bären-EDV-Techniker.

Windows, Fehlercodes und Gerätewissen

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 120: DavSyncProvider: Purged local collection (id: %1).

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 125: DavSyncProvider: Local collection deleted because it no longer exists on the server (collection id: %1).

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 128: DavSyncProvider: The property status %1 returned for a null property is invalid and was coreced to 404.

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 129: DavSyncProvider: Received a non-successful ctag property response (collection id: %1, status %2).

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 132: DavSyncProvider: Deleted successfuly uploaded item because it has the same Uri as a previously downloaded item (item id: %1).

Microsoft-Windows-MCCS-DavSyncProvider · Ereignis 133: DavSyncProvider: Failed to upload change (item id: %1, retry: %2).

Microsoft-Windows-MCCS-EngineShared · Ereignis 2: Error Propagated: HRESULT: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-InternetMail · Ereignis 2: Error Propagated: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-InternetMail · Ereignis 102: Error selecting folder: %1, Server response = %2

Microsoft-Windows-MCCS-InternetMail · Ereignis 103: %1 authentication failed with mechanism %2

Microsoft-Windows-MCCS-InternetMail · Ereignis 311: InternetMail: Cancelling existing socket communication

Microsoft-Windows-MCCS-InternetMail · Ereignis 461: IMAP Failed to fetch message with UID %1

Microsoft-Windows-MCCS-InternetMail · Ereignis 470: IMAP hdr fetch overflowed batch queue - catching up: acct=%1 max=%2 bytes=%3

Microsoft-Windows-MCCS-InternetMailCsp · Ereignis 2: Error Propagated: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 2: Error Propagated: HRESULT: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 101: NetworkHelper::HttpTransport: Callback error: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 102: NetworkHelper::HttpTransport: Request Failure: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 103: NetworkHelper::HttpTransport: Wait Failed on Closing Handle: %1 Wait: %2 Error: %3

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 104: NetworkHelper::HttpTransport: Set Active error: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 105: NetworkHelper::HttpTransport: Set Dormand error: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 106: NetworkHelper::HttpTransport: Set completion event error: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 107: NetworkHelper::HttpTransport: Wait on async request error: Handle: %1 Wait: %2 Error: %3

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 109: NetworkHelper::HttpTransport: Http Status error: Handle: %1 Error: %2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 110: NetworkHelper::HttpTransport: CmSetRequirement(%1) Failure: Handle: %2 Error: %3

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 201: Set PDC Active:%1, invalid CCT state:%2

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 205: CCT failed, possibly because of VPN.

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 207: Invalid CCT state: %1

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 208: CCT failed, number of AOAC connection limitation reached.

Microsoft-Windows-MCCS-NetworkHelper · Ereignis 209: PDC not renewed due to lack of progress, allowing low power state. ActivationHandle: %1

Microsoft-Windows-MCCS-SyncController · Ereignis 2: Error Propagated: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-SyncController · Ereignis 102: SyncController:[Consistency] [%1] Registry key for this partner is being deleted because it's invalid.

Microsoft-Windows-MCCS-SyncController · Ereignis 103: SyncController:[Consistency] Default Store is invalid, but will not be deleted. There were '%1' stores found.

Microsoft-Windows-MCCS-SyncController · Ereignis 104: SyncController:[Consistency] [%1:%2:%3] Store being deleted because it's invalid. There were '%4' stores found.

Microsoft-Windows-MCCS-SyncController · Ereignis 105: SyncController:[Consistency] [%1] Registry key for this partner is invalid, the reason is '%2'.

Microsoft-Windows-MCCS-SyncController · Ereignis 106: SyncController:[Consistency] [%1:%2:%3] Store is invalid, the reason is '%4'.

Microsoft-Windows-MCCS-SyncController · Ereignis 196: Notified golden account existence: %1.

Microsoft-Windows-MCCS-SyncController · Ereignis 545: Delete Account %1: Unknown Store Type %2.

Microsoft-Windows-MCCS-SyncController · Ereignis 552: Ignoring account %1 because its version (%2) doesn't match the current version (%3).

Microsoft-Windows-MCCS-SyncController · Ereignis 555: Account %1 setting schedule trigger requirement %2.

Microsoft-Windows-MCCS-SyncController · Ereignis 556: Account %1 exiting delay and resetting successive empty sync count to zero.

Microsoft-Windows-MCCS-SyncUtil · Ereignis 2: Error Propagated: %1 Location: %2 Line Number: %3

Microsoft-Windows-MCCS-SyncUtil · Ereignis 202: SyncUtil: MXSML Error code=%1

Microsoft-Windows-MCCS-SyncUtil · Ereignis 203: SyncUtil: MXSML Error reason=%1

Microsoft-Windows-MCCS-SyncUtil · Ereignis 204: SyncUtil: MXSML Error url=%1

Microsoft-Windows-MCCS-SyncUtil · Ereignis 205: SyncUtil: MXSML Error srcText=%1

Microsoft-Windows-MCCS-SyncUtil · Ereignis 206: SyncUtil: MXSML Error offset=%1

Microsoft-Windows-MediaFoundation-Platform · Ereignis 1: Attempt to use MFT clsid %1 marked as do not use.

Microsoft-Windows-MediaFoundation-Platform · Ereignis 2: Attempt to use Media Source clsid %1 marked as do not use.