Microsoft-Windows-DeviceManagement-Pushrouter

107 events across 1 channel

Event IDTitleChannel
100MDM PushRouter Service: Failed to create ConfigManager lock service binding.Operational
101MDM PushRouter Service: Successfully created RPC Server Interface group.Operational
102MDM PushRouter Service: Failed to create RPC Server Interface group.Operational
103MDM PushRouter Service: Failed to activate RPC Server Interface group because a …Operational
104MDM PushRouter Service: Successfully activated RPC Server Interface group.Operational
105MDM PushRouter Service: Failed to activate RPC Server Interface group.Operational
106MDM PushRouter Service: Successfully deactivated RPC Server Interface group.Operational
107MDM PushRouter Service: Failed to deactivate RPC Server Interface group.Operational
108MDM PushRouter Service: Successfully closed RPC Server Interface group.Operational
109MDM PushRouter Service: Failed to close RPC Server Interface group.Operational
110MDM PushRouter Service: PushRouter RPC interface Idle status changed.Operational
111MDM PushRouter Service: Number of PushRouter clients remaining.Operational
112MDM PushRouter Service: All clients handled.Operational
113MDM PushRouter Service: Number of active client count rolled over.Operational
114MDM PushRouter Service: PushRouter RPC run down occured.Operational
115MDM PushRouter Service: PushRouter::Open called by a client needing a handle to …Operational
116MDM PushRouter Service: PushRouter::Open called by a client needing to interact …Operational
117MDM PushRouter Service: PushRouter::Open called by a client needing to interact …Operational
118MDM PushRouter Service: PushRouter was submitted a message from the same service …Operational
119MDM PushRouter Service: PushRouter was submitted a message from the same service …Operational
120MDM PushRouter Service: PushRouter was submitted a message from the same service …Operational
121MDM PushRouter Service: PushRouter was submitted a message by a RPC client.Operational
122MDM PushRouter Service: PushRouter was submitted a message by a RPC client.Operational
123MDM PushRouter Service: PushRouter was created successfully.Operational
124MDM PushRouter Service: PushRouter could not be created successfully.Operational
125MDM PushRouter Service: Opening Service Control Manager to change PushRouter …Operational
126MDM PushRouter Service: Opening service handle to change PushRouter startup type …Operational
127MDM PushRouter Service: Changing PushRouter start up type to auto start failed.Operational
128MDM PushRouter Service: Changing PushRouter start up type to delayed auto start …Operational
129MDM PushRouter Service: PushRouter close called by a client interacting with it …Operational
130MDM PushRouter Service: PushRouter close called by a client interacting with it …Operational
131MDM PushRouter Service: A client initiated a get message operation from …Operational
132MDM PushRouter Service: A client was able to successfully get a message from …Operational
133MDM PushRouter Service: A client failed to get a message from PushRouter.Operational
134MDM PushRouter Service: PushRouter was instantiated.Operational
135MDM Message Persistence: Persisted message found.Operational
136MDM Message Persistence: Failed to load persisted message file.Operational
137MDM Message Persistence: Queue Id found for persisted message.Operational
138MDM Message Persistence: No client found for queue Id for persisted message.Operational
139MDM Message Persistence: Client found for queue Id for persisted message.Operational
140MDM Message Persistence: Client failed to launch for queue Id for persisted …Operational
141MDM Message Persistence: No persisted message found.Operational
142MDM Message Persistence: Failed to delete messages file.Operational
143MDM Message Persistence: Failed to process persisted messages.Operational
144MDM Message Persistence: Successfully processed persisted messages.Operational
145MDM PushRouter Service: PushRouter started routing a message.Operational
146MDM PushRouter Service: Routing a message failed.Operational
147MDM PushRouter Service: Message routed successfully.Operational
148MDM PushRouter Service: PushRouter started routing a new message.Operational
149MDM PushRouter Service: Failed to route a new message.Operational
150MDM PushRouter Service: Successfully routed a new message.Operational
151MDM Message Persistence: Failed to load unauthenticated messages file.Operational
152MDM PushRouter Authentication: Loaded an authentication provider.Operational
153MDM PushRouter Authentication: Getting authentication provider failed.Operational
154MDM PushRouter Authentication: Loaded authentication provider failed to …Operational
155MDM PushRouter Authentication: Message authenticated successfully.Operational
156MDM PushRouter Authentication: Message could not be authenticated.Operational
157MDM PushRouter Proxy: RPC call to get a message from PushRouter failed.Operational
158MDM PushRouter Proxy: RPC call to get a message from PushRouter succeeded.Operational
159MDM PushRouter Proxy: RPC call to submit a message from PushRouter failed.Operational
160MDM PushRouter Proxy: RPC call to submit a message from PushRouter succeeded.Operational
161MDM PushRouter Authentication: Failed to get network shared secret because ICCID …Operational
162MDM PushRouter Authentication: WAP Verification succeeded.Operational
163MDM PushRouter Authentication: WAP Verification failed.Operational
164MDM PushRouter Authentication: WAP Authentication failed.Operational
165MDM PushRouter Authentication: WAP Authentication succeeded.Operational
166MDM PushRouter Authentication: SyncMl Authentication failed.Operational
167MDM PushRouter Authentication: SyncMl Authentication succeeded.Operational
168MDM PushRouter Authentication: Getting ServerID from the trigger failed.Operational
169MDM PushRouter Authentication: Getting ServerID from the trigger succeeded.Operational
170MDM PushRouter Authentication: Validating trigger failed.Operational
171MDM PushRouter Authentication: Validating trigger succeeded.Operational
172MDM PushRouter Authentication: Validating nonce failed.Operational
173MDM PushRouter Authentication: Validating nonce succeeded.Operational
174MDM PushRouter Authentication: Using default nonce resync is set to false.Operational
175MDM PushRouter Authentication: Default nonce not found.Operational
176MDM PushRouter: Changing dmwappushservice startup type to demand started.Operational
177MDM PushRouter: Changing dmwappushservice startup type to demand started failed.Operational
178MDM PushRouter: Pushrouter failed to start because the dmwappushservice service …Operational
300MDM Common Utility for Policies: Policy query.Operational
301MDM Common Utility for Policies: Policy set.Operational
500DmWapPushService: Failed to retrieve ICCID of the SIM on which the message was …Operational
501DmWapPushService: Failed to copy WAP message into a format that PushRouter …Operational
502DmWapPushService: Successfully copied WAP message into a format that PushRouter …Operational
503DmWapPushService: Failed to retrieve body of WAP message.Operational
504DmWapPushService: Successfully retrieved body of WAP message.Operational
505DmWapPushService: The current value of SECPOLICY_WSPNOTIFICATIONS is.Operational
506DmWapPushService: Failed to register WNF with EventAggregator for WAP messages …Operational
507DmWapPushService: Successfully registered WNF with EventAggregator for WAP …Operational
508DmWapPushService: Callback to handle a new WAP message received.Operational
509DmWapPushService: There are pending RPC clients currently.Operational
510DmWapPushService: No pending RPC clients remain.Operational
511DmWapPushService: Setting the timer to check if all RPC clients are handled to …Operational
512DmWapPushService: Idle timeout of DmWapPushService is currently set to seconds.Operational
513DmWapPushService: Initialized idle stop-start for DmWapPushService.Operational
514DmWapPushService: Service status updated.Operational
515DmWapPushService: Failed to initialize service.Operational
516DmWapPushService: Successfully initialized service.Operational
517DmWapPushService: Failed to register service's RPC interface.Operational
518DmWapPushService: Successfully registered service's RPC interface.Operational
519DmWapPushService: Failed to uninitialize service.Operational
520DmWapPushService: Successfully uninitialized service.Operational
521DmWapPushService: Failed to unregister service's RPC interface.Operational
522DmWapPushService: Successfully unregistered service's RPC interface.Operational
523DmWapPushService: Service handler invoked.Operational
524DmWapPushService: DmWapPushService is being initialized.Operational
525DmWapPushService: Stop Service handler registered.Operational

Event ID 100 — MDM PushRouter Service: Failed to create ConfigManager lock service binding.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to create ConfigManager lock service binding. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 101 — MDM PushRouter Service: Successfully created RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Successfully created RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 102 — MDM PushRouter Service: Failed to create RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to create RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 103 — MDM PushRouter Service: Failed to activate RPC Server Interface group because a duplicate end point exists.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to activate RPC Server Interface group because a duplicate end point exists. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 104 — MDM PushRouter Service: Successfully activated RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Successfully activated RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 105 — MDM PushRouter Service: Failed to activate RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to activate RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 106 — MDM PushRouter Service: Successfully deactivated RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Successfully deactivated RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 107 — MDM PushRouter Service: Failed to deactivate RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to deactivate RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 108 — MDM PushRouter Service: Successfully closed RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Successfully closed RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 109 — MDM PushRouter Service: Failed to close RPC Server Interface group.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to close RPC Server Interface group. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 110 — MDM PushRouter Service: PushRouter RPC interface Idle status changed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter RPC interface Idle status changed. Is group idle: (%1).

Fields

NameDescription
HexInt1

Event ID 111 — MDM PushRouter Service: Number of PushRouter clients remaining.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Number of PushRouter clients remaining: (%2). Operation: (%1).

Fields

NameDescription
Message1
HRESULT

Event ID 112 — MDM PushRouter Service: All clients handled.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: All clients handled. Number of PushRouter clients remaining: (%1).

Fields

NameDescription
HexInt1

Event ID 113 — MDM PushRouter Service: Number of active client count rolled over.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Number of active client count rolled over. Number of PushRouter clients remaining: (%1).

Fields

NameDescription
HexInt1

Event ID 114 — MDM PushRouter Service: PushRouter RPC run down occured.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter RPC run down occured.

Event ID 115 — MDM PushRouter Service: PushRouter::Open called by a client needing a handle to PushRouter.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter::Open called by a client needing a handle to PushRouter.

Event ID 116 — MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter succeeded. Client id: (%1), Content Type: (%2):, App Id: (%3), Result: (%4).

Fields

NameDescription
Message1
Message2
Message3
HRESULT

Event ID 117 — MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter::Open called by a client needing to interact with PushRouter failed. Content Type: (%1):, App Id: (%2), Result: (%3).

Fields

NameDescription
Message1
Message2
HRESULT

Event ID 118 — MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message origin: (%1).

Fields

NameDescription
HexInt1

Event ID 119 — MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message submission succeeded. Sender Address: (%1), Content Type: (%2), App Id: (%3), Result: (%4).

Fields

NameDescription
Message1
Message2
Message3
HRESULT

Event ID 120 — MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was submitted a message from the same service PushRouter is running in. Message submission failed. Sender Address: (%1):, Content Type: (%2),App Id: (%3), Result: (%4).

Fields

NameDescription
Message1
Message2
Message3
HRESULT

Event ID 121 — MDM PushRouter Service: PushRouter was submitted a message by a RPC client.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was submitted a message by a RPC client. Message submission succeeded. Message origin: (%1), Result: (%2).

Fields

NameDescription
HexInt1
HRESULT

Event ID 122 — MDM PushRouter Service: PushRouter was submitted a message by a RPC client.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was submitted a message by a RPC client. Message submission failed. Message origin: (%1), Result: (%2).

Fields

NameDescription
HexInt1
HRESULT

Event ID 123 — MDM PushRouter Service: PushRouter was created successfully.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was created successfully. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 124 — MDM PushRouter Service: PushRouter could not be created successfully.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter could not be created successfully. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 125 — MDM PushRouter Service: Opening Service Control Manager to change PushRouter startup type failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Opening Service Control Manager to change PushRouter startup type failed. Result: ({HRESULT}).

Fields

NameDescription
HRESULT

Event ID 126 — MDM PushRouter Service: Opening service handle to change PushRouter startup type failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Opening service handle to change PushRouter startup type failed. Result: ({HRESULT}).

Fields

NameDescription
HRESULT

Event ID 127 — MDM PushRouter Service: Changing PushRouter start up type to auto start failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Changing PushRouter start up type to auto start failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 128 — MDM PushRouter Service: Changing PushRouter start up type to delayed auto start failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Changing PushRouter start up type to delayed auto start failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 129 — MDM PushRouter Service: PushRouter close called by a client interacting with it succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter close called by a client interacting with it succeeded. Client id: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 130 — MDM PushRouter Service: PushRouter close called by a client interacting with it failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter close called by a client interacting with it failed. Client id: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 131 — MDM PushRouter Service: A client initiated a get message operation from PushRouter.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: A client initiated a get message operation from PushRouter.

Event ID 132 — MDM PushRouter Service: A client was able to successfully get a message from PushRouter.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: A client was able to successfully get a message from PushRouter. Content Type: (%1), App Id: (%2), Source Address: (%3), Client ID: (%4), Security Account: (%5), Message origin: (%6), Result: (%7).

Fields

NameDescription
Message1
Message2
Message3
Message4
Message5
HexInt1
HexInt3

Event ID 133 — MDM PushRouter Service: A client failed to get a message from PushRouter.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: A client failed to get a message from PushRouter. Content Type: (%1), App Id: (%2), Source Address: (%3), Client ID: (%4), Message origin: (%5), Result: (%6).

Fields

NameDescription
Message1
Message2
Message3
Message4
HexInt1
HexInt3

Event ID 134 — MDM PushRouter Service: PushRouter was instantiated.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter was instantiated.

Event ID 135 — MDM Message Persistence: Persisted message found.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Persisted message found. Location: (%1).

Fields

NameDescription
Message1

Event ID 136 — MDM Message Persistence: Failed to load persisted message file.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Failed to load persisted message file. Location: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 137 — MDM Message Persistence: Queue Id found for persisted message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Queue Id found for persisted message. Location: (%1), Queue Id: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 138 — MDM Message Persistence: No client found for queue Id for persisted message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: No client found for queue Id for persisted message. Location: (%1), Queue Id: (%2), Result: (%3).

Fields

NameDescription
Message1
HexInt1
HRESULT

Event ID 139 — MDM Message Persistence: Client found for queue Id for persisted message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Client found for queue Id for persisted message. Location: (%1), Queue Id: (%2), Result: (%3).

Fields

NameDescription
Message1
Message2
HexInt3
HRESULT

Event ID 140 — MDM Message Persistence: Client failed to launch for queue Id for persisted message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Client failed to launch for queue Id for persisted message. Location: (%1), Client: (%2), Queue Id: (%3), Result: (%4).

Fields

NameDescription
Message1
Message2
HexInt3
HRESULT

Event ID 141 — MDM Message Persistence: No persisted message found.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: No persisted message found.Location: (%1).

Fields

NameDescription
Message1

Event ID 142 — MDM Message Persistence: Failed to delete messages file.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Failed to delete messages file. Queue name: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 143 — MDM Message Persistence: Failed to process persisted messages.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Failed to process persisted messages. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 144 — MDM Message Persistence: Successfully processed persisted messages.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Successfully processed persisted messages. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 145 — MDM PushRouter Service: PushRouter started routing a message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter started routing a message.

Event ID 146 — MDM PushRouter Service: Routing a message failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Routing a message failed. Content: (%1), Application: (%2), Sender: (%3), Client: (%4), Queue Id: (%5), Result: (%6).

Fields

NameDescription
Message1
Message2
Message3
Message4
Message5
HexInt1

Event ID 147 — MDM PushRouter Service: Message routed successfully.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Message routed successfully. Content: (%1), Application: (%2), Sender: (%3), Client: (%4), Queue Id: (%5), Result: (%6).

Fields

NameDescription
Message1
Message2
Message3
Message4
Message5
HexInt1

Event ID 148 — MDM PushRouter Service: PushRouter started routing a new message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: PushRouter started routing a new message.

Event ID 149 — MDM PushRouter Service: Failed to route a new message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Failed to route a new message. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 150 — MDM PushRouter Service: Successfully routed a new message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Service: Successfully routed a new message. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 151 — MDM Message Persistence: Failed to load unauthenticated messages file.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Message Persistence: Failed to load unauthenticated messages file.Queue name: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 152 — MDM PushRouter Authentication: Loaded an authentication provider.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Loaded an authentication provider. Name: (%1).

Fields

NameDescription
Message1

Event ID 153 — MDM PushRouter Authentication: Getting authentication provider failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Getting authentication provider failed. Name: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 154 — MDM PushRouter Authentication: Loaded authentication provider failed to authenticate message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Loaded authentication provider failed to authenticate message. Name: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 155 — MDM PushRouter Authentication: Message authenticated successfully.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Message authenticated successfully. Name: (%1), Security account name: (%2), Message headers: (%3), Sender address: (%4), Role: (%5), Result: (%6).

Fields

NameDescription
Message1
Message2
Message3
Message4
HexInt1
HexInt3

Event ID 156 — MDM PushRouter Authentication: Message could not be authenticated.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Message could not be authenticated. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 157 — MDM PushRouter Proxy: RPC call to get a message from PushRouter failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Proxy: RPC call to get a message from PushRouter failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 158 — MDM PushRouter Proxy: RPC call to get a message from PushRouter succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Proxy: RPC call to get a message from PushRouter succeeded. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 159 — MDM PushRouter Proxy: RPC call to submit a message from PushRouter failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Proxy: RPC call to submit a message from PushRouter failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 160 — MDM PushRouter Proxy: RPC call to submit a message from PushRouter succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Proxy: RPC call to submit a message from PushRouter succeeded. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 161 — MDM PushRouter Authentication: Failed to get network shared secret because ICCID is null.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Failed to get network shared secret because ICCID is null.

Event ID 162 — MDM PushRouter Authentication: WAP Verification succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: WAP Verification succeeded. Security param: (%1), Security role assigned: (%2), Result: (%3).

Fields

NameDescription
HexInt1
HexInt2
HRESULT

Event ID 163 — MDM PushRouter Authentication: WAP Verification failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: WAP Verification failed. Security param: (%1), Security role assigned: (%2), Result: (%3).

Fields

NameDescription
HexInt1
HexInt2
HRESULT

Event ID 164 — MDM PushRouter Authentication: WAP Authentication failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: WAP Authentication failed. Security param: (%1), Policy Value: (%2), Security role assigned: (%3), Result: (%4).

Fields

NameDescription
HexInt1
HexInt2
HexInt3
HRESULT

Event ID 165 — MDM PushRouter Authentication: WAP Authentication succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: WAP Authentication succeeded. Security param: (%1), Policy Value: (%2), Security role assigned: (%3), Result: (%4).

Fields

NameDescription
HexInt1
HexInt2
HexInt3
HRESULT

Event ID 166 — MDM PushRouter Authentication: SyncMl Authentication failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: SyncMl Authentication failed. Headers: (%1), Message Body size: (%2), Result: (%3).

Fields

NameDescription
Message1
HexInt1
HRESULT

Event ID 167 — MDM PushRouter Authentication: SyncMl Authentication succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: SyncMl Authentication succeeded. Headers: (%1), Message Body size: (%2), Result: (%3).

Fields

NameDescription
Message1
HexInt1
HRESULT

Event ID 168 — MDM PushRouter Authentication: Getting ServerID from the trigger failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Getting ServerID from the trigger failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 169 — MDM PushRouter Authentication: Getting ServerID from the trigger succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Getting ServerID from the trigger succeeded. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 170 — MDM PushRouter Authentication: Validating trigger failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Validating trigger failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 171 — MDM PushRouter Authentication: Validating trigger succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Validating trigger succeeded. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 172 — MDM PushRouter Authentication: Validating nonce failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Validating nonce failed. Type of nonce: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 173 — MDM PushRouter Authentication: Validating nonce succeeded.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Validating nonce succeeded. Type of nonce: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 174 — MDM PushRouter Authentication: Using default nonce resync is set to false.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Using default nonce resync is set to false.

Event ID 175 — MDM PushRouter Authentication: Default nonce not found.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter Authentication: Default nonce not found.

Event ID 176 — MDM PushRouter: Changing dmwappushservice startup type to demand started.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter: Changing dmwappushservice startup type to demand started. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 177 — MDM PushRouter: Changing dmwappushservice startup type to demand started failed.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter: Changing dmwappushservice startup type to demand started failed. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 178 — MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM PushRouter: Pushrouter failed to start because the dmwappushservice service is disabled.

Event ID 300 — MDM Common Utility for Policies: Policy query.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Common Utility for Policies: Policy query. Policy ID: (%1), Policy Value: (%2), Result: (%3).

Fields

NameDescription
HexInt1
HexInt2
HRESULT

Event ID 301 — MDM Common Utility for Policies: Policy set.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

MDM Common Utility for Policies: Policy set. Policy ID: (%1), Policy Value: (%2), Result: (%3).

Fields

NameDescription
HexInt1
HexInt2
HRESULT

Event ID 500 — DmWapPushService: Failed to retrieve ICCID of the SIM on which the message was received.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to retrieve ICCID of the SIM on which the message was received. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 501 — DmWapPushService: Failed to copy WAP message into a format that PushRouter understands.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to copy WAP message into a format that PushRouter understands.ICCID: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 502 — DmWapPushService: Successfully copied WAP message into a format that PushRouter understands.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully copied WAP message into a format that PushRouter understands.ICCID: (%1), Result: (%2).

Fields

NameDescription
Message1
HRESULT

Event ID 503 — DmWapPushService: Failed to retrieve body of WAP message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to retrieve body of WAP message. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 504 — DmWapPushService: Successfully retrieved body of WAP message.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully retrieved body of WAP message. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 505 — DmWapPushService: The current value of SECPOLICY_WSPNOTIFICATIONS is.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: The current value of SECPOLICY_WSPNOTIFICATIONS is: (%1).

Fields

NameDescription
HexInt1

Event ID 506 — DmWapPushService: Failed to register WNF with EventAggregator for WAP messages received by SMS Router.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to register WNF with EventAggregator for WAP messages received by SMS Router. Result: (%1).

Fields

NameDescription
HexInt1

Event ID 507 — DmWapPushService: Successfully registered WNF with EventAggregator for WAP messages received by SMS Router.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully registered WNF with EventAggregator for WAP messages received by SMS Router. Result: (%1).

Fields

NameDescription
HexInt1

Event ID 508 — DmWapPushService: Callback to handle a new WAP message received.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Callback to handle a new WAP message received.

Event ID 509 — DmWapPushService: There are pending RPC clients currently.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: There are pending RPC clients currently.

Event ID 510 — DmWapPushService: No pending RPC clients remain.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: No pending RPC clients remain.

Event ID 511 — DmWapPushService: Setting the timer to check if all RPC clients are handled to fire after seconds.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Setting the timer to check if all RPC clients are handled to fire after (%1) seconds.

Fields

NameDescription
HexInt1

Event ID 512 — DmWapPushService: Idle timeout of DmWapPushService is currently set to seconds.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Idle timeout of DmWapPushService is currently set to (%1) seconds.

Fields

NameDescription
HexInt1

Event ID 513 — DmWapPushService: Initialized idle stop-start for DmWapPushService.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Initialized idle stop-start for DmWapPushService.

Event ID 514 — DmWapPushService: Service status updated.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Service status updated. Current state: (%1), Exit code: (%2), Wait hint: (%3).

Fields

NameDescription
HexInt1
HexInt2
HexInt3

Event ID 515 — DmWapPushService: Failed to initialize service.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to initialize service. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 516 — DmWapPushService: Successfully initialized service.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully initialized service. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 517 — DmWapPushService: Failed to register service's RPC interface.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to register service's RPC interface. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 518 — DmWapPushService: Successfully registered service's RPC interface.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully registered service's RPC interface. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 519 — DmWapPushService: Failed to uninitialize service.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to uninitialize service. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 520 — DmWapPushService: Successfully uninitialized service.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully uninitialized service. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 521 — DmWapPushService: Failed to unregister service's RPC interface.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Failed to unregister service's RPC interface. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 522 — DmWapPushService: Successfully unregistered service's RPC interface.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Successfully unregistered service's RPC interface. Result: (%1).

Fields

NameDescription
HRESULT

Event ID 523 — DmWapPushService: Service handler invoked.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Service handler invoked. Opcode: (%1), Current state: (%2).

Fields

NameDescription
HexInt1
HexInt2

Event ID 524 — DmWapPushService: DmWapPushService is being initialized.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: DmWapPushService is being initialized.

Event ID 525 — DmWapPushService: Stop Service handler registered.

Provider
Microsoft-Windows-DeviceManagement-Pushrouter
Channel
Operational

Message

DmWapPushService: Stop Service handler registered. Status: (%1), Result: (%2).

Fields

NameDescription
HexInt1
HRESULT