Microsoft-Windows-UserDataAccess-UserDataService

166 events across 1 channel

Event ID	Title	Channel
1	Error: %1 Location: %2 Line Number: %3.	Operational
2	Error Propagated: %1 Location: %2 Line Number: %3.	Operational
3		Operational
101	Handle %2 running down (path %1) - client crash?	Operational
102	Opened data session object %1.	Operational
103	Closing data session object %1.	Operational
104	CanAppAccessStore: pAppOwnershipId->productId = %1, …	Operational
105	CanAppAccessStore: Can access store = %1.	Operational
106	Cannot convert blob to string for msg [.	Operational
107	UDM Data migrated with status: [.	Operational
108	Call favorites data migrated with status: [.	Operational
201	Handle %1 updated controls to max:%2.	Operational
202	Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5).	Operational
203	Handle %1 has %2 ready notifications, (lost %3).	Operational
204	Handle %1: new notification type [%2], id [%3].	Operational
205	Id [.	Operational
206	Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5).	Operational
301	Caller %1 asked to update missing object type:%2 id:%3.	Operational
302	Caller %1 asked to delete missing object type:%2 id:%3.	Operational
303	Caller %1 looked for properties on missing object type:%2 id:%3.	Operational
304	Deleting ENUM object %1 in rundown.	Operational
305	Deleting SESSION object %1 in rundown.	Operational
306	Client does not have the following capbility [.	Operational
307	Client does not have the following privacy capability [.	Operational
308	Client privacy capability failed allowedCallers = [.	Operational
400	CalendarEventSink %1: Advise to Poom.	Operational
401	CalendarEventSink %1: Unadvise from Poom.	Operational
402	CalendarSearch: %1 items returned.	Operational
403	Remote id not found: store=.	Operational
404	Appointment cache skipped because of missing prop.	Operational
405	CalendarSearch: %1 recurring appts found.	Operational
406	CalendarSearch: inserted item %1, type %2.	Operational
407	Appointment Cache notified: invalidate calendars [.	Operational
501	Modifying Feed of Type %1 for OLITEMID: %2 %3 %4.	Operational
502	Invalid Timestamp for Feed Item.	Operational
503	Feed for contact %1 as a part of operation %2 did not provide enough items.	Operational
504	The following deep link is invalid.	Operational
505	The following image url is too long.	Operational
602	Invalid Pending Upload Request Indentifier Format Encountered	Operational
700	ChatStoreChangedEventSink %1: Advise to Messaging OM.	Operational
701	ChatStoreChangedEventSink %1: Unadvise from Messaging OM.	Operational
702	ChatStoreChanged event: event type [.	Operational
705	Activation status change notification received for Capability Service.	Operational
706	Unknown activation status for Capability Service.	Operational
707	Request Capabilities.	Operational
708	Capabilities retrieved: %1, capabilities are %2.	Operational
709	Notifying messaging app: PFN = {AppPackageFamilyName}; actions = …	Operational
711	ComposingStatusChangedEventSink %1: Advise to RCS.	Operational
712	ComposingStatusChangedEventSink %1: Unadvise from RCS.	Operational
713	ComposingStatusChanged event: source [RCS], chat id [.	Operational
714	RcsEndUserMessageEventSink %1: Advise to End User Messages.	Operational
715	RcsEndUserMessageEventSink %1: Unadvise from End User Messages.	Operational
716	RcsServiceStatusChangedEventSink %1: Advise to RCS.	Operational
717	RcsServiceStatusChangedEventSink %1: Unadvise from RCS.	Operational
718	RcsServiceStatusChanged event: service type [.	Operational
719	Default messaging app fall back to.	Operational
720	Rcs service initialization started	Operational
721	Rcs service is not available	Operational
722	Rcs service adapter initialized	Operational
723	Rcs service adapter released	Operational
724	Rcs service adapter lost connection	Operational
725	Chat: ChatOperationContextGetMessageProperties	Operational
726	Chat: ChatOperationContextGetMessageParticipants	Operational
727	Chat: ChatOperationContextGetMessageAttachments	Operational
728	Chat: ChatOperationContext_MarkAsSeen	Operational
729	Chat: GetChatMessageProperties	Operational
730	Chat: UdmSvcImpl_GetChatObjectProperties	Operational
731	Chat: ProcessChatUpdatesBegin	Operational
732	Chat: ProcessChatUpdatesEnd	Operational
733	Chat: UdmSvcImpl_UpdateChatObjects	Operational
734	Notifying filter app: PFN = {AppPackageFamilyName}.	Operational
735	Conversation does not exist.	Operational
736	One or more conversation properties were not found.	Operational
737	Got a ChatMessage without recipients.	Operational
738	ChatCapabilitiesContext::GetCachedChatCapabilities()	Operational
739	ChatCapabilitiesContext::GetCachedChatCapabilities() - Contact not found	Operational
740	ChatCapabilitiesContext::GetCachedChatCapabilities() - Found a cached contact	Operational
741	ChatCapabilitiesContext::GetCachedChatCapabilities() - capabilities = %1.	Operational
742	ChatCapabilitiesContext::GetCapabilitiesFromNetwork()	Operational
743	ChatCapabilitiesContext::_RequestCapabilities()	Operational
744	Conversation does not exist.	Operational
745	Got app manager instance.	Operational
746	Got default messaging application.	Operational
747	Got messaging app package family name.	Operational
748	Got transport IDs.	Operational
749	Got one default transport ID.	Operational
750	Got one default transport ID.	Operational
751	Flattened items to send.	Operational
752	ChatCapabilitiesContext::_FindCachedPhoneNumberCapabilities found = [.	Operational
753	RcsMultipartMessageTracker::_OnChatOpenedWorker()	Operational
754	ChatAppManager::GetDefaultMessagingApp found default messaging app in registery.	Operational
755	ChatAppManager::GetDefaultMessagingApp ChatAppManager::GetAllMessagingApps() …	Operational
756	ChatAppManager::_GetDefaultMessagingAppInRegistry default app not found in …	Operational
757	ChatAppManager::SetDefaultMessagingAppInRegistry().	Operational
758	ChatAppManager::SetDefaultMessagingApp app already registered.	Operational
759	ChatAppManager::_SetDefaultMessagingAppInRegistry().	Operational
760	ChatAppManager::GetAllDefaultCapableMessagingApps().	Operational
761	Rcs service status adapter not available	Operational
762	RcsTransportChangedEventSink %1: Advise to RCS.	Operational
763	RcsTransportChangedEventSink %1: Unadvise from RCS.	Operational
764	RcsTransportChanged event	Operational
800	CallHistoryNotificationManager NotifyCallHistoryApps.	Operational
1000		Operational
1001		Operational
1002		Operational
1003		Operational
1004		Operational
1005		Operational
1100		Operational
1101		Operational
1104		Operational
1105		Operational
1106		Operational
1107		Operational
1108		Operational
1109		Operational
1110		Operational
1111		Operational
1112		Operational
1113		Operational
1114		Operational
1115		Operational
1116		Operational
1117		Operational
1118		Operational
1119		Operational
1120		Operational
1121		Operational
1122		Operational
1123		Operational
1124		Operational
1125		Operational
1126		Operational
1127		Operational
1128		Operational
1129		Operational
1200		Operational
1201		Operational
1202		Operational
1203		Operational
1204	App: %1, Action: %2.	Operational
1205	App: %1, Action: %2.	Operational
1206		Operational
1207		Operational
1208		Operational
1209		Operational
1210		Operational
1211		Operational
1212		Operational
1213		Operational
1214		Operational
1215		Operational
1216		Operational
1217		Operational
1218		Operational
1219		Operational
1220		Operational
1221		Operational
2001	Cleaning up stale data.	Operational
2002	Starting the knowledge defragmentation task for all sync partners	Operational
2003	Finished the knowledge defragmentation task.	Operational
2004	Starting the knowledge defragmentation task for all sync partners associated …	Operational
2005	Finished the knowledge defragmentation task for all sync partners associated …	Operational
2006	App Store Deleted: App Id [.	Operational
2007	App Store Grouping Deleted: App Id [.	Operational
2008	HandlePackageUninstall called for PFN.	Operational

Event ID 1 — Error: %1 Location: %2 Line Number: %3.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Error: %1 Location: %2 Line Number: %3

Fields

Name	Description
`P1_HResult`	—
`P2_String`	—
`P3_UInt32`	—

Event ID 2 — Error Propagated: %1 Location: %2 Line Number: %3.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Error Propagated: %1 Location: %2 Line Number: %3

Fields

Name	Description
`P1_HResult`	—
`P2_String`	—
`P3_UInt32`	—

Event ID 3 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Fields

Name	Description
`Message`	—

Event ID 101 — Handle %2 running down (path %1) - client crash?

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %2 running down (path %1) - client crash?

Fields

Name	Description
`path`	—
`handle`	—

Event ID 102 — Opened data session object %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Opened data session object %1

Fields

Name	Description
`handle`	—

Event ID 103 — Closing data session object %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Closing data session object %1

Fields

Name	Description
`handle`	—

Event ID 104 — CanAppAccessStore: pAppOwnershipId->productId = %1, pStoreAppOwnershipId->productId = %2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CanAppAccessStore: pAppOwnershipId->productId = %1, pStoreAppOwnershipId->productId = %2

Fields

Name	Description
`AppOwnershipId`	—
`StoreAppOwnershipId`	—

Event ID 105 — CanAppAccessStore: Can access store = %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CanAppAccessStore: Can access store = %1

Fields

Name	Description
`Prop_Boolean_1`	—

Event ID 106 — Cannot convert blob to string for msg [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Cannot convert blob to string for msg [%1], prop [%2]: size actual [%3] vs. expected [%4]

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—
`Prop_UInt_4`	—

Event ID 107 — UDM Data migrated with status: [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

UDM Data migrated with status: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 108 — Call favorites data migrated with status: [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Call favorites data migrated with status: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 201 — Handle %1 updated controls to max:%2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %1 updated controls to max:%2

Fields

Name	Description
`handle`	—
`maxnotify`	—

Event ID 202 — Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5).

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5)

Fields

Name	Description
`handle`	—
`requested`	—
`returned`	—
`remaining`	—
`missed`	—

Event ID 203 — Handle %1 has %2 ready notifications, (lost %3).

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %1 has %2 ready notifications, (lost %3)

Fields

Name	Description
`handle`	—
`readyCount`	—
`lost`	—

Event ID 204 — Handle %1: new notification type [%2], id [%3].

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %1: new notification type [%2], id [%3]

Fields

Name	Description
`handle`	—
`type`	—
`id`	—

Event ID 205 — Id [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Id [%1], StartTime [%2]

Fields

Name	Description
`id`	—
`starttime`	—

Event ID 206 — Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5).

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Handle %1 requested %2 messages, got %3, %4 remain (also said lost %5)

Fields

Name	Description
`handle`	—
`requested`	—
`returned`	—
`remaining`	—
`missed`	—

Event ID 301 — Caller %1 asked to update missing object type:%2 id:%3.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Caller %1 asked to update missing object type:%2 id:%3

Fields

Name	Description
`handle`	—
`type`	—
`id`	—

Event ID 302 — Caller %1 asked to delete missing object type:%2 id:%3.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Caller %1 asked to delete missing object type:%2 id:%3

Fields

Name	Description
`handle`	—
`type`	—
`id`	—

Event ID 303 — Caller %1 looked for properties on missing object type:%2 id:%3.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Caller %1 looked for properties on missing object type:%2 id:%3

Fields

Name	Description
`handle`	—
`type`	—
`id`	—

Event ID 304 — Deleting ENUM object %1 in rundown.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Deleting ENUM object %1 in rundown

Fields

Name	Description
`handle`	—

Event ID 305 — Deleting SESSION object %1 in rundown.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Deleting SESSION object %1 in rundown

Fields

Name	Description
`handle`	—

Event ID 306 — Client does not have the following capbility [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Client does not have the following capbility [{Prop_Type}]

Fields

Name	Description
`Prop_Type`	—

Event ID 307 — Client does not have the following privacy capability [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Client does not have the following privacy capability [{Prop_Type}]

Fields

Name	Description
`Prop_Type`	—

Event ID 308 — Client privacy capability failed allowedCallers = [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Client privacy capability failed allowedCallers = [%1],  m_clientAPISecurityFlags = [%2],  m_clientAPISecurityFlagsForPrivacy = [%3]

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—

Event ID 400 — CalendarEventSink %1: Advise to Poom.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CalendarEventSink %1: Advise to Poom

Fields

Name	Description
`handle`	—

Event ID 401 — CalendarEventSink %1: Unadvise from Poom.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CalendarEventSink %1: Unadvise from Poom

Fields

Name	Description
`handle`	—

Event ID 402 — CalendarSearch: %1 items returned.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CalendarSearch: %1 items returned. index = %2, future items = %3, past items = %4

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—
`Prop_UInt_4`	—

Event ID 403 — Remote id not found: store=.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Remote id not found: store=%1, found=%2

Fields

Name	Description
`Prop_ULong`	—
`Prop_UInt`	—

Event ID 404 — Appointment cache skipped because of missing prop.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Appointment cache skipped because of missing prop: %1

Fields

Name	Description
`Prop_ULong`	—

Event ID 405 — CalendarSearch: %1 recurring appts found.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CalendarSearch: %1 recurring appts found. future items = %2, past items = %3

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—

Event ID 406 — CalendarSearch: inserted item %1, type %2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CalendarSearch: inserted item %1, type %2

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—

Event ID 407 — Appointment Cache notified: invalidate calendars [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Appointment Cache notified: invalidate calendars [%1], invalidate cache [%2]

Fields

Name	Description
`Prop_Boolean_1`	—
`Prop_Boolean_2`	—

Event ID 501 — Modifying Feed of Type %1 for OLITEMID: %2 %3 %4.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Modifying Feed of Type %1 for OLITEMID: %2 %3 %4

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—
`Prop_UInt_4`	—

Event ID 502 — Invalid Timestamp for Feed Item.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Invalid Timestamp for Feed Item: %1

Fields

Name	Description
`remoteId`	—

Event ID 503 — Feed for contact %1 as a part of operation %2 did not provide enough items.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Feed for contact %1 as a part of operation %2 did not provide enough items. %3 were requested and %4 were provided with %5 qualifying. Marking as failed.

Fields

Name	Description
`remoteId`	—
`operationId`	—
`requestAmnt`	—
`providedAmnt`	—
`qualifyingAmnt`	—

Event ID 504 — The following deep link is invalid.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

The following deep link is invalid: %1

Fields

Name	Description
`deepLink`	—

Event ID 505 — The following image url is too long.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

The following image url is too long: %1

Fields

Name	Description
`deepLink`	—

Event ID 602 — Invalid Pending Upload Request Indentifier Format Encountered

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Invalid Pending Upload Request Indentifier Format Encountered

Event ID 700 — ChatStoreChangedEventSink %1: Advise to Messaging OM.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatStoreChangedEventSink %1: Advise to Messaging OM

Fields

Name	Description
`handle`	—

Event ID 701 — ChatStoreChangedEventSink %1: Unadvise from Messaging OM.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatStoreChangedEventSink %1: Unadvise from Messaging OM

Fields

Name	Description
`handle`	—

Event ID 702 — ChatStoreChanged event: event type [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatStoreChanged event: event type [%1], item type [%2]

Fields

Name	Description
`EventType`	—
`ItemType`	—

Event ID 705 — Activation status change notification received for Capability Service.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Activation status change notification received for Capability Service. New status: %1

Fields

Name	Description
`ActivationStatus`	—

Event ID 706 — Unknown activation status for Capability Service.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Unknown activation status for Capability Service: %1

Fields

Name	Description
`ActivationStatus`	—

Event ID 707 — Request Capabilities.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Request Capabilities: %1

Fields

Name	Description
`TelString`	—

Event ID 708 — Capabilities retrieved: %1, capabilities are %2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Capabilities retrieved:  %1, capabilities are %2

Fields

Name	Description
`TelString`	—
`RcsCapabilityBits`	—

Event ID 709 — Notifying messaging app: PFN = {AppPackageFamilyName}; actions = {NotificationActions}.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Notifying messaging app: PFN = {AppPackageFamilyName}; actions = {NotificationActions}

Fields

Name	Description
`AppPackageFamilyName`	—
`NotificationActions`	—

Event ID 711 — ComposingStatusChangedEventSink %1: Advise to RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ComposingStatusChangedEventSink %1: Advise to RCS

Fields

Name	Description
`handle`	—

Event ID 712 — ComposingStatusChangedEventSink %1: Unadvise from RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ComposingStatusChangedEventSink %1: Unadvise from RCS

Fields

Name	Description
`handle`	—

Event ID 713 — ComposingStatusChanged event: source [RCS], chat id [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ComposingStatusChanged event: source [RCS], chat id [%1], is group [%2], teluri [%3], is composing [%4]

Fields

Name	Description
`RcsChatId`	—
`isGroup`	—
`TelString`	—
`isComposing`	—

Event ID 714 — RcsEndUserMessageEventSink %1: Advise to End User Messages.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsEndUserMessageEventSink %1: Advise to End User Messages

Fields

Name	Description
`handle`	—

Event ID 715 — RcsEndUserMessageEventSink %1: Unadvise from End User Messages.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsEndUserMessageEventSink %1: Unadvise from End User Messages

Fields

Name	Description
`handle`	—

Event ID 716 — RcsServiceStatusChangedEventSink %1: Advise to RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsServiceStatusChangedEventSink %1: Advise to RCS

Fields

Name	Description
`handle`	—

Event ID 717 — RcsServiceStatusChangedEventSink %1: Unadvise from RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsServiceStatusChangedEventSink %1: Unadvise from RCS

Fields

Name	Description
`handle`	—

Event ID 718 — RcsServiceStatusChanged event: service type [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsServiceStatusChanged event: service type [%1], is supported [%2]

Fields

Name	Description
`serviceType`	—
`isSupported`	—

Event ID 719 — Default messaging app fall back to.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Default messaging app fall back to: %1

Fields

Name	Description
`AppPackageFamilyName`	—

Event ID 720 — Rcs service initialization started

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service initialization started

Event ID 721 — Rcs service is not available

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service is not available

Event ID 722 — Rcs service adapter initialized

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service adapter initialized

Event ID 723 — Rcs service adapter released

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service adapter released

Event ID 724 — Rcs service adapter lost connection

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service adapter lost connection

Event ID 725 — Chat: ChatOperationContextGetMessageProperties

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ChatOperationContextGetMessageProperties

Event ID 726 — Chat: ChatOperationContextGetMessageParticipants

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ChatOperationContextGetMessageParticipants

Event ID 727 — Chat: ChatOperationContextGetMessageAttachments

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ChatOperationContextGetMessageAttachments

Event ID 728 — Chat: ChatOperationContext_MarkAsSeen

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ChatOperationContext_MarkAsSeen

Event ID 729 — Chat: GetChatMessageProperties

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: GetChatMessageProperties

Event ID 730 — Chat: UdmSvcImpl_GetChatObjectProperties

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: UdmSvcImpl_GetChatObjectProperties

Event ID 731 — Chat: ProcessChatUpdatesBegin

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ProcessChatUpdatesBegin

Event ID 732 — Chat: ProcessChatUpdatesEnd

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: ProcessChatUpdatesEnd

Event ID 733 — Chat: UdmSvcImpl_UpdateChatObjects

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Chat: UdmSvcImpl_UpdateChatObjects

Event ID 734 — Notifying filter app: PFN = {AppPackageFamilyName}.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Notifying filter app: PFN = {AppPackageFamilyName}

Fields

Name	Description
`AppPackageFamilyName`	—

Event ID 735 — Conversation does not exist.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Conversation does not exist. ConversationId: [%1]

Fields

Name	Description
`Prop_ULong`	—

Event ID 736 — One or more conversation properties were not found.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

One or more conversation properties were not found. ConversationId: [%1]

Fields

Name	Description
`Prop_ULong`	—

Event ID 737 — Got a ChatMessage without recipients.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got a ChatMessage without recipients.

Event ID 738 — ChatCapabilitiesContext::GetCachedChatCapabilities()

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::GetCachedChatCapabilities()

Event ID 739 — ChatCapabilitiesContext::GetCachedChatCapabilities() - Contact not found

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::GetCachedChatCapabilities() - Contact not found

Event ID 740 — ChatCapabilitiesContext::GetCachedChatCapabilities() - Found a cached contact

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::GetCachedChatCapabilities() - Found a cached contact

Event ID 741 — ChatCapabilitiesContext::GetCachedChatCapabilities() - capabilities = %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::GetCachedChatCapabilities() - capabilities = %1

Fields

Name	Description
`Prop_ULong`	—

Event ID 742 — ChatCapabilitiesContext::GetCapabilitiesFromNetwork()

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::GetCapabilitiesFromNetwork()

Event ID 743 — ChatCapabilitiesContext::_RequestCapabilities()

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::_RequestCapabilities()

Event ID 744 — Conversation does not exist.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Conversation does not exist. Provider count: [%1], First Provider id [%2]

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—

Event ID 745 — Got app manager instance.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got app manager instance. HResult: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 746 — Got default messaging application.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got default messaging application. HResult: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 747 — Got messaging app package family name.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got messaging app package family name. HResult: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 748 — Got transport IDs.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got transport IDs. HResult: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 749 — Got one default transport ID.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got one default transport ID. HResult: [%1] TransportID: [%2]

Fields

Name	Description
`P1_HResult`	—
`Prop_ULong`	—

Event ID 750 — Got one default transport ID.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Got one default transport ID. HResult: [%1] TransportID: [%2]

Fields

Name	Description
`P1_HResult`	—
`Prop_ULong`	—

Event ID 751 — Flattened items to send.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Flattened items to send. HResult: [%1]

Fields

Name	Description
`P1_HResult`	—

Event ID 752 — ChatCapabilitiesContext::_FindCachedPhoneNumberCapabilities found = [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatCapabilitiesContext::_FindCachedPhoneNumberCapabilities found = [%1]

Fields

Name	Description
`Prop_ULong`	—

Event ID 753 — RcsMultipartMessageTracker::_OnChatOpenedWorker()

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsMultipartMessageTracker::_OnChatOpenedWorker()

Event ID 754 — ChatAppManager::GetDefaultMessagingApp found default messaging app in registery.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::GetDefaultMessagingApp found default messaging app in registery.

Event ID 755 — ChatAppManager::GetDefaultMessagingApp ChatAppManager::GetAllMessagingApps() failed to find any messaging apps.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::GetDefaultMessagingApp ChatAppManager::GetAllMessagingApps() failed to find any messaging apps.

Event ID 756 — ChatAppManager::_GetDefaultMessagingAppInRegistry default app not found in registry.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::_GetDefaultMessagingAppInRegistry default app not found in registry.

Event ID 757 — ChatAppManager::SetDefaultMessagingAppInRegistry().

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::SetDefaultMessagingAppInRegistry().

Event ID 758 — ChatAppManager::SetDefaultMessagingApp app already registered.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::SetDefaultMessagingApp app already registered.

Event ID 759 — ChatAppManager::_SetDefaultMessagingAppInRegistry().

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::_SetDefaultMessagingAppInRegistry().

Fields

Name	Description
`P1_UnicodeString`	—

Event ID 760 — ChatAppManager::GetAllDefaultCapableMessagingApps().

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

ChatAppManager::GetAllDefaultCapableMessagingApps(). - no default apps found

Event ID 761 — Rcs service status adapter not available

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Rcs service status adapter not available

Event ID 762 — RcsTransportChangedEventSink %1: Advise to RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsTransportChangedEventSink %1: Advise to RCS

Fields

Name	Description
`handle`	—

Event ID 763 — RcsTransportChangedEventSink %1: Unadvise from RCS.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsTransportChangedEventSink %1: Unadvise from RCS

Fields

Name	Description
`handle`	—

Event ID 764 — RcsTransportChanged event

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

RcsTransportChanged event

Event ID 800 — CallHistoryNotificationManager NotifyCallHistoryApps.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

CallHistoryNotificationManager NotifyCallHistoryApps.

Event ID 1000 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1001 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1002 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1003 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1004 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1005 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1100 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1101 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1104 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1105 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1106 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1107 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1108 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1109 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1110 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1111 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1112 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1113 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1114 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1115 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1116 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1117 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1118 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1119 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1120 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1121 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1122 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1123 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1124 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1125 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1126 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1127 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1128 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1129 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1200 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1201 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1202 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1203 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1204 — App: %1, Action: %2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

App: %1, Action: %2

Fields

Name	Description
`AppName`	—
`AccessedString`	—

Event ID 1205 — App: %1, Action: %2.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

App: %1, Action: %2

Fields

Name	Description
`AppName`	—
`AccessedString`	—

Event ID 1206 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1207 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1208 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1209 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1210 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1211 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1212 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1213 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1214 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1215 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1216 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1217 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1218 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1219 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1220 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 1221 —

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Event ID 2001 — Cleaning up stale data.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Cleaning up stale data. Priority cleanup? [%1] Pending Installs? [%2]

Fields

Name	Description
`Prop_Boolean_1`	—
`Prop_Boolean_2`	—

Event ID 2002 — Starting the knowledge defragmentation task for all sync partners

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Starting the knowledge defragmentation task for all sync partners

Event ID 2003 — Finished the knowledge defragmentation task.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Finished the knowledge defragmentation task. Examined %1 stores and %2 partners out of which defragmentation succeeded for %3, partially succeeded for %4 and failed for %5.

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—
`Prop_UInt_4`	—
`Prop_UInt_5`	—

Event ID 2004 — Starting the knowledge defragmentation task for all sync partners associated with store %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Starting the knowledge defragmentation task for all sync partners associated with store %1

Fields

Name	Description
`Prop_Prop`	—

Event ID 2005 — Finished the knowledge defragmentation task for all sync partners associated with store %1.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

Finished the knowledge defragmentation task for all sync partners associated with store %1. Examined %2 partners out of which defragmentation succeeded for %3, partially succeeded for %4 and failed for %5.

Fields

Name	Description
`Prop_UInt_1`	—
`Prop_UInt_2`	—
`Prop_UInt_3`	—
`Prop_UInt_4`	—
`Prop_UInt_5`	—

Event ID 2006 — App Store Deleted: App Id [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

App Store Deleted: App Id [%1], Reason [%2]

Fields

Name	Description
`AppId`	—
`AppDataCleanupReason`	—

Event ID 2007 — App Store Grouping Deleted: App Id [.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

App Store Grouping Deleted: App Id [%1], Reason [%2]

Fields

Name	Description
`AppId`	—
`AppDataCleanupReason`	—

Event ID 2008 — HandlePackageUninstall called for PFN.

Provider: Microsoft-Windows-UserDataAccess-UserDataService
Channel: Operational

Message

HandlePackageUninstall called for PFN: %1

Fields

Name	Description
`P1_UnicodeString`	—