Microsoft-Exchange-HighAvailability

808 events across 8 channels

Event	Title	Channel	Sample
100	Initiating startup automount.	Operational	N
101	Initiating automount due to store start on server 'ServerFqdn'.	Operational	N
103	Active Manager started.	Operational	N
104	Active Manager start postponed.	Operational	N
105	Active Manager stopped.	Operational	N
106	ACLL failed while performing switchover on shutdown for database 'DatabaseName'.	Operational	N
107	Lossy mount enabled for database 'DatabaseName'.	Operational	N
108	Mount rejected for database 'DatabaseName' since data loss exceeds configured …	Operational	N
109	Role monitor started with role 'Role'.	Operational	N
110	Cluster node state change detected for node 'NodeNameFqdn' (Node …	Operational	N
111	Active manager role changed from 'PreviousRole' to 'CurrentRole'.	Operational	N
112	Database 'DatabaseName' is attempting to mount on server 'ServerFqdn'.	Operational	N
113	Database 'DatabaseName' failed to mount on server 'ServerFqdn' with error: …	Operational	N
114	Database 'DatabaseName' mounted successfully on server 'ServerFqdn'.	Operational	N
118	Database 'DatabaseName' is attempting to move to 'ToServer'.	Operational	N
119	Database 'DatabaseName' failed to move to 'ToServer' with error: ErrorMessage.	Operational	N
120	Database 'DatabaseName' moved successfully to 'ToServer'.	Operational	N
121	Direct mount operation failed for database (Guid=DatabaseGuid, …	Operational	N
122	Direct dismount operation failed for database (Guid=DatabaseGuid, …	Operational	N
123	Switchover on shutdown initated for server 'SourceServer'.	Operational	N
124	Switchover on shutdown failed for server 'SourceServer' with error: …	Operational	N
125	Switchover on shutdown successfully completed for server 'SourceServer'.	Operational	N
126	Server operation generated unhandled exception (Exception=ExceptionString).	Operational	N
127	Forcefully dismounting all the locally mounted databases on server 'ServerFqdn' …	Operational	N
128	Service monitor detected that 'Service' service is now running.	Operational	N
129	Service monitor detected that 'Service' service is now stopped.	Operational	N
130	Store service start detected but configuration is currently invalid.	Operational	N
131	The FacilityDescription has been successfully initialized.	Operational	N
132	Failure item notification registration for database 'DatabaseName' failed.	Operational	N
133	Finished startup automount (AttemptedMounts=MountedCount, …	Operational	N
134	Finished automounting due to store start (Node=NodeName, …	Operational	N
135	Finished failover (Node=NodeName, Databases=DatabaseCount).	Operational	N
136	Finished switchover (Node=NodeName, Databases=DatabaseCount).	Operational	N
137	Initiating server failover (Node=NodeName).	Operational	N
138	Initiating server switchover (Node=NodeName).	Operational	N
139	Message.	Operational	N
140	Mount rejected for database 'DatabaseName' since attempts to copy the last logs …	Operational	N
141	Database 'DatabaseName' failed to mount (error: ErrorMessage).	Operational	N
142	Database 'DatabaseName' failed to dismount (error: ErrorMessage).	Operational	N
143	Database 'DatabaseName' failed to move (error: ErrorMessage).	Operational	N
144	Active Manager skipped automounting database 'DatabaseName' since MountAtStartup …	Operational	N
145	Active Manager skipped automounting database 'DatabaseName' since it was admin …	Operational	N
146	ReplayState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node …	Debug	N
147	Database 'DatabaseName' cannot be activated on possible target server …	Operational	N
148	Database 'DatabaseName' cannot be activated on any server because none of their …	Operational	N
149	An error occurred while trying to select database copy 'DatabaseName' on server …	Operational	N
150	Database copy 'DatabaseName' on server 'PossibleServer' has been selected for …	Operational	N
151	An error occurred while trying to validate the specified database copy …	Operational	N
152	Database copy 'DatabaseName' on specified server 'TargetServer' has passed …	Operational	N
153	ACLL completed without loss while performing switchover on shutdown for database …	Operational	N
154	ACLL completed without loss for database 'DatabaseName'.	Operational	N
155	Database 'DatabaseName' successfully copied the last logs to server 'ToServer' …	Operational	N
156	Database property update failed on local site (db='DatabaseName', …	Operational	N
157	Database property remote replication request failed (db='DatabaseName', …	Operational	N
158	Database property remote replication request succeeded (db='DatabaseName', …	Operational	N
159	Store service is stopped on node 'NodeName' and all the database which were …	Operational	N
160	There seems to be a database operation which is already in progress.	Operational	N
161	There seems to be a database operation which is already in progress.	Operational	N
162	Database 'DatabaseName' copied the last logs to server 'ToServer' from server …	Operational	N
163	The attempt to copy remaining uncopied logs failed for database Database.	Operational	N
164	Databases are being marked as dismounted because the store was stopped on server …	Operational	N
165	Database DatabaseName on server ServerFqdn is being dismounted because it's not …	Operational	N
166	The batch mounter operation failed with error ErrorMessage.	Operational	N
167	Best copy selection for database 'DatabaseName' failed to get the database …	Operational	N
168	Active manager did not perform an action for server 'ServerName' since debug …	Operational	N
169	Debug options settings are enabled on this Database availability group.	Operational	N
170	Log TruncationState 'StateName' for database 'DatabaseName(DatabaseGuid)' on …	TruncationDebug	N
171	Active manager received system event EventCode from server ServerReporting.	Operational	N
172	Persistent state of database DatabaseName is synchronized.	Operational	N
173	Active directory properties of database DatabaseName is synchronized.	Operational	N
174	The cluster group is hosted on this server but the current role is Unknown.	Operational	N
175	The cluster group was already moved.	Operational	N
176	This server is now running as 'Role'.	Operational	N
177	The cluster group is being moved to server 'NodeName'.	Operational	N
178	The cluster group was successfully moved to server 'NodeName'.	Operational	N
179	The cluster group failed to move to server 'NodeName'.	Operational	N
180	An error was encounted accessing the cluster'.	Operational	N
181	No new cluster owner could be found.	Operational	N
182	Active Directory access has failed.	Operational	N
183	Active Directory access is now functioning properly.	Debug	N
184	Node status could not be recorded.	Operational	N
185	Mapi access to this node may be broken.	Operational	N
186	Mapi access to this node is expected to be operational because windows …	Operational	N
187	Mapi access to this node is expected to be operational because Active Directory …	Operational	N
188	Initiating move of all active databases (Node=NodeName).	Operational	N
189	Finished moving all active databases (Node=NodeName, Databases=DatabaseCount, …	Operational	N
190	Moving all active databases failed for server 'SourceServer' (MoveComment: …	Operational	N
191	Database 'DatabaseName' cannot be activated on server 'ServerName' because the …	Operational	N
192	Suspend requested for database guid=DatabaseGuid, comment='SuspendComment', …	Operational	N
193	Suspend database guid=DatabaseGuid succeeded.	Operational	N
194	Suspend database guid=DatabaseGuid failed: Message.	Operational	N
195	Resume requested for database guid=DatabaseGuid, flags='ResumeFlags'.	Operational	N
196	Resume database guid=DatabaseGuid succeeded.	Operational	N
197	Resume database guid=DatabaseGuid failed: Message.	Operational	N
198	BeginSeed requested for database guid=DatabaseGuid, args='SeedArgs'.	Operational	N
199	BeginSeed database guid=DatabaseGuid succeeded.	Operational	N
200	BeginSeed database guid=DatabaseGuid failed: Message.	Operational	N
201	CancelSeed requested for database guid=DatabaseGuid.	Operational	N
202	CancelSeed database guid=DatabaseGuid succeeded.	Operational	N
203	CancelSeed database guid=DatabaseGuid failed: Message.	Operational	N
204	ExSearch Operation requested for database guid=DatabaseGuid on server 'Server'.	Operational	N
205	ExSearch Operation for database guid=DatabaseGuid on server 'Server' succeeded.	Operational	N
206	ExSearch Operation for database 'DatabaseName' (DatabaseGuid) on server 'Server' …	Operational	N
207	Incremental Reseed (DatabaseName\ServerName) determined logs are diverged from …	Operational	N
208	Incremental Reseed (DatabaseName\ServerName) started copying logs from gen …	Operational	N
209	Incremental Reseed (DatabaseName\ServerName) decided the local copy will have a …	Operational	N
210	Incremental Reseed (DatabaseName\ServerName) has started to patch the local …	Operational	N
211	Incremental Reseed (DatabaseName\ServerName) reused the patch file.	Operational	N
212	Incremental Reseed (DatabaseName\ServerName) patched Message1 pages to the local …	Operational	N
213	Incremental Reseed (DatabaseName\ServerName) replaced logs from gen Message1 to …	Operational	N
214	Incremental Reseed (DatabaseName\ServerName) found a page number Message1 …	Operational	N
215	Incremental Reseed (DatabaseName\ServerName) ignored the …	Operational	N
216	An error was encountered while processing a failure item for database …	Operational	N
217	An unrecoverable error on database 'DatabaseName' was encountered that triggered …	Operational	N
218	ACLL for database 'DatabaseName' failed due to a timeout while waiting to …	Operational	N
219	During ACLL the log copier for database 'DatabaseName' had to cleanup a …	Debug	N
220	Incremental Reseed (DatabaseName\ServerName) V1 is going to be performed.	Operational	N
221	Truncation context opened for database 'DatabaseName' from server 'ServerName' …	TruncationDebug	N
222	Truncation context failed to open for database 'DatabaseName' from server …	Operational	N
223	Database 'DatabaseGuid' from server 'PassiveServerName' reported ok to truncate …	TruncationDebug	N
224	Global truncation point for database 'DatabaseName' found minimum gen 'Message1' …	TruncationDebug	N
225	Log files for database 'Message1' deleted from 'Message2' to 'Message3'.	TruncationDebug	N
226	Disposed database 'Message' info from global list.	TruncationDebug	N
227	Active manager configuration change detected.	Operational	N
228	Database copy 'DatabaseName\ServerName' was in a clean state and was …	Operational	N
229	Database copy 'DatabaseName\ServerName' failed to redirty because: Message1.	Operational	N
230	The log was rolled for database copy 'DatabaseName\ServerName' to allow granular …	Debug	N
231	The attempt to roll the log for database copy 'DatabaseName\ServerName' failed: …	Operational	N
232	During ACLL for database copy 'DatabaseName\ServerName' granular logs were used …	Debug	N
233	The attempt to use granular logs during ACLL for database copy …	Operational	N
234	Granular replication on database copy 'DatabaseName\ServerName' failed to …	Operational	N
235	BatchMounter operations are disabled since registry parameter …	Operational	N
236	Granular replication on database copy 'DatabaseName\ServerName' detected log …	Operational	N
237	Granular replication on database copy 'DatabaseName\ServerName' successfully …	Operational	N
238	Granular replication on database copy 'DatabaseName\ServerName' failed to repair …	Operational	N
239	During initialization of database copy 'DatabaseName\ServerName' logs were …	Operational	N
240	During initialization of database copy 'DatabaseName\ServerName' logs could not …	Operational	N
241	Detected stale last log generated information for database 'DatabaseName'.	Operational	N
242	A new log for database copy 'DatabaseName\ServerName' was written to 'Message1' …	Operational	N
243	The database copy 'DatabaseName\ServerName' was in an errored state but …	Operational	N
244	The database copy 'DatabaseName\ServerName' was in an errored state but …	Operational	N
245	Block-mode replication for database copy 'DatabaseName\ServerName' released a …	BlockReplication	N
246	The attempt to seed database 'DatabaseName' from the active copy on server …	Seeding	N
247	Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the …	Seeding	N
248	The attempt to seed database 'DatabaseName' from the passive copy on server …	Seeding	N
249	Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the …	Seeding	N
250	Attempt to cause BugCheck failed with error 'ErrorMessage'.	Operational	N
251	Skipped bugcheck due to reason: BugcheckSkippedReason …	Operational	N
252	Failure item processing detected an inconsistent event record …	Operational	N
253	Incremental Reseed (DatabaseName\ServerName) determined that Message1 pages will …	Operational	N
254	Incremental Reseed (DatabaseName\ServerName) finished copying logs from gen …	Operational	N
255	Log verification for database copy 'DatabaseName\ServerName' failed on log file …	Operational	N
256	File 'Message1' which is part of database copy 'DatabaseName\ServerName' was …	Operational	N
257	The database copy 'DatabaseName\ServerName' will require reseeding because the …	Operational	N
258	Initiating clean dismount of database 'DatabaseName' on 'ActiveServer' since it …	Operational	N
259	Mount request for database 'DatabaseName' is rejected since system shutdown …	Operational	N
260	Initiating Store Rpc to dismount database 'DatabaseGuid' on server 'ServerName'.	Operational	N
261	Finshed dismount Store Rpc for database 'DatabaseGuid' on server 'ServerName'.	Operational	N
262	Finished force dismounting all locally mounted databases.	Operational	N
263	Initiating graceful crash of store process.	Operational	N
264	Finished graceful crash of store process.	Operational	N
265	The FacilityDescription has been stopped.	Operational	N
266	BlockModeReplication is terminated on the active side because the passive copy …	BlockReplication	N
267	BlockModeReplication is terminated on the passive side for database …	BlockReplication	N
268	Active copy of database 'DatabaseName' on this server is now starting a seed for …	Seeding	N
269	Seed-from-active for database 'DatabaseName' to the passive copy on server …	Seeding	N
270	Seed-from-active for database 'DatabaseName' to the passive copy on server …	Seeding	N
271	Passive copy of database 'DatabaseName' on this server is now starting a seed …	Seeding	N
272	Seed-from-passive for database 'DatabaseName' to the passive copy on server …	Seeding	N
273	Seed-from-passive for database 'DatabaseName' to the passive copy on server …	Seeding	N
274	Active copy of database 'DatabaseName' on this server started reading database …	Seeding	N
275	Active copy of database 'DatabaseName' on this server finished reading database …	Seeding	N
276	Disable replay lag requested for database guid=DatabaseGuid, …	Operational	N
277	Disable replay lag for database guid=DatabaseGuid succeeded.	Operational	N
278	Disable replay lag for database guid=DatabaseGuid failed: Message.	Operational	N
279	Enable replay lag requested for database guid=DatabaseGuid.	Operational	N
280	Enable replay lag for database guid=DatabaseGuid succeeded.	Operational	N
281	Enable replay lag for database guid=DatabaseGuid failed: Message.	Operational	N
282	Cluster API 'ApiName' appears to be hung for 'Elapsed'.	Operational	N
283	Operation 'ApiName' took an unusually long time of 'Elapsed' to complete.	Operational	N
284	Service 'ServiceName' was forcefully terminated.	Operational	N
285	Local dismount of all databases has been delayed.	Operational	N
286	Delayed local dismount is avoided because the Active Manager role is now Role …	Operational	N
287	Delayed local dismount request of all databases has been cancelled.	Operational	N
288	Added delayed failover entry for ServerName with Delay delay.	Operational	N
289	Delayed failover entry already exists for ServerName.	Operational	N
290	Removed delayed failover entry for 'ServerName' (Reason: Reason).	Operational	N
291	Delayed failover cancelled since ServerName now is in state 'Up'.	Operational	N
292	Transient failover suppression persistent state operation failed.	Operational	N
293	Critical Cluster API 'ApiName' failed with error ErrorCode.	Operational	N
294	Active Directory configuration lookup failed with error: Message.	Monitoring	N
295	Copy Status Poller component encountered an error: Message.	Monitoring	N
296	Replay Lag Manager component encountered an error: Message.	Monitoring	N
297	Replay Lag Manager component encountered an error when processing database …	Monitoring	N
298	Replay Lag Manager requested enabling replay lag for database copy …	Monitoring	N
299	Database 'DatabaseGuid' returns global min required 'GenToPreserve' …	TruncationDebug	N
300	Initiating mount for database 'DatabaseName' (Flags=Flags, …	Operational	N
301	Failed to mount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, …	Operational	N
302	Successfully mounted database 'DatabaseName' on ActiveServer …	Operational	N
303	Initiating dismount for database 'DatabaseName' on ActiveServer (Flags=Flags).	Operational	N
304	Failed to dismount database 'DatabaseName' on ActiveServer …	Operational	N
305	Successfully dismounted database 'DatabaseName' on ActiveServer …	Operational	N
306	Initiating move for database 'DatabaseName' (FromServer=FromServer, …	Operational	N
307	Failed to move database 'DatabaseName' (InitialActive=InitialActiveServer, …	Operational	N
308	Successfully moved database 'DatabaseName' from InitialActiveServer to …	Operational	N
309	Initiating remount for database 'DatabaseName' on ActiveServer(Flags=MountFlags, …	Operational	N
310	Failed to remount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, …	Operational	N
311	Successfully remounted database 'DatabaseName' on ActiveServer …	Operational	N
312	Initiating Acll for database 'DatabaseName' on RunningOnServer …	Operational	N
313	Failed Acll for database 'DatabaseName' on RunningOnServer …	Operational	N
314	Successfully finished Acll for database 'DatabaseName' on RunningOnServer …	Operational	N
315	Initiating store mount for database 'DatabaseName' on RunningOnServer …	Operational	N
316	Failed store mount for database 'DatabaseName' on RunningOnServer …	Operational	N
318	Successfully finished store mount for database 'DatabaseName' on RunningOnServer …	Operational	N
319	Initiating store dismount for database 'DatabaseName' on RunningOnServer …	Operational	N
320	Failed store dismount for database 'DatabaseName' on RunningOnServer …	Operational	N
321	Successfully finished store dismount for database 'DatabaseName' on …	Operational	N
322	Active server for database 'DatabaseName' changed from PreviousActiveServer to …	Operational	N
323	Attempt for mount skipped for database 'DatabaseName' on SkippedOnServer …	Operational	N
324	Acll determined that database 'UniqueId' lost DatabaseGuid log(s).	Operational	N
325	Active manager on this server is running as Role for duration …	Operational	N
326	System event 'SystemEvent' is enqueued to system event queue.	Debug	N
327	System event processing started for event 'SystemEvent'.	Debug	N
328	System event processing finished for event 'SystemEvent' (Duration=Duration).	Debug	N
329	System event processing finished for event 'SystemEvent' with exception …	Debug	N
330	System event processing for event 'SystemEvent' exceeded 'Duration'ms.	Debug	N
331	Acll determined that database 'DatabaseName' lost NumberOfLostLogs log(s).	Operational	N
332	The copy of database 'DatabaseName' is starting as a passive.	Operational	N
333	The copy of database 'DatabaseName' is losing LossInBytes bytes during …	Operational	N
334	Initiating data gathering for best copy selection for database 'DatabaseName' …	Operational	N
335	Completed data gathering for best copy selection for database 'DatabaseName' …	Operational	N
336	Acll for database 'DatabaseName' finished.	Operational	N
337	Mount for database 'DatabaseName' finished.	Operational	N
338	Incremental Reseed for database 'DatabaseName' finished divergence checking …	Operational	N
339	The copy of database 'DatabaseName' lost LossInBytes bytes after a successful …	Operational	N
340	Incremental reseed failed to preserve the old logs: Exception.	Operational	N
341	Best copy selection information chose server NewServerName.	Operational	N
342	Proceeding with move for database 'DatabaseName' (FromServer=FromServer, …	Operational	N
343	The callback to perform Preferred Moves failed with: Message.	Operational	N
382	Cluster API 'ApiName' appears to be hung for 'Elapsed'.	Operational	N
383	SpaceMonitor component encountered an error: Message.	Monitoring	N
384	SpaceMonitor component encountered an error when processing database …	Monitoring	N
385	Low space was detected for the local copy of database 'DatabaseName'.	Monitoring	N
386	SetBroken called for the local copy of database 'DatabaseName'.	Operational	N
387	Average disk write rate has been above the threshold of Thresholdms for …	Operational	N
388	A Controller cache reset was done successfully on MachineName.	Operational	N
389	Average disk read latency has been above the threshold for database MachineName.	Operational	N
390	An NTFS corruption issue has been detected on system drive of this server.	Operational	N
391	An NTFS corruption issue has been detected on drive D: of this server.	Operational	N
392	NTFS corruption issues have been detected on multiple drives of this server.	Operational	N
393	SetDisconnected called for the local copy of database 'DatabaseName'.	Operational	N
394	Segments Retransmitted counter has been above the threshold of Threshold …	Operational	N
395	A network adapter reset was failed on MachineName Error: ErrorMessage.	Operational	N
396	A network adapter reset was done successfully on MachineName.	Operational	N
397	Fail to send RescueBox recovery request on MachineName Error: ErrorMessage.	Operational	N
398	A RescueBox recovery request has been sent successfully on MachineName.	Operational	N
399	Fpga presence check has been failing with error ErrorCode for …	Operational	N
500	The ThirdPartyReplication provider successfully started the NotificationListener …	Operational	N
501	The ThirdPartyReplication provider attempted to start the NotificationListener …	Operational	N
502	The ThirdPartyReplication provider is stopping the NotificationListener.	Operational	N
503	An unexpected exception was caught by HAThirdPartyReplication.	Operational	N
504	The ThirdPartyReplication provider was notified that it is entering the PAME …	Operational	N
505	The ThirdPartyReplication provider was notified that it is entering the SAME …	Operational	N
506	The ThirdPartyReplication provider was notified that database 'DatabaseGuid' …	Operational	N
600	The Exchange Third Party Replication Listener was successfully started.	Operational	N
601	The Exchange Third Party Replication Listener failed to start due to an error: …	Operational	N
602	The Exchange Third Party Replication Listener is stopping.	Operational	N
603	ThirdPartyReplication is enabled but an invalid operation was attempted: Message …	Operational	N
604	ThirdPartyReplication service was denied to user 'Message' because it is not …	Operational	N
605	ImmediateDismountMailboxDatabase for database 'DatabaseGuid' failed: Message The …	Operational	N
606	ChangeActiveServer for database 'DatabaseGuid' to server 'NewActiveServerName' …	Operational	N
607	ChangeActiveServer for database 'DatabaseName' 'DatabaseGuid' from server …	Operational	N
608	The Third Party Replication vendor responded with 'Response' to a …	Operational	N
609	The Third Party Replication vendor did not respond to a DatabaseMoveNeeded for …	Operational	N
700	Disk heartbeat started.	Operational	N
701	Disk heartbeat stopped.	Operational	N
702	Replay Lag Manager successfully enabled replay lag for database copy …	Monitoring	N
703	Replay Lag Manager failed to enable replay lag for database copy …	Monitoring	N
704	Replay Lag Manager requested disabling replay lag for database copy …	Monitoring	N
705	Replay Lag Manager successfully disabled replay lag for database copy …	Monitoring	N
706	Replay Lag Manager failed to disable replay lag for database copy …	Monitoring	N
707	Log Replay for database 'DatabaseName' is replaying logs from generation …	Operational	N
708	Log Replay for database 'DatabaseName' is replaying logs in the replay lag …	Operational	N
709	Log Replay for database 'DatabaseName' is reinstating replay lag.	Operational	N
710	Dumpster Redelivery component encountered an error when determining server …	Operational	N
711	Re-delivery of messages from the transport dumpster will be attempted for …	Operational	N
712	Dumpster redelivery for database 'DatabaseName' failed.	Operational	N
713	Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database …	Operational	N
714	Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit …	Operational	N
715	Successfully requested dumpster redelivery to HUB Transport server HubServer to …	Operational	N
716	Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database …	Operational	N
717	Active Manager detected remote site connectivity issues but the majority of …	Operational	N
718	Active Manager is postponing the immediate dismount of locally mounted databases …	Operational	N
719	Majority node check completed.	Operational	N
720	Majority node check was not attemped since there are no cluster members …	Operational	N
721	LastKnownGoodConfig serialization failed.	Operational	N
722	LastKnownGoodConfig initialized from registry.	Operational	N
723	Periodic database status analyzer skipped mounting database 'DatabaseName'.	Operational	N
724	Database dismount failed on timeout (databaseGuid='DatabaseGuid', …	Operational	N
725	FileChecker got 'file in use' error, when trying to access database …	Operational	N
726	Acll for database 'DatabaseName' observed highest log generation as HighestGen …	Operational	N
727	Active Manager detected remote site connectivity issues and the majority of …	Operational	N
728	Skipped bugcheck since another request is already in progress.	Operational	N
729	Attempting to cause BugCheck.	Operational	N
730	Skipped bugcheck due to store as registry key 'DisabledRegKey' has disabled it …	Operational	N
731	Initiating local Store Rpc to mount database 'DatabaseGuid'.	Operational	N
732	Successfully finished local mount for database 'DatabaseGuid'.	Operational	N
733	Failed local Store Mount Rpc for database 'DatabaseGuid'.	Operational	N
734	Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database …	Operational	N
735	An ExceededDatabaseMaxSize error on database 'DatabaseName' was encountered that …	Operational	N
736	Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit …	Operational	N
737	Dumpster redelivery resubmit RPC to resubmit messages for database …	Operational	N
738	Replay Lag Manager suppressed a request to disable replay lag for database copy …	Monitoring	N
739	The store service is being killed.	Operational	N
740	A diagnostic dump has been sent prior to killing the store service.	Operational	N
747	ESE staging flags are configured to: FlagsString (FlagsInt) on MachineName.	Operational	N
748	Log Replay suspend/resume state for database 'DatabaseName' has changed.	Operational	N
750	Replay Lag Manager requested activating replay lag delay (suspending log replay) …	Monitoring	N
751	Replay Lag Manager successfully activated replay lag delay (suspended log …	Monitoring	N
752	Replay Lag Manager failed to activate replay lag delay (suspend log replay) for …	Monitoring	N
753	Replay Lag Manager requested deactivating replay lag (resuming log replay) for …	Monitoring	N
754	Replay Lag Manager successfully deactivated replay lag (resumed log replay) for …	Monitoring	N
755	Replay Lag Manager failed to deactivate replay lag (resume log replay) for …	Monitoring	N
756	Replay Lag Manager will attempt to deactivate replay lag (resume log replay) for …	Monitoring	N
780	The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for longer …	Operational	N
781	The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for a very …	Operational	N
800	BlockMode replication for database 'DatabaseName' failed to initialize with the …	BlockReplication	N
801	BlockModeReplication was unable to drain the write queue for passive database …	BlockReplication	N
802	Database 'DatabaseName' is not replicated, yet constraint is not set to None in …	Monitoring	N
803	Database 'DatabaseName' is replicated, but constraint 'Constraint' is not …	Monitoring	N
804	Database 'DatabaseName' last log generation number ServerName received by the …	Monitoring	N
805	Database 'DatabaseName' last log generation number PassiveLogCopyGeneration …	Monitoring	N
806	Database 'DatabaseName' best copy could not be found.	Monitoring	N
807	Database 'DatabaseName' most up-to-date copy is on server 'ServerName'.	Monitoring	N
808	Database 'DatabaseGuid' throttling data is updated for the first time after …	Monitoring	N
809	Database 'DatabaseName' throttling constraint is None.	Monitoring	N
810	Database 'DatabaseName' is throttled based on following values: data protection …	Monitoring	N
811	At initialization, database copy 'DatabaseName\ServerName' has logs in the …	Operational	N
812	Primary Active Manager is not responding to other servers or it is not in valid …	Operational	N
813	PAM health monitor encountered an exception while trying to check the health …	Operational	N
814	PAM health monitor cancelled the attempt to move PAM since the server changed …	Operational	N
815	PAM health monitor cancelled the attempt to move PAM since it got valid reply …	Operational	N
816	PAM health monitor successfully moved PAM (From=FromServer, To=ToServer).	Operational	N
817	PAM health monitor could not find any server with valid role to move PAM.	Operational	N
818	Active manager configuration is not initialized.	Operational	N
819	PAM health monitor is attempting to move PAM (From=FromServer, To=ToServer).	Operational	N
820	AD lookup failed: Message.	Operational	N
821	Seeding to the local copy of database 'DatabaseName' ('DatabaseGuid') failed: …	Seeding	N
822	CI Seeding has begun for database 'DatabaseName'.	Seeding	N
823	CI Seeding failed for database 'DatabaseGuid'.	Seeding	N
824	CI Seeding encounted an error while processing database 'DatabaseName' …	Seeding	N
825	DB Seeding has begun for the local copy of database 'DatabaseName' …	Seeding	N
826	DB Seeding has completed for the local copy of database 'DatabaseName' …	Seeding	N
827	CI Seeding has begun for the local copy of database 'DatabaseName' …	Seeding	N
828	CI is trying to resume indexing for the local copy of database 'DatabaseName' …	Seeding	N
829	Seeding log files failed on the source side while processing database …	Seeding	N
830	Seeding failed on the source side while processing database 'DatabaseName' …	Seeding	N
831	Incremental Reseed (DatabaseName\ServerName) started saving old logs from gen …	Operational	N
832	Incremental Reseed (DatabaseName\ServerName) started moving new logs from gen …	Operational	N
833	The copy of 'DatabaseName' has been marked for stop.	Debug	N
834	The copy 'DatabaseName\ServerName' is starting with no logs.	Operational	N
835	The copy 'DatabaseName\ServerName' received gen Message1 from global …	Operational	N
836	The copy 'DatabaseName\ServerName' found log reset pending with gen Message1.	Operational	N
837	The local copy of 'DatabaseName' is starting with first log to copy at gen …	Operational	N
838	The copy 'DatabaseName\ServerName' failed to get start gen from global …	Operational	N
839	The log copier for 'DatabaseName\ServerName' is starting with the lowest …	Operational	N
840	Database 'DatabaseName' failed to mount on server 'ServerFqdn' due to timeout: …	Operational	N
841	ListMdbStatus failed to server 'NodeName': Message.	Operational	N
842	ListMdbStatus = MdbStatusFlags for database 'DatabaseName' (DatabaseGuid) on …	Debug	N
843	Recovery from ListMdbStatus failure is being attempted.	Operational	N
844	Recovery from ListMdbStatus failure is being attempted.	Operational	N
845	Failed to close the backup reader handle for database 'DatabaseName' …	Seeding	N
846	Database 'DatabaseName' has no copies and is being ignored.	Operational	N
847	GetDiskFreeSpaceEx failed with error ErrorCode using path 'DatabasePath' for …	TruncationDebug	N
848	Low disk space exists on the active (local) copy of database DatabaseGuid.	TruncationDebug	N
849	The IoBufferPool used by block mode replication was initialized with BufferCount …	Operational	N
850	Mount status validation failed after database 'DatabaseName' could not be moved …	Operational	N
851	Full server reseed is being started.	Seeding	N
852	Full server reseed is first attempting to resume database copy …	Seeding	N
853	Full server reseed failed to resume database copy 'DatabaseName\ServerName'.	Seeding	N
854	Full server reseed encountered an error.	Seeding	N
855	Full server reseed has completed kicking off reseeds.	Seeding	N
856	Full server reseed is now attempting to reseed database copy …	Seeding	N
857	Full server reseed failed to reseed database copy 'DatabaseName\ServerName'.	Seeding	N
858	Full server reseed is being skipped because the Microsoft Exchange Replication …	Seeding	N
859	Another instance of a full server reseed is already running.	Seeding	N
860	Database 'DatabaseName' is active on a disfavored server but cannot be moved …	Operational	N
861	Loose truncation is being used on database 'DatabaseName'.	TruncationDebug	N
862	Truncation for database 'DatabaseGuid' was unable to find file …	TruncationDebug	N
863	The support api failed to start: Message.	Operational	N
864	The TCP listener has started listening on port Port.	Operational	N
865	Serialization failed: Message.	Operational	N
866	Truncation for database 'DatabaseGuid' is paused because a backup is in …	TruncationDebug	N
867	CI Seeding has completed for the local copy of database 'DatabaseName' …	Seeding	N
868	The TCP listener failed to start listening on port Port.	Operational	N
869	Windows is configured for scavenge replication on port Port.	Operational	N
870	Windows is not configured for scavenge replication.	Operational	N
871	Windows is failed to configure for scavenge replication on port Port.	Operational	N
872	Replication for passive copy of DatabaseName is switching to scavenge.	Operational	N
873	Replication for passive copy of DatabaseName is switching to normal.	Operational	N
874	Active Directory is in a failed state.	Operational	N
875	The replication TCP port stored in the registry failed.	Operational	N
876	FileMode for database 'DatabaseName' is connected at gen StartingGen with the …	Debug	N
877	Log file 'LogFileName' has unexpected signature 'LogFileSig' instead of …	Operational	N
878	Thread priority was not downgraded: Message.	Operational	N
879	FileChecker determined that database file 'EdbFilePath' for database …	Operational	N
880	FileChecker determined that database file 'EdbFilePath' for database …	Operational	N
881	FileChecker determined that database file 'EdbFilePath' for database …	Operational	N
882	File-mode replication for database 'DatabaseName' is starting with passive …	Debug	N
883	File-mode replication for database 'DatabaseName' is terminating with passive …	Debug	N
884	Deletion of file 'Message1' which is part of database copy …	Operational	N
900	The passive copy of 'DatabaseName' is starting its components.	Debug	N
901	The copy of 'DatabaseName' encountered an unusual situation: Details.	Debug	N
902	ACLL starting for 'DatabaseName'.	Debug	N
903	ACLL for 'DatabaseName' finished after Duration.	Debug	N
904	ACLL for 'DatabaseName' failed after Duration.	Debug	N
905	Mount for local copy of 'DatabaseName' is starting.	Debug	N
906	IncrementalReseed for 'DatabaseName' is replacing OldLog with NewLog.	Debug	N
907	Acll for 'DatabaseName' failed due to an active incompatible operation: Error.	Debug	N
908	Mount for 'DatabaseName' failed due to an active incompatible operation: Error.	Debug	N
909	Database 'DatabaseName' was seeded to TargetServer.	Seeding	N
910	DB Seeding has begun for the local copy of database 'DatabaseName' …	Seeding	N
911	DB Seeding has completed for the local copy of database 'DatabaseName' …	Seeding	N
912	Seeding file 'EdbFilePath' for the local copy of database 'DatabaseName' …	Seeding	N
913	Failed to close the backup reader file handle for 'EdbFilePath' of database …	Seeding	N
1000	BlockMode replication could not obtain the lock on the timer.	BlockReplication	N
1001	A client-side network connection to RemoteNodeName using 'RemoteEndpoint' from …	Network	N
1002	A client-side attempt to connect to RemoteNodeName using 'RemoteEndpoint' from …	Network	N
1003	Database redundancy health check failed.	Monitoring	N
1004	Database redundancy health check passed.	Monitoring	N
1005	Database site-level redundancy health check failed.	Monitoring	N
1006	Database site-level redundancy health check passed.	Monitoring	N
1007	Database availability health check failed.	Monitoring	N
1008	Database availability health check passed.	Monitoring	N
1009	Database site-level availability health check failed.	Monitoring	N
1010	Database site-level availability health check passed.	Monitoring	N
1011	Health validation check 'CheckName' for database copy 'DatabaseCopyName' …	Monitoring	N
1012	Database Health Monitor component encountered an error: Message.	Monitoring	N
1013	A server-side connection is open with client RemoteNodeName using remote …	Network	N
1014	A server-side connection was closed.	Network	N
1015	A client-side connection was closed.	Network	N
1016	A server-side idle connection is being closed.	Network	N
1017	Database redundancy two-copy health check passed.	Monitoring	N
1018	Database redundancy two-copy health check failed.	Monitoring	N
1019	An inconsistency was detected by network discovery: 'Message' Normally this is …	Network	N
1020	This server rejected a connection attempt from remote 'RemoteEndpoint' to …	Network	N
1021	Database 'DatabaseName' appears to have a copy status cached entry that has not …	Monitoring	N
1022	Some databases on server 'Message1' have copy status cached entries that have …	Monitoring	N
1023	Database remote connectivity health check failed.	Monitoring	N
1024	Database remote connectivity health check passed.	Monitoring	N
1025	Health validation check 'CheckName' for database copy 'DatabaseCopyName' is …	Monitoring	N
1026	All databases on server 'Message' have copy status cached entries that have been …	Monitoring	N
1027	PAM monitor failure to restart ClusSvc on Server.	Operational	N
1028	PAM monitor successfully restarted ClusSvc on Server.	Operational	N
1029	Database RPC Authentication health check failed.	Monitoring	N
1030	Database RPC Authentication health check passed.	Monitoring	N
1031	The Database Health Monitor component found database copies with the following …	Monitoring	N
1100	Managed Availability health tracker encountered an error.	Operational	N
1101	Initiating move of all active databases requested by a managed availability …	Operational	N
1102	Finished moving all active databases requested by a managed availability …	Operational	N
1103	Server: ServerName HealthStates: HealthStates.	Operational	N
1104	AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.	AppLogMirror	N
1105	AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.	AppLogMirror	N
1106	AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.	AppLogMirror	N
1107	Automatic Reseed Manager component encountered an error: Message.	Seeding	N
1108	Automatic Reseed Manager component encountered an error when processing database …	Seeding	N
1109	Automatic Reseed Manager is starting repair workflow 'WorkflowName' for database …	Seeding	N
1110	Automatic Reseed Manager successfully completed repair workflow 'WorkflowName' …	Seeding	N
1111	Automatic Reseed Manager failed to execute repair workflow 'WorkflowName' for …	Seeding	N
1112	Automatic Reseed Manager has detected a content indexing error for database …	Seeding	N
1113	Automatic Reseed Manager has detected single copy of the content index for …	Seeding	N
1114	Automatic Reseed Manager has detected no copy of the content index for database …	Seeding	N
1115	Unable to read database 'DatabaseName' throttling configuration.	Monitoring	N
1116	Server-level health validation check failed to update the LastRunTime in the …	Monitoring	N
1117	Automatic Reseed Manager throttled repair workflow 'WorkflowName' for database …	Seeding	N
1118	Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part …	Seeding	N
1119	Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part …	Seeding	N
1120	Automatic Reseed Manager failed to reseed database copy 'DatabaseName' as part …	Seeding	N
1121	Automatic Reseed Manager failed to assign a spare volume for database copy …	Seeding	N
1122	Automatic Reseed Manager recently assigned a spare volume for database copy …	Seeding	N
1123	Automatic Reseed Manager is skipping a reseed of database copy 'DatabaseName' as …	Seeding	N
1124	Automatic Reseed Manager is beginning attempt number AttemptNumber of execution …	Seeding	N
1125	Automatic Reseed Manager has successfully assigned spare volume 'VolumeName' …	Seeding	N
1126	Automatic Reseed Manager failed to execute attempt number AttemptNumber of stage …	Seeding	N
1127	Automatic Reseed Manager has successfully initiated reseed (with …	Seeding	N
1128	Automatic Reseed Manager is resetting repair workflow 'WorkflowName' for …	Seeding	N
1129	Automatic Reseed Manager has successfully configured the missing mount point for …	Seeding	N
1130	Automatic Reseed Manager failed to do in-place reseed for database copy …	Seeding	N
1131	The Disk Reclaimer is searching for quarantined disks that can potentially be …	Seeding	N
1132	The Disk Reclaimer failed to pass the database redundancy health check for one …	Seeding	N
1133	The Disk Reclaimer failed to reclaim volume 'VolumeName' mounted at …	Seeding	N
1134	The Disk Reclaimer succeeded to format and reclaim volume 'VolumeName' mounted …	Seeding	N
1135	The Disk Reclaimer encountered an error: ErrorMessage.	Seeding	N
1136	The Disk Reclaimer encountered an error when trying to determine if volume …	Seeding	N
1137	The Disk Reclaimer started configuring volume mountpoints after Reinstall on …	Seeding	N
1138	The Disk Reclaimer PostInstall configuration is attempting to resume all copies …	Seeding	N
1139	The Disk Reclaimer found one or more unknown databases while configuring …	Seeding	N
1140	The Disk Reclaimer PostInstall configuration encountered an error while …	Seeding	N
1141	The Disk Reclaimer finished configuring volume mountpoints after Reinstall on …	Seeding	N
1142	The Disk Reclaimer is about to quarantine corrupted disk or volume 'VolumeName' …	Seeding	N
1143	The Disk Reclaimer skipped reclaiming volume 'VolumeName' mounted at …	Seeding	N
1144	The Disk Reclaimer found 'Count' never mounted active databases on the server.	Seeding	N
1145	The Disk Reclaimer found never mounted active database: 'Database' missing …	Seeding	N
1146	The Disk Reclaimer was unable to fixup mountpoint for active database: …	Seeding	N
1147	The Disk Reclaimer was unable to mount active database: 'DatabaseName'.	Seeding	N
1148	The Disk Reclaimer completed its attempt to fix volume mountpoints for active …	Seeding	N
1149	The Volume Manager found the following volumes: …	Seeding	N
1150	Database active status tracker initialization failed with error: Message.	Operational	N
1151	The Disk Reclaimer PostInstall configuration found a misconfigured volume …	Seeding	N
1152	The Disk Reclaimer will not attempt to reclaim any quarantined volumes because …	Seeding	N
1153	Automatic Reseed Manager is being skipped because: Message.	Seeding	N
1154	The Disk Reclaimer is being skipped because: Message.	Seeding	N
1155	The Disk Reclaimer encountered an Active Directory error: ErrorMessage.	Seeding	N
1156	Automatic Reseed Manager found that the mount point directory for database …	Seeding	N
1157	The Disk Reclaimer found there are 'FormattedVolumeCount' volumes which have …	Operational	N
1158	The Disk Reclaimer didn't found any formatted volumes.	Operational	N
1160	Cluster API operation seems to be hung.	Operational	N
1161	Hung node detection completed (GUM ID: GumId LockOwner: LockOwner Context: …	Operational	N
1162	Hung node detection failed (Error: ErrorMessage).	Operational	N
1163	Attempt to open the cluster on server ServerName timed out while trying to find …	Operational	N
1164	Attempt to kill cluster service was skipped since the registry override …	Operational	N
1165	Sending a request to kill ServiceName service on server ServerName.	Operational	N
1166	ServiceName service successfully killed on server ServerName.	Operational	N
1167	An attempt to kill ServiceName service on server ServerName failed.	Operational	N
1168	Request received to kill ServiceName service from server ServerName.	Operational	N
1169	Killing process ProcessName.	Operational	N
1170	Hung node action skipped since gum id change was observed in the detection.	Operational	N
1171	Incremental Reseed (DatabaseName\ServerName) failed to copy log generation …	Operational	N
1172	Bandwidth Monitor is now running.	Operational	N
1173	Bandwidth Monitor stopped.	Operational	N
1174	Bandwidth Monitor raised exception: Message.	Operational	N
1180	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1181	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1182	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1183	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1184	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1185	An in-place reseed has been requested for the local copy of database …	Seeding	N
1186	The Volume Manager found misconfigured volume 'VolumeName' mounted at …	Seeding	N
1187	The Volume Manager found misconfigured volume 'VolumeName' mounted at …	Seeding	N
1188	Automatic Reseed Manager found never mounted active database 'Database' missing …	Seeding	N
1189	Automatic Reseed Manager allocated volume 'VolumeName' for never mounted active …	Seeding	N
1190	Automatic Reseed Manager was unable to fixup mountpoint for active database: …	Seeding	N
1191	Automatic Reseed Manager was unable to mount active database: 'DatabaseName'.	Seeding	N
1192	Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part …	Seeding	N
1193	Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part …	Seeding	N
1194	A reseed to spare volume has been requested for the local copy of database …	Seeding	N
1195	Automatic Reseed Manager determined that database 'DatabaseName' recovered from …	Seeding	N
1196	Automatic Reseed Manager determined that the secondary partition of database …	Seeding	N
1197	Automatic Reseed Manager determined that the secondary partition of database …	Seeding	N
1198	Automatic Reseed Manager failed to reseed the secondary partition of database …	Seeding	N
1210	Attempt to initiate system failover for replay service down failed for server …	Operational	N
1211	System failover skipped for server ServerName.	Operational	N
1212	Throttling check did not allow system failover to proceed for server ServerName.	Operational	N
1213	Throttling check allowed system failover to proceed for server ServerName.	Operational	N
1214	Failed to initialize throttled action traker state from cluster database.	Operational	N
1215	Failover on replay down feature is disabled with registry override.	Operational	N
1216	Failover on replay down tracker is not initialized.	Operational	N
1217	Starting action Action for cluster node NodeName.	Operational	N
1218	Completed action Action for cluster node NodeName.	Operational	N
1219	Cluster node action Action is blocked for NodeName since there are operations …	Operational	N
1220	Cluster node action Action is blocked for NodeName since there are nodes that …	Operational	N
1230	Cached last log updater failed to update last log generation info.	Operational	N
1231	An rpc request to PAM to update last log generation info failed.	Operational	N
1232	Initiating cluster database updates from local nodes in stead of Primary Active …	Operational	N
1233	Continuing cluster database updates locally …	Operational	N
1234	Switching back to PAM based to cluster database updates …	Operational	N
1235	Database 'DatabaseName' copy on server 'ServerName' is too far behind.	Monitoring	N
1236	After TimeoutInSeconds seconds the SocketStream leaked resources to allow its …	Operational	N
1237	SocketStream could not obtain buffer space.	Operational	N
1238	Database file 'EdbFilePath' for database 'DatabaseName' finished seeding.	Seeding	N
1239	Negotiation of compression with server 'RemoteNodeName' failed.	Operational	N
1240	Remote server 'RemoteNodeName' passed an unrecognized compression configuration.	Operational	N
1241	PAM Monitor is attempting to perform the recovery.	Operational	N
1242	PAM move cancelled since majority are not running as SAM (Total: …	Operational	N
1243	Database operation 'RequestedOperationClass' is not enqueued since database …	Operational	N
1244	MonitoredDatabase for database 'DatabaseName' failed to start: ExceptionMessage …	Operational	N
1245	Attempt to query bitlocked failed: Message.	Operational	N
1246	Seeding starts for local copy of database 'DatabaseName'.	Seeding	N
1247	Seeding for local copy of database 'DatabaseName' failed to establish divergence …	Seeding	N
1248	Incremental seeding for local copy of database 'DatabaseName' failed to send the …	Operational	N
1249	Seeding for local copy of database 'DatabaseName' was cancelled.	Seeding	N
1250	Cluster batch writer failed while attempting operation 'Operation' (error: …	Operational	N
1251	The MonitoredDatabase for database 'DatabaseName' was requested to stop at …	Operational	N
1252	The Disk Reclaimer has removed the mountpoint 'MountPoint'.	Seeding	N
1253	The Disk Reclaimer has added the mountpoint 'MountPoint' => 'Volume'.	Seeding	N
1254	The Disk Reclaimer has created the folder for database 'Database' at 'Folder'.	Seeding	N
1255	Automatic Reseed Manager failed to execute attempt number AttemptNumber of stage …	Seeding	N
1256	The Disk Reclaimer encountered an error when trying to determine which database …	Seeding	N
1270	The secondary partition status for the local copy of database 'DatabaseName' …	Operational	N
1300	Start gathering hung node information via RPC calls (List of servers: …	Operational	N
1301	Start gathering cluster node status (ClusterOpen node: ClusterOpenTarget).	Operational	N
1302	Hung Node information gathering completed (HungNodeInfo: HungNodeInfo).	Operational	N
1303	Hung Node information analysis completed (HungNodeAction: HungNodeAction).	Operational	N
1310	Start recovery action for cluster node hung (Target servers: TargetServers).	Operational	N
1311	Requesting remote reboot (target servers: RebootServers) and restart of clussvc …	Operational	N
1320	Attempt to remote reboot of target node succeeded (Target: Targets, …	Operational	N
1321	Attempt to remote reboot of target node failed or throttled.	Operational	N
1322	Attempt to evict target node succeeded (Target: Targets).	Operational	N
1323	Total up node check failed for evict target node action.	Operational	N
1324	Total up node check succeeded for evict target node action.	Operational	N
1325	Attempt to evict target node failed or throttled.	Operational	N
1326	Recovering ClusDB hang by attempting to restart ClusSvc on the following …	Operational	N
1327	Recovering ClusDB hang by attempting to restart clussvc on all nodes (Up, …	Operational	N
1328	Restarting an individual node was throttled (ClusDB hang recovery).	Operational	N
1329	Restarting clussvc on a node as part of restarting all nodes in the DAG was …	Operational	N
1330	Cluster database periodic cleanup failed.	Operational	N
1331	Cluster database periodic cleanup skipped.	Operational	N
1332	Cluster database periodic cleanup batch operation failed.	Operational	N
1333	Cluster database periodic cleanup did not detect any stale databases or servers.	Operational	N
1334	Cluster database periodic cleanup for key ParentKeyName completed …	Operational	N
1335	Cluster database periodic cleanup detected DatabaseCountWaitingForConfirmation …	Operational	N
1336	Cluster database periodic cleanup analyze failed.	Operational	N
1340	Recovering ClusDB hang by attempting to restart clussvc on all nodes is blocked: …	Operational	N
1381	Prereqs for offline defragmentation process of database Database completed …	Operational	N
1382	Prereqs for offline defragmentation process of database Database failed (it took …	Operational	N
1383	Dismount of database Database and suspending its copies (for offline …	Operational	N
1384	Dismount of database Database or suspending its copies (for offline …	Operational	N
1385	EDB file defragmentation stage and integrity check of database Database …	Operational	N
1386	EDB file defragmentation stage and integrity check of database Database failed …	Operational	N
1387	Final stage (mount database and reseeding copies) of offline defragmentation of …	Operational	N
1388	Final stage (mount database and reseeding copies) of offline defragmentation of …	Operational	N
1389	Recovering from incosistent state (left behind by one of the stages of offline …	Operational	N
1390	Recovering from incosistent state (left behind by one of the stages of offline …	Operational	N
1400	AD configuration is not available : Message.	Operational	N
1401	AD configuration refresh took excessive time : TotalDuration.	Operational	N
1402	AD configuration refresh failed : Message.	Operational	N
1403	Process ProcessName is using MeasuredConsumption MB of memory.	Operational	N
1404	Process ProcessName is using MeasuredConsumption handles.	Operational	N
1405	Process ProcessName is using MeasuredConsumption threads.	Operational	N
1406	SetServerComponentState was run: Server=Server Requester=Requester …	Operational	N
1500	Database Health Tracker component encountered an error: Message.	Monitoring	N
1501	Database Health Tracker is now running as the Primary role.	Monitoring	N
1502	Database Health Tracker is currently running as the 'Role' role.	Monitoring	N
1503	Database Health Tracker, running as the Primary role, failed to persist the …	Monitoring	N
1504	Database Health Tracker, running as a Secondary role, failed to persist the …	Monitoring	N
1505	Database Health Tracker failed to initialize the health information from the …	Monitoring	N
1506	Remote operation 'OperationName' timed out to one or more servers after …	Monitoring	N
1507	Remote operation 'OperationName' failed to one or more servers.	Monitoring	N
1508	During startup, the Primary candidate role failed to get back any successful …	Monitoring	N
1509	During startup, the Primary candidate role determined that a new health …	Monitoring	N
1510	During startup, the Primary candidate role is ignoring the older health …	Monitoring	N
1511	Secondary role received an older health information table of update time …	Monitoring	N
1512	The Monitoring WCF service failed to register its endpoint.	Monitoring	N
1513	During startup, the Primary candidate role is updating its health information …	Monitoring	N
1514	Database Health Tracker could not initialize the health information from the …	Monitoring	N
1515	Database Health Tracker is initializing the health information from the …	Monitoring	N
1516	During startup, the Primary candidate role will initialize the health …	Monitoring	N
1517	Failover sequence number for database guid DatabaseGuid is not based on time due …	Operational	N
1518	The Monitoring WCF service started.	Monitoring	N
1600	Database potential redundancy health check passed.	Monitoring	N
1601	Database potential redundancy health check failed.	Monitoring	N
1602	Databases on server Message have passed the check for potential database …	Monitoring	N
1603	Some databases on server LocalMachineName will potentially have insufficient …	Monitoring	N
1604	Database potential redundancy health check failed, but not enough total passive …	Monitoring	N
1605	Server level database potential redundancy issue has been detected for two or …	Monitoring	N
1606	FailedCopies Database Copies out of NumberOfCopies have a growing Log Copy queue …	Monitoring	N
2000	AvailabilitySensorError component encountered an error: Message.	Operational	N
2001	Database scanning during passive replay is disabled on 'DatabaseName'.	Operational	N
2002	Database scanning during passive replay is enabled on 'DatabaseName'.	Operational	N
2003	The log copier for database 'DatabaseName' found divergence at generation …	Operational	N
2004	The log copier for database 'DatabaseName' could not verify divergence at …	Operational	N
2005	The log copier for database 'DatabaseName' is terminating because server …	Operational	N
2006	The ESE LogConsumer for database 'DatabaseName' failed during termination: …	BlockReplication	N
2007	BlockMode terminated for database 'DatabaseName'.	BlockReplication	N
2008	ACLL completed with minor loss due to LazyCommit while performing switchover on …	Operational	N
2009	Prior to mounting database 'DatabaseName' possible loss due LazyCommit was …	Operational	N
2010	Prior to mounting database 'DatabaseName' possible loss due LazyCommit could not …	Operational	N
2011	After mounting database 'DatabaseName' redelivery was performed for possible …	Operational	N
2012	After mounting database 'DatabaseName' possible loss due LazyCommit could not be …	Operational	N
2013	ACLL failed for database 'DatabaseName'.	Operational	N
2014	Database 'DatabaseName' cannot be moved because the active copy on server …	Operational	N
2015	Sent CAFE notification to endpoint Endpoint (json: 'JsonPayload').	Operational	N
2016	Failed CAFE notification to endpoint Endpoint (json: 'JsonPayload').	Operational	N
2017	InvokeWithTimeout perf: MaxDelay MaxDelayInUsec uSec.	Operational	N
2018	ThreadPool: CurrentWorkers CurrentWorkerThreads.	Operational	N
2019	SafetyNet request 'StoreValueName' for database 'DatabaseName' failed to …	Operational	N
2020	SafetyNet request 'StoreValueName' for database 'DatabaseName' has expired.	Operational	N
2021	SafetyNet for database 'DatabaseName' failed due to a serialization error: …	Operational	N
2022	The local copy of database 'DatabaseName' was marked Disconnected but BlockMode …	Operational	N
2023	The local copy of database 'DatabaseName' has entered BlockMode Replication.	BlockReplication	N
2024	Passive BlockMode for database 'DatabaseName' failed to receive a response from …	BlockReplication	N
2025	Passive BlockMode for database 'DatabaseName' failed to ping active ActiveServer …	BlockReplication	N
2026	Passive BlockMode for database 'DatabaseName' failed to initialize.	BlockReplication	N
2027	Passive BlockMode for database 'DatabaseName' failed to read data.	BlockReplication	N
2028	Passive BlockMode for database 'DatabaseName' failed due to a local consumer …	BlockReplication	N
2029	FileIOErrorOnSource for database 'DatabaseName': Corrupt: TreatedAsCorrupt.	Operational	N
2030	The copy of 'DatabaseName' has a loss window from LossStart to LossEnd.	Operational	N
2031	The copy of 'DatabaseName' has a loss window from LossStart to LossEnd that is …	Operational	N
2032	LossVerification during IncrementalReseed failed: Error.	Operational	N
2033	SetBlockFlags failed during failure item processing for database 'DatabaseName' …	Operational	N
2034	Incremental Reseed failed for database 'DatabaseName' because DivergenceInLogs …	Operational	N
2035	Incremental Reseed failed for database 'DatabaseName' because LogsToCopy logs …	Operational	N
2036	MonitoredDatabase for database 'DatabaseName' is starting.	Operational	N
2037	MonitoredDatabase for database 'DatabaseName' has started.	Operational	N
2038	The active copy for database 'DatabaseGuid' could not be determined: Error.	Operational	N
2039	The configuration for the local copy of database 'DatabaseName' could not be …	Operational	N
2040	The active copy for database 'DatabaseName' is ActiveCopy.	Debug	N
2041	A network error happened at LocationTag: Error.	Debug	N
2042	A network timeout happened at LocationTag: Error.	Debug	N
2043	The secondary database partition 'SecondaryEdbFilePath' of database …	Operational	N
2050	Suspend log replay requested for database guid=DatabaseGuid, …	Operational	N
2051	Suspend log replay for database guid=DatabaseGuid succeeded.	Operational	N
2052	Suspend log replay for database guid=DatabaseGuid failed: Message.	Operational	N
2053	Resume log replay requested for database guid=DatabaseGuid.	Operational	N
2054	Resume log replay for database guid=DatabaseGuid succeeded.	Operational	N
2055	Resume log replay for database guid=DatabaseGuid failed: Message.	Operational	N
2056	RedundancySensorError component encountered an error: Message.	Operational	N
2057	Loss redelivery after incremental reseed for database 'DatabaseName' failed: …	Operational	N
2058	The copy of 'DatabaseName' has a loss window from LossStart to LossEnd for which …	Operational	N
2059	The DAG is configured with ActivityState 'DagActivityState' so the …	Operational	N
2060	The passive copy of 'DatabaseName' has stopped with last log copied at …	Debug	N
2061	The LogCopier for 'DatabaseName' halted communication after ACLL.	Debug	N
2062	The active copy for database DatabaseGuid ignored CircularLogging because there …	Operational	N
2063	Move back to server 'TargetServerName' completed.	Operational	N
2064	Move back to server 'TargetServerName' timed out after ElapsedTime.	Operational	N
2065	Microsoft Exchange Server Locator Service failed to find active server for …	Debug	N
2066	Microsoft Exchange Server Locator Service failed to find active servers for the …	Operational	N
2070	Active Manager configuration refresh failed.	Operational	N
2071	Active manager skipped initiating failover for a NodeName due to nodedown event …	Operational	N
2072	Active manager skipped initiating failover for a NodeName due to nodedown …	Operational	N
2073	Active manager skipped dismounting all locally mounted databases for …	Operational	N
2074	Loose truncation on database DatabaseGuid was performed due to low space.	TruncationDebug	N
2075	Truncation on database DatabaseGuid is being performed.	TruncationDebug	N
2076	Loose truncation on database DatabaseGuid was performed due to excess log …	TruncationDebug	N
2077	Microsoft Exchange Server Locator Service Logger failed to commit log …	Monitoring	N
2078	Rebalance for CPU found work.	Debug	N
2079	Rebalance for CPU ignored database 'DatabaseName' because: Reason.	Debug	N
2080	Rebalance for CPU moved database 'DatabaseName' from OldActive to NewActive.	Debug	N
2081	Rebalance for CPU timed out after Timeout.	Debug	N
2082	Forced mount for database 'DatabaseName' failed.	Operational	N
2083	Forced mount for database 'DatabaseName' is being attempted.	Operational	N
2084	Forced mount for database 'DatabaseName' checked server ServerChecked to …	Operational	N
2090	Database move supporting operations performance details.	Operational	N
2091	Global truncation for 'DatabaseName' on active ActiveServer took Duration.	Operational	N
2092	LogCopier for database 'DatabaseName' connected to active ActiveServer detected …	Operational	N
2093	TcpStats report from Context=Context.	Operational	N
2094	TcpStats internal failure.	Operational	N
2095	LogCopyServer for database 'DatabaseName' sending data to passive PassiveServer …	Operational	N
2096	ListMDBStatus for server Server failed while hosting actives=HostingActives with …	Operational	N
2097	Local copy of database 'DatabaseName' was hung for …	Operational	N
2098	Log 'FileName' failed to open after 'DurationOfOpen' with error Exception.	Operational	N
2099	Dismount database 'DatabaseName' attempted from CallerContext.	Operational	N
2100	The Message1 has been Message2.	Operational	N
2101	The callback to update Network Throttling configuration failed with: Message1.	Operational	N
2102	The IsPrimaryTable operation from Azure storage table (IsPrimary:IsPrimaryTable) …	Operational	N
2103	The operation to retrieve the storage configuration from Torus Secret failed …	Operational	N
2104	Operation:Operation; SourceLocation:SourceLocation; …	Monitoring	N
2130	Restart RI for database 'DatabaseName' requested.	Debug	N
2131	RI for database 'DatabaseName' has been selected for restart.	Debug	N
2132	Component 'ComponentName' instance 'InstanceName' stopped after 'StopDuration'.	Debug	N
2133	Registry value EnableCounterForIoctl could not be set.	Monitoring	N
2134	There was an error reading disk performance data.	Monitoring	N
2135	Restart RI for database 'DatabaseName' has been deferred.	Debug	N
2136	ReplayDiagnosticsHandler failed to start: Message.	Operational	N
2137	Lossy ACLL for database 'DatabaseName' contacted SourceNode to check for …	Operational	N
2138	Lossy ACLL for database 'DatabaseName' running on RequestingNode contacted this …	Operational	N
2139	Lossy ACLL for database 'DatabaseName' used BlockMode generation Generation.	Operational	N
2140	The attempt to truncate local logs for database 'DatabaseName' failed: …	Operational	N
2141	The ServiceName service is starting.	Operational	N
2142	The Message service is stopping without waiting for an incomplete startup to …	Operational	N
2143	An override was used to configure the copy of 'DatabaseName' as Role.	Operational	N
2144	Probing file 'FileName' failed.	Operational	N
2145	ACLL driven dismount database 'DatabaseName' succeeded after Duration.	Operational	N
2146	ACLL driven dismount database 'DatabaseName' failed after Duration.	Operational	N
2147	ACLL driven dismount database 'DatabaseName' failed due to timeout after …	Operational	N
2148	ACLL probe of the EDB for 'DatabaseName' took DurationInMicrosec microseconds.	Debug	N
2149	ProcessAffinity for ServiceName was set successfully=SuccessfullySet.	Operational	N
2500	Attempted to upgrade FPGA image from version RpdVersionOnFlash to …	Operational	N
2501	An attempt to initialize the FPGA was abandoned because the service is stopping.	Operational	N
2502	An exception was thrown while trying to perform an operation on the FPGA.	Operational	N
2503	Operation failed with error: ErrorCode.	Operational	N
2504	FpgaCoreLib.	Operational	N
3000	Microsoft Exchange Server 'RequestingMachineName' initiated bug check for server …	Operational	N
3001	Triggered Active manager configuration refresh since PAM change notification …	Operational	N
3002	Received PAM change notification received from server 'ReportingServer' but …	Operational	N
3003	The DB copies 'DBNames' on Volume with volume id 'VolumeId' have been forcefully …	Seeding	N
3004	The volume 'VolumeId' was forcefully formatted.	Seeding	N
3005	Message.	Seeding	N
3006	Found an empty encrypted NTFS spare : VolumeId.	Seeding	N
3007	Message.	Seeding	N
3008	Found a potential ReFS volume for force dismount : VolumeId.	Seeding	N
3009	ReFStoNTFS reformat failed server prereqs for failed and suspended, seeding …	Seeding	N
3010	ReFStoNTFS reformat failed dag prereqs for failed and suspended, seeding copies: …	Seeding	N
3013	Avg FFB on DatabaseName was AvgLatencyInMsec mSec.	Debug	N
3014	Full reseed for database 'DatabaseName\MachineName' finished.	Operational	N
3015	Disk monitor component [Message] started.	Operational	N
3016	Disk monitor component [Message] Succeed.	Operational	N
3017	Disk monitor component [Message] Failed: StackTrace.	Operational	N
3018	Disk [Message1]: partition access paths: Message2, the expected protected status …	Operational	N
3019	FQDN resolution failed for server ServerName with error : Message.	Operational	N
3020	CallSite encountered SerializationException with a message of : …	Debug	N
9000	The Disk Reclaimer used-only encrypted volume 'VolumeName' mounted at …	Operational	N
9001	The Disk Reclaimer failed to used-only encrypt volume 'VolumeName' mounted at …	Operational	N
9002	The Disk Reclaimer couldn't find any empty spare volumes to encrypt.	Operational	N
9003	The Disk Reclaimer found 'VolumeCount' candidates for Encryption.	Operational	N
9004	The Disk Reclaimer successfully used-only encrypted 'SuccessCount' Empty volumes …	Operational	N
9005	Unable to get Win32_EncryptableVolume object for volume : 'SuccessCount' due to …	Operational	N
9006	The Disk Reclaimer skipped encrypting empty Win8 volumes.	Operational	N
9007	Volume 'VolumeName' is mounted on a virtual disk.	Operational	N
9008	The Disk Reclaimer skipped calling Bitlocker Maintenance as the config is …	Operational	N
9009	he Disk Reclaimer failed to start full volume encryption for volume 'VolumeName' …	Operational	N
9010	The Disk Reclaimer started full volume encryption for volume 'VolumeName' …	Operational	N
9012	The Disk Reclaimer successfully started full volume encryption on volume …	Operational	N
9014	The Disk Reclaimer skipped encrypting empty Win7 volumes.	Operational	N
9016	Bitlocker Encryption Percentage for volume 'VolumeName' is at …	Operational	N
9017	The Disk Reclaimer is calling Win7 encryption method in BitlockerHelper.	Operational	N
9019	The Disk Reclaimer is calling Win8 encryption method in BitlockerHelper.	Operational	N
9021	Bitlocker Encryption failed for mountpoint 'MountPoint' volume 'VolumeName' due …	Operational	N

Event ID 100: Initiating startup automount.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating startup automount.

Event ID 101: Initiating automount due to store start on server 'ServerFqdn'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating automount due to store start on server 'ServerFqdn'

Fields #

Name	Description
`ServerFqdn`

Event ID 103: Active Manager started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager started

Event ID 104: Active Manager start postponed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager start postponed

Event ID 105: Active Manager stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager stopped

Event ID 106: ACLL failed while performing switchover on shutdown for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL failed while performing switchover on shutdown for database 'DatabaseName'

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 107: Lossy mount enabled for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Lossy mount enabled for database 'DatabaseName'

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 108: Mount rejected for database 'DatabaseName' since data loss exceeds configured limits.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mount rejected for database 'DatabaseName' since data loss exceeds configured limits

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 109: Role monitor started with role 'Role'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Role monitor started with role 'Role'

Fields #

Name	Description
`Role`

Event ID 110: Cluster node state change detected for node 'NodeNameFqdn' (Node state='NodeState').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster node state change detected for node 'NodeNameFqdn' (Node state='NodeState')

Fields #

Name	Description
`NodeNameFqdn`
`NodeState`

Event ID 111: Active manager role changed from 'PreviousRole' to 'CurrentRole'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager role changed from 'PreviousRole' to 'CurrentRole'

Fields #

Name	Description
`CurrentRole`
`PreviousRole`

Event ID 112: Database 'DatabaseName' is attempting to mount on server 'ServerFqdn'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' is attempting to mount on server 'ServerFqdn'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerFqdn`
`MountFlags`
`MountDialOverride`
`TryOtherServers`
`ActionCode`

Event ID 113: Database 'DatabaseName' failed to mount on server 'ServerFqdn' with error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to mount on server 'ServerFqdn' with error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerFqdn`
`ErrorMessage`

Event ID 114: Database 'DatabaseName' mounted successfully on server 'ServerFqdn'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' mounted successfully on server 'ServerFqdn'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerFqdn`

Event ID 118: Database 'DatabaseName' is attempting to move to 'ToServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' is attempting to move to 'ToServer'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ToServer`
`FromServer`
`MountFlags`
`DismountFlags`
`MountDialOverride`
`TryOtherServers`
`ActionCode`

Event ID 119: Database 'DatabaseName' failed to move to 'ToServer' with error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to move to 'ToServer' with error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ToServer`
`ErrorMessage`

Event ID 120: Database 'DatabaseName' moved successfully to 'ToServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' moved successfully to 'ToServer'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ToServer`

Event ID 121: Direct mount operation failed for database (Guid=DatabaseGuid, Error=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Direct mount operation failed for database (Guid=DatabaseGuid, Error=ErrorMessage)

Fields #

Name	Description
`DatabaseGuid`
`ErrorMessage`

Event ID 122: Direct dismount operation failed for database (Guid=DatabaseGuid, Error=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Direct dismount operation failed for database (Guid=DatabaseGuid, Error=ErrorMessage)

Fields #

Name	Description
`DatabaseGuid`
`ErrorMessage`

Event ID 123: Switchover on shutdown initated for server 'SourceServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Switchover on shutdown initated for server 'SourceServer'

Fields #

Name	Description
`SourceServer`

Event ID 124: Switchover on shutdown failed for server 'SourceServer' with error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Switchover on shutdown failed for server 'SourceServer' with error: ErrorMessage

Fields #

Name	Description
`SourceServer`
`ErrorMessage`

Event ID 125: Switchover on shutdown successfully completed for server 'SourceServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Switchover on shutdown successfully completed for server 'SourceServer'

Fields #

Name	Description
`SourceServer`

Event ID 126: Server operation generated unhandled exception (Exception=ExceptionString).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Server operation generated unhandled exception (Exception=ExceptionString)

Fields #

Name	Description
`ExceptionString`

Event ID 127: Forcefully dismounting all the locally mounted databases on server 'ServerFqdn' (Reason: Reason).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Forcefully dismounting all the locally mounted databases on server 'ServerFqdn' (Reason: Reason).

Fields #

Name	Description
`ServerFqdn`
`Reason`

Event ID 128: Service monitor detected that 'Service' service is now running.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Service monitor detected that 'Service' service is now running.

Fields #

Name	Description
`Service`

Event ID 129: Service monitor detected that 'Service' service is now stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Service monitor detected that 'Service' service is now stopped.

Fields #

Name	Description
`Service`

Event ID 130: Store service start detected but configuration is currently invalid.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Store service start detected but configuration is currently invalid

Event ID 131: The FacilityDescription has been successfully initialized.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The FacilityDescription has been successfully initialized.

Fields #

Name	Description
`FacilityDescription`

Event ID 132: Failure item notification registration for database 'DatabaseName' failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failure item notification registration for database 'DatabaseName' failed. (error=ErrorMessage)

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 133: Finished startup automount (AttemptedMounts=MountedCount, AttemptedDismounts=DismountedCount, AttemptedDbSyncs=DbSyncedCount,AttemptedMoves=MoveCount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished startup automount (AttemptedMounts=MountedCount, AttemptedDismounts=DismountedCount, AttemptedDbSyncs=DbSyncedCount,AttemptedMoves=MoveCount).

Fields #

Name	Description
`MountedCount`
`DismountedCount`
`DbSyncedCount`
`MoveCount`

Event ID 134: Finished automounting due to store start (Node=NodeName, AttemptedMounts=MountedCount, AttemptedDismounts=DismountedCount, AttemptedDbSyncs=DbSyncedCount,AttemptedMoves=MoveCount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished automounting due to store start (Node=NodeName, AttemptedMounts=MountedCount, AttemptedDismounts=DismountedCount, AttemptedDbSyncs=DbSyncedCount,AttemptedMoves=MoveCount).

Fields #

Name	Description
`NodeName`
`MountedCount`
`DismountedCount`
`DbSyncedCount`
`MoveCount`

Event ID 135: Finished failover (Node=NodeName, Databases=DatabaseCount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished failover (Node=NodeName, Databases=DatabaseCount).

Fields #

Name	Description
`NodeName`
`DatabaseCount`

Event ID 136: Finished switchover (Node=NodeName, Databases=DatabaseCount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished switchover (Node=NodeName, Databases=DatabaseCount).

Fields #

Name	Description
`NodeName`
`DatabaseCount`

Event ID 137: Initiating server failover (Node=NodeName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating server failover (Node=NodeName).

Fields #

Name	Description
`NodeName`

Event ID 138: Initiating server switchover (Node=NodeName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating server switchover (Node=NodeName).

Fields #

Name	Description
`NodeName`

Event ID 139: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Message

Fields #

Name	Description
`Message`

Event ID 140: Mount rejected for database 'DatabaseName' since attempts to copy the last logs from the previous source server encountered an error (Error=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mount rejected for database 'DatabaseName' since attempts to copy the last logs from the previous source server encountered an error (Error=ErrorMessage)

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`

Event ID 141: Database 'DatabaseName' failed to mount (error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to mount (error: ErrorMessage)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 142: Database 'DatabaseName' failed to dismount (error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to dismount (error: ErrorMessage)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 143: Database 'DatabaseName' failed to move (error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to move (error: ErrorMessage)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 144: Active Manager skipped automounting database 'DatabaseName' since MountAtStartup is set to false.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager skipped automounting database 'DatabaseName' since MountAtStartup is set to false

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`

Event ID 145: Active Manager skipped automounting database 'DatabaseName' since it was admin dismounted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager skipped automounting database 'DatabaseName' since it was admin dismounted

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`

Event ID 146: ReplayState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node 'NodeName' changed from 'OldValue' to 'NewValue'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ReplayState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node 'NodeName' changed from 'OldValue' to 'NewValue'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`NodeName`
`StateName`
`OldValue`
`NewValue`

Event ID 147: Database 'DatabaseName' cannot be activated on possible target server 'PossibleServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' cannot be activated on possible target server 'PossibleServer'. Reason: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PossibleServer`
`ErrorMessage`

Event ID 148: Database 'DatabaseName' cannot be activated on any server because none of their copy status healths could be determined.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' cannot be activated on any server because none of their copy status healths could be determined.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`

Event ID 149: An error occurred while trying to select database copy 'DatabaseName' on server 'PossibleServer' for possible activation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An error occurred while trying to select database copy 'DatabaseName' on server 'PossibleServer' for possible activation. The following checks were run: 'ChecksRun'. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PossibleServer`
`ChecksRun`
`ErrorMessage`
`OperationId`
`CheckThatFailed`

Event ID 150: Database copy 'DatabaseName' on server 'PossibleServer' has been selected for possible activation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database copy 'DatabaseName' on server 'PossibleServer' has been selected for possible activation. The following checks were run: 'ChecksRun'.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PossibleServer`
`ChecksRun`
`OperationId`

Event ID 151: An error occurred while trying to validate the specified database copy 'DatabaseName' on server 'TargetServer' for possible activation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An error occurred while trying to validate the specified database copy 'DatabaseName' on server 'TargetServer' for possible activation. The following checks were run: 'ChecksRun'. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`TargetServer`
`ChecksRun`
`ErrorMessage`
`OperationId`

Event ID 152: Database copy 'DatabaseName' on specified server 'TargetServer' has passed activation validation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database copy 'DatabaseName' on specified server 'TargetServer' has passed activation validation. The following checks were run: 'ChecksRun'.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`TargetServer`
`ChecksRun`
`OperationId`

Event ID 153: ACLL completed without loss while performing switchover on shutdown for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL completed without loss while performing switchover on shutdown for database 'DatabaseName'

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 154: ACLL completed without loss for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL completed without loss for database 'DatabaseName'

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 155: Database 'DatabaseName' successfully copied the last logs to server 'ToServer' from server 'SourceServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' successfully copied the last logs to server 'ToServer' from server 'SourceServer'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ToServer`
`SourceServer`

Event ID 156: Database property update failed on local site (db='DatabaseName', localSite='LocalSiteDN', error='Error').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database property update failed on local site (db='DatabaseName', localSite='LocalSiteDN', error='Error')

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`LocalSiteDN`
`Error`

Event ID 157: Database property remote replication request failed (db='DatabaseName', sites='SiteDNList', DcsContacted='DcsContactedList', error='Error').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database property remote replication request failed (db='DatabaseName', sites='SiteDNList', DcsContacted='DcsContactedList', error='Error')

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`SiteDNList`
`DcsContactedList`
`Error`

Event ID 158: Database property remote replication request succeeded (db='DatabaseName', sites='SiteDNList', DcsContacted='DcsContactedList').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database property remote replication request succeeded (db='DatabaseName', sites='SiteDNList', DcsContacted='DcsContactedList')

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`SiteDNList`
`DcsContactedList`

Event ID 159: Store service is stopped on node 'NodeName' and all the database which were active on that server were marked as Dismounted (count=Count).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Store service is stopped on node 'NodeName' and all the database which were active on that server were marked as Dismounted (count=Count)

Fields #

Name	Description
`NodeName`
`Count`

Event ID 160: There seems to be a database operation which is already in progress.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

There seems to be a database operation which is already in progress. Mount operation will be delayed until the previous operation is complete (databaseGuid='DatabaseGuid', error='Error')

Fields #

Name	Description
`DatabaseGuid`
`Error`

Event ID 161: There seems to be a database operation which is already in progress.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

There seems to be a database operation which is already in progress. Dismount operation will be delayed until the previous operation is complete (databaseGuid='DatabaseGuid', error='Error')

Fields #

Name	Description
`DatabaseGuid`
`Error`

Event ID 162: Database 'DatabaseName' copied the last logs to server 'ToServer' from server 'SourceServer' with some potential data loss.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' copied the last logs to server 'ToServer' from server 'SourceServer' with some potential data loss

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ToServer`
`SourceServer`

Event ID 163: The attempt to copy remaining uncopied logs failed for database Database.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The attempt to copy remaining uncopied logs failed for database Database. Error: ErrorMessage

Fields #

Name	Description
`Database`
`ErrorMessage`

Event ID 164: Databases are being marked as dismounted because the store was stopped on server 'NodeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Databases are being marked as dismounted because the store was stopped on server 'NodeName'.

Fields #

Name	Description
`NodeName`

Event ID 165: Database DatabaseName on server ServerFqdn is being dismounted because it's not the current active server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database DatabaseName on server ServerFqdn is being dismounted because it's not the current active server.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerFqdn`

Event ID 166: The batch mounter operation failed with error ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The batch mounter operation failed with error ErrorMessage.

Fields #

Name	Description
`ErrorMessage`

Event ID 167: Best copy selection for database 'DatabaseName' failed to get the database availability group.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Best copy selection for database 'DatabaseName' failed to get the database availability group. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 168: Active manager did not perform an action for server 'ServerName' since debug option 'DebugOption' is set (Hint: Hint).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager did not perform an action for server 'ServerName' since debug option 'DebugOption' is set (Hint: Hint)

Fields #

Name	Description
`ServerName`
`DebugOption`
`Hint`

Event ID 169: Debug options settings are enabled on this Database availability group.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Debug options settings are enabled on this Database availability group.

Event ID 170: Log TruncationState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node 'NodeName' changed from 'OldValue' to 'NewValue'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Log TruncationState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node 'NodeName' changed from 'OldValue' to 'NewValue'

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`NodeName`
`StateName`
`OldValue`
`NewValue`

Event ID 171: Active manager received system event EventCode from server ServerReporting.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager received system event EventCode from server ServerReporting.

Fields #

Name	Description
`EventCode`
`ServerReporting`

Event ID 172: Persistent state of database DatabaseName is synchronized.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Persistent state of database DatabaseName is synchronized. (PreviousState: PreviousMountStatus, NewState: NewMountStatus)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PreviousMountStatus`
`NewMountStatus`
`ActiveServer`

Event ID 173: Active directory properties of database DatabaseName is synchronized.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active directory properties of database DatabaseName is synchronized. (PreviousOwningServer: InitialOwningServer, NewActiveServer: NewActiveServer)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`InitialOwningServer`
`NewActiveServer`

Event ID 174: The cluster group is hosted on this server but the current role is Unknown.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The cluster group is hosted on this server but the current role is Unknown. An attempt will be made to move the group.

Event ID 175: The cluster group was already moved.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The cluster group was already moved. It is now hosted on server 'NodeName'.

Fields #

Name	Description
`NodeName`

Event ID 176: This server is now running as 'Role'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

This server is now running as 'Role'.

Fields #

Name	Description
`Role`

Event ID 177: The cluster group is being moved to server 'NodeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The cluster group is being moved to server 'NodeName'.

Fields #

Name	Description
`NodeName`

Event ID 178: The cluster group was successfully moved to server 'NodeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The cluster group was successfully moved to server 'NodeName'.

Fields #

Name	Description
`NodeName`

Event ID 179: The cluster group failed to move to server 'NodeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The cluster group failed to move to server 'NodeName'. Message

Fields #

Name	Description
`NodeName`
`Message`

Event ID 180: An error was encounted accessing the cluster'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An error was encounted accessing the cluster'. Message

Fields #

Name	Description
`Message`

Event ID 181: No new cluster owner could be found.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

No new cluster owner could be found.

Event ID 182: Active Directory access has failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Directory access has failed. This has been recorded in the cluster database.

Event ID 183: Active Directory access is now functioning properly.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Active Directory access is now functioning properly. This has been recorded in the cluster database.

Event ID 184: Node status could not be recorded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Node status could not be recorded. This could prevent some network failure logic from functioning correctly. NodeStatus:Message1 Failure:Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 185: Mapi access to this node may be broken.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mapi access to this node may be broken.

Event ID 186: Mapi access to this node is expected to be operational because windows clustering is reporting the network as healthy.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mapi access to this node is expected to be operational because windows clustering is reporting the network as healthy.

Event ID 187: Mapi access to this node is expected to be operational because Active Directory can be accessed by this node.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mapi access to this node is expected to be operational because Active Directory can be accessed by this node.

Event ID 188: Initiating move of all active databases (Node=NodeName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating move of all active databases (Node=NodeName).

Fields #

Name	Description
`NodeName`

Event ID 189: Finished moving all active databases (Node=NodeName, Databases=DatabaseCount, MoveComment=MoveComment).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished moving all active databases (Node=NodeName, Databases=DatabaseCount, MoveComment=MoveComment).

Fields #

Name	Description
`NodeName`
`DatabaseCount`
`MoveComment`

Event ID 190: Moving all active databases failed for server 'SourceServer' (MoveComment: MoveComment, Error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Moving all active databases failed for server 'SourceServer' (MoveComment: MoveComment, Error: ErrorMessage).

Fields #

Name	Description
`SourceServer`
`ErrorMessage`
`MoveComment`

Event ID 191: Database 'DatabaseName' cannot be activated on server 'ServerName' because the RPC to retrieve the copy status health failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' cannot be activated on server 'ServerName' because the RPC to retrieve the copy status health failed. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerName`
`ErrorMessage`

Event ID 192: Suspend requested for database guid=DatabaseGuid, comment='SuspendComment', flags='SuspendFlags', initiator='Initiator'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend requested for database guid=DatabaseGuid, comment='SuspendComment', flags='SuspendFlags', initiator='Initiator'.

Fields #

Name	Description
`DatabaseGuid`
`SuspendComment`
`SuspendFlags`
`Initiator`

Event ID 193: Suspend database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 194: Suspend database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 195: Resume requested for database guid=DatabaseGuid, flags='ResumeFlags'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume requested for database guid=DatabaseGuid, flags='ResumeFlags'.

Fields #

Name	Description
`DatabaseGuid`
`ResumeFlags`

Event ID 196: Resume database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 197: Resume database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 198: BeginSeed requested for database guid=DatabaseGuid, args='SeedArgs'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

BeginSeed requested for database guid=DatabaseGuid, args='SeedArgs'.

Fields #

Name	Description
`DatabaseGuid`
`SeedArgs`

Event ID 199: BeginSeed database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

BeginSeed database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 200: BeginSeed database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

BeginSeed database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 201: CancelSeed requested for database guid=DatabaseGuid.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

CancelSeed requested for database guid=DatabaseGuid.

Fields #

Name	Description
`DatabaseGuid`

Event ID 202: CancelSeed database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

CancelSeed database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 203: CancelSeed database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

CancelSeed database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 204: ExSearch Operation requested for database guid=DatabaseGuid on server 'Server'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ExSearch Operation requested for database guid=DatabaseGuid on server 'Server'.

Fields #

Name	Description
`DatabaseGuid`
`Operation`
`Server`

Event ID 205: ExSearch Operation for database guid=DatabaseGuid on server 'Server' succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ExSearch Operation for database guid=DatabaseGuid on server 'Server' succeeded.

Fields #

Name	Description
`DatabaseGuid`
`Operation`
`Server`

Event ID 206: ExSearch Operation for database 'DatabaseName' (DatabaseGuid) on server 'Server' failed: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ExSearch Operation for database 'DatabaseName' (DatabaseGuid) on server 'Server' failed: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Operation`
`Server`
`ErrorMessage`

Event ID 207: Incremental Reseed (DatabaseName\ServerName) determined logs are diverged from gen Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) determined logs are diverged from gen Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 208: Incremental Reseed (DatabaseName\ServerName) started copying logs from gen Message1 to gen Message2 from the source.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) started copying logs from gen Message1 to gen Message2 from the source.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 209: Incremental Reseed (DatabaseName\ServerName) decided the local copy will have a required log range from Message1-Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) decided the local copy will have a required log range from Message1-Message2.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 210: Incremental Reseed (DatabaseName\ServerName) has started to patch the local copy.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) has started to patch the local copy.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 211: Incremental Reseed (DatabaseName\ServerName) reused the patch file.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) reused the patch file.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 212: Incremental Reseed (DatabaseName\ServerName) patched Message1 pages to the local copy which has a total of Message2 pages (including header page).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) patched Message1 pages to the local copy which has a total of Message2 pages (including header page)

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 213: Incremental Reseed (DatabaseName\ServerName) replaced logs from gen Message1 to gen Message2 in dir Message3.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) replaced logs from gen Message1 to gen Message2 in dir Message3

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`
`Message3`

Event ID 214: Incremental Reseed (DatabaseName\ServerName) found a page number Message1 exceeding the current database size of Message2 pages.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) found a page number Message1 exceeding the current database size of Message2 pages

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 215: Incremental Reseed (DatabaseName\ServerName) ignored the IsamFileIOBeyondEOFException while patching page Message1 on a database with a total of Message2 pages.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) ignored the IsamFileIOBeyondEOFException while patching page Message1 on a database with a total of Message2 pages (including header page)

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 216: An error was encountered while processing a failure item for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An error was encountered while processing a failure item for database 'DatabaseName'. The attempt to suspend the local copy failed: Message

Fields #

Name	Description
`DatabaseName`
`Message`

Event ID 217: An unrecoverable error on database 'DatabaseName' was encountered that triggered a clean dismount attempt.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An unrecoverable error on database 'DatabaseName' was encountered that triggered a clean dismount attempt. This dismount failed: Message

Fields #

Name	Description
`DatabaseName`
`Message`

Event ID 218: ACLL for database 'DatabaseName' failed due to a timeout while waiting to control the log copier.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL for database 'DatabaseName' failed due to a timeout while waiting to control the log copier.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 219: During ACLL the log copier for database 'DatabaseName' had to cleanup a preexisting failed connection.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

During ACLL the log copier for database 'DatabaseName' had to cleanup a preexisting failed connection. A new connection will be attempted.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 220: Incremental Reseed (DatabaseName\ServerName) V1 is going to be performed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) V1 is going to be performed. Generations Required:Message1-Message2, divergence point(the generation that log files are diverged):Message3.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`
`Message3`

Event ID 221: Truncation context opened for database 'DatabaseName' from server 'ServerName' with circular logging option 'Message1'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Truncation context opened for database 'DatabaseName' from server 'ServerName' with circular logging option 'Message1'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 222: Truncation context failed to open for database 'DatabaseName' from server 'ServerName' with reason: 'Message1'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Truncation context failed to open for database 'DatabaseName' from server 'ServerName' with reason: 'Message1'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 223: Database 'DatabaseGuid' from server 'PassiveServerName' reported ok to truncate 'GenToPreserve'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Database 'DatabaseGuid' from server 'PassiveServerName' reported ok to truncate 'GenToPreserve'. Local active requires gen 'LocalGenRequired'.

Fields #

Name	Description
`DatabaseGuid`
`PassiveServerName`
`GenToPreserve`
`LocalGenRequired`

Event ID 224: Global truncation point for database 'DatabaseName' found minimum gen 'Message1' due to server 'ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Global truncation point for database 'DatabaseName' found minimum gen 'Message1' due to server 'ServerName'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 225: Log files for database 'Message1' deleted from 'Message2' to 'Message3'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Log files for database 'Message1' deleted from 'Message2' to 'Message3'.

Fields #

Name	Description
`Message1`
`Message2`
`Message3`

Event ID 226: Disposed database 'Message' info from global list.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Disposed database 'Message' info from global list.

Fields #

Name	Description
`Message`

Event ID 227: Active manager configuration change detected.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager configuration change detected. (PreviousRole='PreviousRole', CurrentRole='CurrentRole', ChangeFlags='ChangeFlags', LastError='LastError')

Fields #

Name	Description
`CurrentRole`
`PreviousRole`
`ChangeFlags`
`LastError`

Event ID 228: Database copy 'DatabaseName\ServerName' was in a clean state and was successfully marked dirty.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database copy 'DatabaseName\ServerName' was in a clean state and was successfully marked dirty.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 229: Database copy 'DatabaseName\ServerName' failed to redirty because: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database copy 'DatabaseName\ServerName' failed to redirty because: Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 230: The log was rolled for database copy 'DatabaseName\ServerName' to allow granular replication.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The log was rolled for database copy 'DatabaseName\ServerName' to allow granular replication.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 231: The attempt to roll the log for database copy 'DatabaseName\ServerName' failed: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The attempt to roll the log for database copy 'DatabaseName\ServerName' failed: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 232: During ACLL for database copy 'DatabaseName\ServerName' granular logs were used from generation LowGeneration to HighGeneration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

During ACLL for database copy 'DatabaseName\ServerName' granular logs were used from generation LowGeneration to HighGeneration.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`LowGeneration`
`HighGeneration`

Event ID 233: The attempt to use granular logs during ACLL for database copy 'DatabaseName\ServerName' failed: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The attempt to use granular logs during ACLL for database copy 'DatabaseName\ServerName' failed: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 234: Granular replication on database copy 'DatabaseName\ServerName' failed to validate log 'Message1'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Granular replication on database copy 'DatabaseName\ServerName' failed to validate log 'Message1'. The error was: Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 235: BatchMounter operations are disabled since registry parameter 'AmDisableBatchOperations' is enabled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

BatchMounter operations are disabled since registry parameter 'AmDisableBatchOperations' is enabled.

Event ID 236: Granular replication on database copy 'DatabaseName\ServerName' detected log corruption on 'Message1' and will attempt automatic repair.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Granular replication on database copy 'DatabaseName\ServerName' detected log corruption on 'Message1' and will attempt automatic repair. The error that triggered this action was : Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 237: Granular replication on database copy 'DatabaseName\ServerName' successfully repaired log corruption on 'Message1'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Granular replication on database copy 'DatabaseName\ServerName' successfully repaired log corruption on 'Message1'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 238: Granular replication on database copy 'DatabaseName\ServerName' failed to repair log corruption on 'Message1'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Granular replication on database copy 'DatabaseName\ServerName' failed to repair log corruption on 'Message1'. The failure was due to: Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 239: During initialization of database copy 'DatabaseName\ServerName' logs were successfully inspected from generation LowGeneration to HighGeneration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

During initialization of database copy 'DatabaseName\ServerName' logs were successfully inspected from generation LowGeneration to HighGeneration.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`LowGeneration`
`HighGeneration`

Event ID 240: During initialization of database copy 'DatabaseName\ServerName' logs could not be preserved past generation FailedGeneration due to: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

During initialization of database copy 'DatabaseName\ServerName' logs could not be preserved past generation FailedGeneration due to: ErrorMessage.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`FailedGeneration`
`ErrorMessage`

Event ID 241: Detected stale last log generated information for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Detected stale last log generated information for database 'DatabaseName'. (LastUpdatedTime(UTC)=LastLogGenerationTimeStamp, Allowed duration=AllowedDuration, Actual duration=ActualDuration).

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`UniqueId`
`LastLogGenerationTimeStamp`
`AllowedDuration`
`ActualDuration`

Event ID 242: A new log for database copy 'DatabaseName\ServerName' was written to 'Message1' but an error accessing the file occurred: Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A new log for database copy 'DatabaseName\ServerName' was written to 'Message1' but an error accessing the file occurred: Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 243: The database copy 'DatabaseName\ServerName' was in an errored state but 'Mount-Database -Force' was used to override the error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The database copy 'DatabaseName\ServerName' was in an errored state but 'Mount-Database -Force' was used to override the error.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 244: The database copy 'DatabaseName\ServerName' was in an errored state but 'Move-ActiveMailboxDatabaseMove -SkipHealthChecks was used to override the error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The database copy 'DatabaseName\ServerName' was in an errored state but 'Move-ActiveMailboxDatabaseMove -SkipHealthChecks was used to override the error.

Fields #

Name	Description
`DatabaseName`
`ServerName`

Event ID 245: Block-mode replication for database copy 'DatabaseName\ServerName' released a range of complete but unfinalized logs from generation LowGen to HiGen.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Block-mode replication for database copy 'DatabaseName\ServerName' released a range of complete but unfinalized logs from generation LowGen to HiGen. The data is identical to the active copy but the file timestamps may differ by a small value.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`LowGen`
`HiGen`

Event ID 246: The attempt to seed database 'DatabaseName' from the active copy on server 'SourceServerName' to the copy on server 'TargetServerName' failed: ErrorMsg.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The attempt to seed database 'DatabaseName' from the active copy on server 'SourceServerName' to the copy on server 'TargetServerName' failed: ErrorMsg

Fields #

Name	Description
`DatabaseName`
`SourceServerName`
`TargetServerName`
`ErrorMsg`

Event ID 247: Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the active copy on server 'SourceServerName' to the copy on server 'TargetServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the active copy on server 'SourceServerName' to the copy on server 'TargetServerName'. Total bytes sent: TotalBytesSent. Duration of transfer: SendTimeSpan. Throughput: Thruput.

Fields #

Name	Description
`DatabaseName`
`SourceServerName`
`TargetServerName`
`TotalBytesSent`
`SendTimeSpan`
`Thruput`
`EdbFilePath`

Event ID 248: The attempt to seed database 'DatabaseName' from the passive copy on server 'SourceServerName' to the copy on server 'TargetServerName' failed: ErrorMsg.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The attempt to seed database 'DatabaseName' from the passive copy on server 'SourceServerName' to the copy on server 'TargetServerName' failed: ErrorMsg

Fields #

Name	Description
`DatabaseName`
`SourceServerName`
`TargetServerName`
`ErrorMsg`

Event ID 249: Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the passive copy on server 'SourceServerName' to the copy on server 'TargetServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Database file 'EdbFilePath' for database 'DatabaseName' was seeded from the passive copy on server 'SourceServerName' to the copy on server 'TargetServerName'. Total bytes sent: TotalBytesSent. Duration of transfer: SendTimeSpan. Throughput: Thruput.

Fields #

Name	Description
`DatabaseName`
`SourceServerName`
`TargetServerName`
`TotalBytesSent`
`SendTimeSpan`
`Thruput`
`EdbFilePath`

Event ID 250: Attempt to cause BugCheck failed with error 'ErrorMessage'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to cause BugCheck failed with error 'ErrorMessage'. (LastBootTime=LastBootTime, BugcheckReason=BugcheckReason)

Fields #

Name	Description
`ErrorMessage`
`LastBootTime`
`BugcheckReason`

Event ID 251: Skipped bugcheck due to reason: BugcheckSkippedReason (BugcheckReason=BugcheckReason).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Skipped bugcheck due to reason: BugcheckSkippedReason (BugcheckReason=BugcheckReason)

Fields #

Name	Description
`BugcheckReason`
`BugcheckSkippedReason`

Event ID 252: Failure item processing detected an inconsistent event record (Database=DatabaseName, IsEventPresent=IsEventPresent, Exception=Exception).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failure item processing detected an inconsistent event record (Database=DatabaseName, IsEventPresent=IsEventPresent, Exception=Exception)

Fields #

Name	Description
`DatabaseName`
`IsEventPresent`
`Exception`

Event ID 253: Incremental Reseed (DatabaseName\ServerName) determined that Message1 pages will need to be patched into the local copy which has a total of Message2 pages (including header page).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) determined that Message1 pages will need to be patched into the local copy which has a total of Message2 pages (including header page)

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 254: Incremental Reseed (DatabaseName\ServerName) finished copying logs from gen Message1 to gen Message2 from the source.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) finished copying logs from gen Message1 to gen Message2 from the source.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 255: Log verification for database copy 'DatabaseName\ServerName' failed on log file 'Message1': Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log verification for database copy 'DatabaseName\ServerName' failed on log file 'Message1': Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 256: File 'Message1' which is part of database copy 'DatabaseName\ServerName' was deleted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

File 'Message1' which is part of database copy 'DatabaseName\ServerName' was deleted.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`

Event ID 257: The database copy 'DatabaseName\ServerName' will require reseeding because the active on 'Message1' has diverged prior to generation Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The database copy 'DatabaseName\ServerName' will require reseeding because the active on 'Message1' has diverged prior to generation Message2.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 258: Initiating clean dismount of database 'DatabaseName' on 'ActiveServer' since it is marked as admin dismounted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating clean dismount of database 'DatabaseName' on 'ActiveServer' since it is marked as admin dismounted.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`

Event ID 259: Mount request for database 'DatabaseName' is rejected since system shutdown initated at 'ShutdownInitiatedTime' is in progress.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mount request for database 'DatabaseName' is rejected since system shutdown initated at 'ShutdownInitiatedTime' is in progress.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ShutdownInitiatedTime`

Event ID 260: Initiating Store Rpc to dismount database 'DatabaseGuid' on server 'ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating Store Rpc to dismount database 'DatabaseGuid' on server 'ServerName'.

Fields #

Name	Description
`ServerName`
`DatabaseGuid`
`Flags`
`RetryOnConflict`

Event ID 261: Finshed dismount Store Rpc for database 'DatabaseGuid' on server 'ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finshed dismount Store Rpc for database 'DatabaseGuid' on server 'ServerName'. DurableDismount=DurableDismount

Fields #

Name	Description
`ServerName`
`DatabaseGuid`
`ErrorMessage`
`DurableDismount`
`Duration`

Event ID 262: Finished force dismounting all locally mounted databases.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished force dismounting all locally mounted databases. (IsSuccess=IsSuccess)

Fields #

Name	Description
`IsSuccess`

Event ID 263: Initiating graceful crash of store process.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating graceful crash of store process.

Event ID 264: Finished graceful crash of store process.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished graceful crash of store process.

Fields #

Name	Description
`ErrorMessage`

Event ID 265: The FacilityDescription has been stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The FacilityDescription has been stopped.

Fields #

Name	Description
`FacilityDescription`

Event ID 266: BlockModeReplication is terminated on the active side because the passive copy 'DatabaseName\PassiveServerName' is not consuming data fast enough.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockModeReplication is terminated on the active side because the passive copy 'DatabaseName\PassiveServerName' is not consuming data fast enough.

Fields #

Name	Description
`DatabaseName`
`PassiveServerName`

Event ID 267: BlockModeReplication is terminated on the passive side for database 'DatabaseName' because the depth limit of DepthLimitInBytes bytes was reached.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockModeReplication is terminated on the passive side for database 'DatabaseName' because the depth limit of DepthLimitInBytes bytes was reached.

Fields #

Name	Description
`DatabaseName`
`DepthLimitInBytes`

Event ID 268: Active copy of database 'DatabaseName' on this server is now starting a seed for the passive copy on server TargetServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Active copy of database 'DatabaseName' on this server is now starting a seed for the passive copy on server TargetServer.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 269: Seed-from-active for database 'DatabaseName' to the passive copy on server TargetServer completed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seed-from-active for database 'DatabaseName' to the passive copy on server TargetServer completed.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 270: Seed-from-active for database 'DatabaseName' to the passive copy on server TargetServer was cancelled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seed-from-active for database 'DatabaseName' to the passive copy on server TargetServer was cancelled. Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 271: Passive copy of database 'DatabaseName' on this server is now starting a seed for the passive copy on server TargetServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Passive copy of database 'DatabaseName' on this server is now starting a seed for the passive copy on server TargetServer. If this is a database seed, log replay will be suspended for this copy and will be automatically resumed when the seed is completed or aborted.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 272: Seed-from-passive for database 'DatabaseName' to the passive copy on server TargetServer completed and log replay will be resumed for this copy.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seed-from-passive for database 'DatabaseName' to the passive copy on server TargetServer completed and log replay will be resumed for this copy.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 273: Seed-from-passive for database 'DatabaseName' to the passive copy on server TargetServer was cancelled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seed-from-passive for database 'DatabaseName' to the passive copy on server TargetServer was cancelled. Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 274: Active copy of database 'DatabaseName' on this server started reading database pages for Incremental Reseed of the passive copy on server TargetServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Active copy of database 'DatabaseName' on this server started reading database pages for Incremental Reseed of the passive copy on server TargetServer.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 275: Active copy of database 'DatabaseName' on this server finished reading database pages for Incremental Reseed of the passive copy on server TargetServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Active copy of database 'DatabaseName' on this server finished reading database pages for Incremental Reseed of the passive copy on server TargetServer.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 276: Disable replay lag requested for database guid=DatabaseGuid, reason='DisableReason'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disable replay lag requested for database guid=DatabaseGuid, reason='DisableReason'.

Fields #

Name	Description
`DatabaseGuid`
`DisableReason`

Event ID 277: Disable replay lag for database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disable replay lag for database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 278: Disable replay lag for database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disable replay lag for database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 279: Enable replay lag requested for database guid=DatabaseGuid.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Enable replay lag requested for database guid=DatabaseGuid.

Fields #

Name	Description
`DatabaseGuid`

Event ID 280: Enable replay lag for database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Enable replay lag for database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 281: Enable replay lag for database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Enable replay lag for database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 282: Cluster API 'ApiName' appears to be hung for 'Elapsed'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster API 'ApiName' appears to be hung for 'Elapsed'. Cluster service will be restarted to recover from this condition.

Fields #

Name	Description
`ApiName`
`StartTime`
`Elapsed`
`HintStr`
`MaxAllowedLatency`

Event ID 283: Operation 'ApiName' took an unusually long time of 'Elapsed' to complete.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Operation 'ApiName' took an unusually long time of 'Elapsed' to complete.

Fields #

Name	Description
`ApiName`
`StartTime`
`Elapsed`
`HintStr`
`IsUnhandledException`
`ReturnCode`
`MaxAllowedLatency`

Event ID 284: Service 'ServiceName' was forcefully terminated.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Service 'ServiceName' was forcefully terminated. (Reason: Reason).

Fields #

Name	Description
`ServiceName`
`Reason`
`ErrorMessage`

Event ID 285: Local dismount of all databases has been delayed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Local dismount of all databases has been delayed. A request is queued to dismount the databases in Delay seconds.

Fields #

Name	Description
`Delay`

Event ID 286: Delayed local dismount is avoided because the Active Manager role is now Role and not Unknown.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Delayed local dismount is avoided because the Active Manager role is now Role and not Unknown.

Fields #

Name	Description
`Role`

Event ID 287: Delayed local dismount request of all databases has been cancelled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Delayed local dismount request of all databases has been cancelled.

Event ID 288: Added delayed failover entry for ServerName with Delay delay.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Added delayed failover entry for ServerName with Delay delay. Databases will remain mounted during the delay unless there are further errors.

Fields #

Name	Description
`ServerName`
`ReasonCode`
`ReportedTime`
`Delay`

Event ID 289: Delayed failover entry already exists for ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Delayed failover entry already exists for ServerName. Delayed failover will be performed at DueTime.

Fields #

Name	Description
`ServerName`
`DueTime`

Event ID 290: Removed delayed failover entry for 'ServerName' (Reason: Reason).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Removed delayed failover entry for 'ServerName' (Reason: Reason).

Fields #

Name	Description
`ServerName`
`Reason`

Event ID 291: Delayed failover cancelled since ServerName now is in state 'Up'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Delayed failover cancelled since ServerName now is in state 'Up'.

Fields #

Name	Description
`ServerName`

Event ID 292: Transient failover suppression persistent state operation failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Transient failover suppression persistent state operation failed. (Operation: Operation, ServerName:ServerName, Error:ErrorMessage)

Fields #

Name	Description
`Operation`
`ServerName`
`ErrorMessage`

Event ID 293: Critical Cluster API 'ApiName' failed with error ErrorCode.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Critical Cluster API 'ApiName' failed with error ErrorCode. (Hint: Hint)

Fields #

Name	Description
`ApiName`
`ErrorCode`
`Hint`

Event ID 294: Active Directory configuration lookup failed with error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Active Directory configuration lookup failed with error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 295: Copy Status Poller component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Copy Status Poller component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 296: Replay Lag Manager component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 297: Replay Lag Manager component encountered an error when processing database 'DatabaseName': ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager component encountered an error when processing database 'DatabaseName': ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`
`ExceptionFullString`

Event ID 298: Replay Lag Manager requested enabling replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of EnableSuppression.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager requested enabling replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of EnableSuppression.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`EnableSuppression`

Event ID 299: Database 'DatabaseGuid' returns global min required 'GenToPreserve' ('GenToPreserveWithoutCheckpoint' not including the checkpoint at logfile creation) to server 'PassiveServerName' after passing s...

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Database 'DatabaseGuid' returns global min required 'GenToPreserve' ('GenToPreserveWithoutCheckpoint' not including the checkpoint at logfile creation) to server 'PassiveServerName' after passing startGen 'StartGenTruncated' to ESE for truncation on the active copy.

Fields #

Name	Description
`DatabaseGuid`
`PassiveServerName`
`StartGenTruncated`
`GenToPreserve`
`GenToPreserveWithoutCheckpoint`

Event ID 300: Initiating mount for database 'DatabaseName' (Flags=Flags, MountDialoverride=MountdialOverride).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating mount for database 'DatabaseName' (Flags=Flags, MountDialoverride=MountdialOverride)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActionCategory`
`ActionInitiator`
`ActionReason`
`AmRole`
`PAMServer`
`Flags`
`MountdialOverride`

Event ID 301: Failed to mount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed to mount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`ErrorMessage`
`FailoverSequenceNumber`

Event ID 302: Successfully mounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully mounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`FailoverSequenceNumber`

Event ID 303: Initiating dismount for database 'DatabaseName' on ActiveServer (Flags=Flags).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating dismount for database 'DatabaseName' on ActiveServer (Flags=Flags)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActionCategory`
`ActionInitiator`
`ActionReason`
`AmRole`
`PAMServer`
`Flags`

Event ID 304: Failed to dismount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed to dismount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`ErrorMessage`
`FailoverSequenceNumber`

Event ID 305: Successfully dismounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber, DurableDismount=DurableDismount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully dismounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber, DurableDismount=DurableDismount)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`FailoverSequenceNumber`
`DurableDismount`

Event ID 306: Initiating move for database 'DatabaseName' (FromServer=FromServer, ToServer=TargetServer, MoveComment=MoveComment).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating move for database 'DatabaseName' (FromServer=FromServer, ToServer=TargetServer, MoveComment=MoveComment)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActionCategory`
`ActionInitiator`
`ActionReason`
`AmRole`
`PAMServer`
`MountFlags`
`DismountFlags`
`MountdialOverride`
`FromServer`
`TargetServer`
`TryOtherHealthyServers`
`SkipValidationChecks`
`MoveComment`
`ComponentName`
`SubReason`

Event ID 307: Failed to move database 'DatabaseName' (InitialActive=InitialActiveServer, CurrentActive=ActiveServer, Duration=ElapsedTime, MoveComment=MoveComment, ErrorMessage=ErrorMessage, FailoverSequenceNumb...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed to move database 'DatabaseName' (InitialActive=InitialActiveServer, CurrentActive=ActiveServer, Duration=ElapsedTime, MoveComment=MoveComment, ErrorMessage=ErrorMessage, FailoverSequenceNumber=SubReason)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`InitialActiveServer`
`ElapsedTime`
`ErrorMessage`
`MoveComment`
`FailureCateogry`
`SubReason`
`FailoverSequenceNumber`

Event ID 308: Successfully moved database 'DatabaseName' from InitialActiveServer to ActiveServer (Duration=ElapsedTime, MoveComment=MoveComment, FailoverSequenceNumber=SubReason).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully moved database 'DatabaseName' from InitialActiveServer to ActiveServer (Duration=ElapsedTime, MoveComment=MoveComment, FailoverSequenceNumber=SubReason)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`InitialActiveServer`
`ElapsedTime`
`MoveComment`
`SubReason`
`FailoverSequenceNumber`

Event ID 309: Initiating remount for database 'DatabaseName' on ActiveServer(Flags=MountFlags, MountDialoverRide=MountdialOverride, FromServer=FromServer).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating remount for database 'DatabaseName' on ActiveServer(Flags=MountFlags, MountDialoverRide=MountdialOverride, FromServer=FromServer)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActionCategory`
`ActionInitiator`
`ActionReason`
`AmRole`
`PAMServer`
`MountFlags`
`MountdialOverride`
`FromServer`

Event ID 310: Failed to remount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed to remount database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage, FailoverSequenceNumber=FailoverSequenceNumber)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`ErrorMessage`
`FailoverSequenceNumber`

Event ID 311: Successfully remounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully remounted database 'DatabaseName' on ActiveServer (Duration=ElapsedTime, FailoverSequenceNumber=FailoverSequenceNumber)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ElapsedTime`
`FailoverSequenceNumber`

Event ID 312: Initiating Acll for database 'DatabaseName' on RunningOnServer (SourceServer=SourceServer).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating Acll for database 'DatabaseName' on RunningOnServer (SourceServer=SourceServer)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`SourceServer`

Event ID 313: Failed Acll for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed Acll for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`ElapsedTime`
`ErrorMessage`
`DismountRequested`
`DismountDuration`
`DismountResultFlags`

Event ID 314: Successfully finished Acll for database 'DatabaseName' on RunningOnServer (IsLossyMount=IsLossyMount, Duration=ElapsedTime).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully finished Acll for database 'DatabaseName' on RunningOnServer (IsLossyMount=IsLossyMount, Duration=ElapsedTime)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`IsLossyMount`
`ElapsedTime`
`DismountRequested`
`DismountDuration`
`DismountResultFlags`

Event ID 315: Initiating store mount for database 'DatabaseName' on RunningOnServer (MountFlags=MountFlags, IsLossyMountEnabled=IsLossyMountEnabled, AMMountFlags=AMMountFlags).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating store mount for database 'DatabaseName' on RunningOnServer (MountFlags=MountFlags, IsLossyMountEnabled=IsLossyMountEnabled, AMMountFlags=AMMountFlags)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`MountFlags`
`IsLossyMountEnabled`
`AMMountFlags`

Event ID 316: Failed store mount for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed store mount for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime, ErrorMessage=ErrorMessage)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`ElapsedTime`
`ErrorMessage`

Event ID 318: Successfully finished store mount for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully finished store mount for database 'DatabaseName' on RunningOnServer (Duration=ElapsedTime)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`ElapsedTime`

Event ID 319: Initiating store dismount for database 'DatabaseName' on RunningOnServer (DismountFlags=DismountFlags, BestEffortTimeout=BestEffortTimeout).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating store dismount for database 'DatabaseName' on RunningOnServer (DismountFlags=DismountFlags, BestEffortTimeout=BestEffortTimeout)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`DismountFlags`
`BestEffortTimeout`

Event ID 320: Failed store dismount for database 'DatabaseName' on RunningOnServer (DismountMode=DismountMode, Duration=ElapsedTime, ErrorMessage=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed store dismount for database 'DatabaseName' on RunningOnServer (DismountMode=DismountMode, Duration=ElapsedTime, ErrorMessage=ErrorMessage)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`DismountMode`
`ElapsedTime`
`ErrorMessage`

Event ID 321: Successfully finished store dismount for database 'DatabaseName' on RunningOnServer (DismountMode=DismountMode, Duration=ElapsedTime, DurableDismount=DurableDismount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully finished store dismount for database 'DatabaseName' on RunningOnServer (DismountMode=DismountMode, Duration=ElapsedTime, DurableDismount=DurableDismount)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`RunningOnServer`
`DismountMode`
`ElapsedTime`
`DurableDismount`

Event ID 322: Active server for database 'DatabaseName' changed from PreviousActiveServer to CurrentActiveServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active server for database 'DatabaseName' changed from PreviousActiveServer to CurrentActiveServer

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`PreviousActiveServer`
`CurrentActiveServer`

Event ID 323: Attempt for mount skipped for database 'DatabaseName' on SkippedOnServer (ErrorMessage=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt for mount skipped for database 'DatabaseName' on SkippedOnServer (ErrorMessage=ErrorMessage)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`SkippedOnServer`
`ErrorMessage`

Event ID 324: Acll determined that database 'UniqueId' lost DatabaseGuid log(s).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Acll determined that database 'UniqueId' lost DatabaseGuid log(s). Lossy dismount was possible: LossyDismountWasPossible

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`NumberOfLostLogs`
`LastLogNotified`
`LastLogShipped`
`MountDial`
`IsMountDialUsed`
`LastLogInspectedTime`
`LatestInspectorTimeFromState`
`LossyDismountWasPossible`
`LastLogGenIsStale`

Event ID 325: Active manager on this server is running as Role for duration ElapsedTimeInCurrentRole (AuthoritativeServer=AuthoritativeServer, ChangeFlags='ChangeFlags', LastError='LastError', ServersInMaintenan...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager on this server is running as Role for duration ElapsedTimeInCurrentRole (AuthoritativeServer=AuthoritativeServer, ChangeFlags='ChangeFlags', LastError='LastError', ServersInMaintenance='ServersInMaintenance')

Fields #

Name	Description
`Role`
`AuthoritativeServer`
`ElapsedTimeInCurrentRole`
`ChangeFlags`
`LastError`
`ServersInMaintenance`

Event ID 326: System event 'SystemEvent' is enqueued to system event queue.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

System event 'SystemEvent' is enqueued to system event queue.

Fields #

Name	Description
`SystemEvent`

Event ID 327: System event processing started for event 'SystemEvent'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

System event processing started for event 'SystemEvent'.

Fields #

Name	Description
`SystemEvent`

Event ID 328: System event processing finished for event 'SystemEvent' (Duration=Duration).

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

System event processing finished for event 'SystemEvent' (Duration=Duration).

Fields #

Name	Description
`SystemEvent`
`Duration`

Event ID 329: System event processing finished for event 'SystemEvent' with exception 'Exception' (Duration=Duration).

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

System event processing finished for event 'SystemEvent' with exception 'Exception' (Duration=Duration).

Fields #

Name	Description
`SystemEvent`
`Duration`
`Exception`

Event ID 330: System event processing for event 'SystemEvent' exceeded 'Duration'ms.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

System event processing for event 'SystemEvent' exceeded 'Duration'ms.

Fields #

Name	Description
`SystemEvent`
`Duration`

Event ID 331: Acll determined that database 'DatabaseName' lost NumberOfLostLogs log(s).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Acll determined that database 'DatabaseName' lost NumberOfLostLogs log(s)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`NumberOfLostLogs`
`LastLogNotified`
`EndOfLogGeneration`
`EndOfLogByteOffset`
`EndOfLogUtc`
`EndOfLogWasGranular`
`OriginalActive`
`OtherPassives`
`UniqueId`
`LastLogGenIsStale`

Event ID 332: The copy of database 'DatabaseName' is starting as a passive.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of database 'DatabaseName' is starting as a passive. Its end of log is 'EndOfLogFilename' of generation EndOfLogGeneration.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`EndOfLogFilename`
`EndOfLogGeneration`
`EndOfLogByteOffset`
`EndOfLogUtc`
`EndOfLogWasE00`
`ISeedRequired`
`ActiveServer`
`LastWriteTimeIsFromE00Predecessor`

Event ID 333: The copy of database 'DatabaseName' is losing LossInBytes bytes during incremental reseed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of database 'DatabaseName' is losing LossInBytes bytes during incremental reseed.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LossInBytes`
`EndOfLogGeneration`
`EndOfLogByteOffset`
`DivergenceGeneration`
`DivergenceByteOffset`
`EndOfLogUtc`
`EndOfLogWasE00`
`ActiveServer`
`ConvergenceUtc`

Event ID 334: Initiating data gathering for best copy selection for database 'DatabaseName' (BcsType=BcsType, IsStatusFetcherConstructed=IsStatusFetcherConstructed).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating data gathering for best copy selection for database 'DatabaseName' (BcsType=BcsType, IsStatusFetcherConstructed=IsStatusFetcherConstructed)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`BcsType`
`IsStatusFetcherConstructed`

Event ID 335: Completed data gathering for best copy selection for database 'DatabaseName' (Duration=ElapsedTime).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Completed data gathering for best copy selection for database 'DatabaseName' (Duration=ElapsedTime)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`ElapsedTime`
`HasDatabaseBeenMountedElapsedTime`
`GetDatabaseCopiesElapsedTime`
`DetermineServersToContactElapsedTime`
`GetCopyStatusRpcElapsedTime`

Event ID 336: Acll for database 'DatabaseName' finished.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Acll for database 'DatabaseName' finished. (Duration=AcllQueuedOpStartElapsedTime)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`
`IsSkipHealthChecks`
`IsPrepareToStopCalled`
`IsNewCopierInspectorCreated`
`IsGranuleUsedAsE00`
`IsAcllFoundDeadConnection`
`IsAcllCouldNotControlLogCopier`
`IsLogCopierInitializedForAcll`
`ReplicaInstanceStage`
`CopyStatus`
`CopyQueueLengthAcllStart`
`ReplayQueueLengthAcllStart`
`ReplayQueueLengthAcllEnd`
`NumberOfLogsLost`
`NumberOfLogsCopied`
`AcllQueuedOpStartElapsedTime`
`AcllQueuedOpExecutionElapsedTime`
`AcquireSuspendLockElapsedTime`
`EnsureTargetDismountedElapsedTime`
`FileCheckerAtStartElapsedTime`
`CleanUpTempIncReseedFilesElapsedTime`
`IsIncrementalReseedNecessaryElapsedTime`
`AttemptFinalCopyElapsedTime`
`InspectFinalLogsElapsedTime`
`InspectE00LogElapsedTime`
`CheckRequiredLogFilesAtEndElapsedTime`
`CopyLogsOverallElapsedTime`
`AcllEnterLogCopierWorkerLockElapsedTime`
`RunAcllInitElapsedTime`
`AcllLogCopierFirstInitElapsedTime`
`AcllInitWaitForReadCallbackElapsedTime`
`ComputeLossAndMountAllowedOverallElapsedTime`
`SetLossVariablesElapsedTime`
`ProtectUnboundedDatalossElapsedTime`
`MarkRedeliveryRequiredElapsedTime`
`RollbackLastLogIfNecessaryElapsedTime`
`IsE00EndOfLogStreamAfterIncReseed`
`SetE00LogGenerationElapsedTime`
`LossDueToLazyCommit`
`LastLogGenIsStale`
`SecondaryLogCopyAttempted`
`NumberOfSecondaryLogsObtained`
`SecondaryLogCopyElapsedTime`
`SecondaryLogCopyQueryElapsed`
`MountAllowed`
`LosslessMoveRequested`
`DismountRequested`
`DismountSucceeded`
`DismountResultFlags`
`DismountDuration`
`DismountErrMsg`

Event ID 337: Mount for database 'DatabaseName' finished.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mount for database 'DatabaseName' finished. (Duration StoreMount=StoreMountElapsedTime, Duration PreMount=AmPreMountCallbackElapsedTime)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LastAcllLossAmount`
`AmPreMountCallbackElapsedTime`
`RegistryReplicatorCopyElapsedTime`
`StoreMountElapsedTime`
`PreMountQueuedOpStartElapsedTime`
`PreMountQueuedOpExecutionElapsedTime`
`PreventMountIfNecessaryElapsedTime`
`ResumeActiveCopyElapsedTime`
`UpdateLastLogGenOnMountElapsedTime`
`GetRunningReplicaInstanceElapsedTime`
`ConfirmLogResetElapsedTime`
`LowestGenerationInDirectory`
`HighestGenerationInDirectory`
`GenerationAvailableInDirectory`
`UpdateLastLogGeneratedInClusDB`
`IsLossyMountEnabled`
`HighestLogGenBefore`
`HighestLogGenAfter`
`LastAcllRunWithSkipHealthChecks`
`IsDismountInProgress`
`TotalElapsedTime`

Event ID 338: Incremental Reseed for database 'DatabaseName' finished divergence checking and/or resynchronizing the log stream.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed for database 'DatabaseName' finished divergence checking and/or resynchronizing the log stream. (IncReseed Needed = IsIncReseedNeeded. Check Duration=IsIncrementalReseedRequiredOverallElapsedTime, IncReseed Duration=PerformIncrementalReseedOverallElapsedTime)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRunningACLL`
`IsRestartedIncReseed`
`IsFailedPassivePagePatch`
`IsE00LogExists`
`IsDivergentAfterSeed`
`IsIncReseedNeeded`
`IsIncReseedV1Performed`
`IsDatabaseConsistent`
`IsPagesReferencedInDivergentLogs`
`PassiveEOLGen`
`NumPagesToBePatched`
`ActiveHighestLogGen`
`HighestLogGenRequired`
`LowestLogGenRequired`
`IsIncrementalReseedRequiredOverallElapsedTime`
`CheckForDivergenceAfterSeedingElapsedTime`
`CheckSourceDatabaseMountedFirstElapsedTime`
`QueryLogRangeFirstElapsedTime`
`PerformIncrementalReseedOverallElapsedTime`
`FindDivergencePointElapsedTime`
`PrepareIncReseedV2OverallElapsedTime`
`RedirtyDatabaseElapsedTime`
`PauseTruncationElapsedTime`
`GeneratePageListSinceDivergenceElapsedTime`
`ReadDatabasePagesFromActiveElapsedTime`
`CopyAndInspectRequiredLogFilesElapsedTime`
`PatchDatabaseOverallElapsedTime`
`ReplaceLogFilesElapsedTime`
`SourceServer`
`FirstDivergedLogGen`
`ReplaceE00LogTransactedElapsedTime`
`EnsureTargetDismountedElapsedTime`
`IsLogfileEqualElapsedTime`
`IsLogfileSubsetElapsedTime`
`IsPreviousLogNotBinaryEqual`
`ReseedSecondaryPartitionElapsedTime`

Event ID 339: The copy of database 'DatabaseName' lost LossInBytes bytes after a successful incremental reseed from active on ActiveServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of database 'DatabaseName' lost LossInBytes bytes after a successful incremental reseed from active on ActiveServer. Divergence was at generation DivergenceGeneration. Common time was CommonLogUtc.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LossInBytes`
`EndOfLogGeneration`
`EndOfLogByteOffset`
`EndOfLogUtc`
`EndOfLogWasE00`
`DivergenceGeneration`
`DivergenceByteOffset`
`CommonLogUtc`
`ActiveServer`
`NumPagesPatched`
`TotalPageReferences`
`ServerVersion`
`StartTime`
`Duration`
`CurrentPAM`

Event ID 340: Incremental reseed failed to preserve the old logs: Exception.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental reseed failed to preserve the old logs: Exception

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`SourceDir`
`TargetDir`
`Exception`

Event ID 341: Best copy selection information chose server NewServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Best copy selection information chose server NewServerName

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`OldServerName`
`NewServerName`
`ActionInitiator`
`ActionCategory`
`ActionReason`
`AcllNoLoss`
`AcllLogsLost`
`AcllLogGenShipped`
`AcllLogGenNotified`
`AcllMountDialOverrideUsed`
`AcllLastInspectedLogTime`
`LastSeenGlobalLogGeneration`
`SortBy`
`CopyStatus`
`AttemptedServers`
`Errors`
`Success`
`AcllWasAttempted`
`LossDueToLazyCommit`
`AcllReportedLastLogGenIsStale`

Event ID 342: Proceeding with move for database 'DatabaseName' (FromServer=FromServer, ToServer=TargetServer, MoveComment=MoveComment).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Proceeding with move for database 'DatabaseName' (FromServer=FromServer, ToServer=TargetServer, MoveComment=MoveComment)

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActionCategory`
`ActionInitiator`
`ActionReason`
`AmRole`
`PAMServer`
`MountFlags`
`DismountFlags`
`MountdialOverride`
`FromServer`
`TargetServer`
`TryOtherHealthyServers`
`SkipValidationChecks`
`MoveComment`
`ComponentName`
`SubReason`

Event ID 343: The callback to perform Preferred Moves failed with: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The callback to perform Preferred Moves failed with: Message

Fields #

Name	Description
`Message`

Event ID 382: Cluster API 'ApiName' appears to be hung for 'Elapsed'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster API 'ApiName' appears to be hung for 'Elapsed'. An alert will be raised for this condition.

Fields #

Name	Description
`ApiName`
`StartTime`
`Elapsed`
`HintStr`
`MaxAllowedLatency`

Event ID 383: SpaceMonitor component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

SpaceMonitor component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 384: SpaceMonitor component encountered an error when processing database 'DatabaseName': ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

SpaceMonitor component encountered an error when processing database 'DatabaseName': ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`
`ExceptionFullString`

Event ID 385: Low space was detected for the local copy of database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Low space was detected for the local copy of database 'DatabaseName'.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`TotalSpaceInMB`
`RemainingSpaceInMB`
`RemainingSpacePercent`
`CopyQueueLen`
`ReplayQueueLen`
`MinLogGen`
`MaxLogGen`
`HealthyCopyCount`
`MinRequiredHealthy`

Event ID 386: SetBroken called for the local copy of database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SetBroken called for the local copy of database 'DatabaseName'.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`
`StackTrace`
`Exception`
`HResult`

Event ID 387: Average disk write rate has been above the threshold of Thresholdms for FailureSuppressionDurationMinuteminutes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Average disk write rate has been above the threshold of Thresholdms for FailureSuppressionDurationMinuteminutes.

Fields #

Name	Description
`MachineName`
`FailureCategory`
`Threshold`
`FailureSuppressionDurationMinute`

Event ID 388: A Controller cache reset was done successfully on MachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A Controller cache reset was done successfully on MachineName.

Fields #

Name	Description
`MachineName`

Event ID 389: Average disk read latency has been above the threshold for database MachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Average disk read latency has been above the threshold for database MachineName.

Fields #

Name	Description
`MachineName`

Event ID 390: An NTFS corruption issue has been detected on system drive of this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An NTFS corruption issue has been detected on system drive of this server.

Event ID 391: An NTFS corruption issue has been detected on drive D: of this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An NTFS corruption issue has been detected on drive D: of this server.

Event ID 392: NTFS corruption issues have been detected on multiple drives of this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

NTFS corruption issues have been detected on multiple drives of this server.

Event ID 393: SetDisconnected called for the local copy of database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SetDisconnected called for the local copy of database 'DatabaseName'. LastCopied: LastCopiedGen LastNotified: LastNotifiedGen

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`
`StackTrace`
`LastCopiedGen`
`LastNotifiedGen`

Event ID 394: Segments Retransmitted counter has been above the threshold of Threshold retransmits per sec for FailureSuppressionDurationMinuteminutes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Segments Retransmitted counter has been above the threshold of Threshold retransmits per sec for FailureSuppressionDurationMinuteminutes.

Fields #

Name	Description
`MachineName`
`FailureCategory`
`Threshold`
`FailureSuppressionDurationMinute`

Event ID 395: A network adapter reset was failed on MachineName Error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A network adapter reset was failed on MachineName Error: ErrorMessage.

Fields #

Name	Description
`MachineName`
`ErrorMessage`

Event ID 396: A network adapter reset was done successfully on MachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A network adapter reset was done successfully on MachineName.

Fields #

Name	Description
`MachineName`

Event ID 397: Fail to send RescueBox recovery request on MachineName Error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Fail to send RescueBox recovery request on MachineName Error: ErrorMessage.

Fields #

Name	Description
`MachineName`
`ErrorMessage`

Event ID 398: A RescueBox recovery request has been sent successfully on MachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A RescueBox recovery request has been sent successfully on MachineName.

Fields #

Name	Description
`MachineName`

Event ID 399: Fpga presence check has been failing with error ErrorCode for FailureSuppressionDurationMinutes minutes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Fpga presence check has been failing with error ErrorCode for FailureSuppressionDurationMinutes minutes. ErrorMessage.

Fields #

Name	Description
`MachineName`
`ErrorCode`
`ErrorMessage`
`FailureSuppressionDurationMinutes`

Event ID 500: The ThirdPartyReplication provider successfully started the NotificationListener and is listening for AME events.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider successfully started the NotificationListener and is listening for AME events.

Event ID 501: The ThirdPartyReplication provider attempted to start the NotificationListener but failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider attempted to start the NotificationListener but failed: Message

Fields #

Name	Description
`Message`

Event ID 502: The ThirdPartyReplication provider is stopping the NotificationListener.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider is stopping the NotificationListener.

Event ID 503: An unexpected exception was caught by HAThirdPartyReplication.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An unexpected exception was caught by HAThirdPartyReplication.dll: Message The following stacktrace may help diagnose the problem: StackTrace

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 504: The ThirdPartyReplication provider was notified that it is entering the PAME role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider was notified that it is entering the PAME role.

Event ID 505: The ThirdPartyReplication provider was notified that it is entering the SAME role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider was notified that it is entering the SAME role.

Event ID 506: The ThirdPartyReplication provider was notified that database 'DatabaseGuid' should be moved off 'CurrentActiveFQDN' and left mounted=MountDesired.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ThirdPartyReplication provider was notified that database 'DatabaseGuid' should be moved off 'CurrentActiveFQDN' and left mounted=MountDesired.

Fields #

Name	Description
`DatabaseGuid`
`CurrentActiveFQDN`
`MountDesired`

Event ID 600: The Exchange Third Party Replication Listener was successfully started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Exchange Third Party Replication Listener was successfully started.

Event ID 601: The Exchange Third Party Replication Listener failed to start due to an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Exchange Third Party Replication Listener failed to start due to an error: Message

Fields #

Name	Description
`Message`

Event ID 602: The Exchange Third Party Replication Listener is stopping.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Exchange Third Party Replication Listener is stopping.

Event ID 603: ThirdPartyReplication is enabled but an invalid operation was attempted: Message The following stacktrace may help diagnose the problem: StackTrace.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ThirdPartyReplication is enabled but an invalid operation was attempted: Message The following stacktrace may help diagnose the problem: StackTrace

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 604: ThirdPartyReplication service was denied to user 'Message' because it is not part of the LocalAdministrators group.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ThirdPartyReplication service was denied to user 'Message' because it is not part of the LocalAdministrators group.

Fields #

Name	Description
`Message`

Event ID 605: ImmediateDismountMailboxDatabase for database 'DatabaseGuid' failed: Message The following stacktrace may help diagnose the problem: StackTrace.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ImmediateDismountMailboxDatabase for database 'DatabaseGuid' failed: Message The following stacktrace may help diagnose the problem: StackTrace

Fields #

Name	Description
`DatabaseGuid`
`Message`
`StackTrace`

Event ID 606: ChangeActiveServer for database 'DatabaseGuid' to server 'NewActiveServerName' failed: Message The following stacktrace may help diagnose the problem: StackTrace.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ChangeActiveServer for database 'DatabaseGuid' to server 'NewActiveServerName' failed: Message The following stacktrace may help diagnose the problem: StackTrace

Fields #

Name	Description
`DatabaseGuid`
`NewActiveServerName`
`Message`
`StackTrace`

Event ID 607: ChangeActiveServer for database 'DatabaseName' 'DatabaseGuid' from server 'OldActiveServerName' to server 'NewActiveServerName' succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ChangeActiveServer for database 'DatabaseName' 'DatabaseGuid' from server 'OldActiveServerName' to server 'NewActiveServerName' succeeded.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`OldActiveServerName`
`NewActiveServerName`

Event ID 608: The Third Party Replication vendor responded with 'Response' to a DatabaseMoveNeeded for database 'DatabaseGuid' on server 'CurrentActiveFQDN' with mount desired = 'MountDesired'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Third Party Replication vendor responded with 'Response' to a DatabaseMoveNeeded for database 'DatabaseGuid' on server 'CurrentActiveFQDN' with mount desired = 'MountDesired'.

Fields #

Name	Description
`DatabaseGuid`
`CurrentActiveFQDN`
`MountDesired`
`Response`

Event ID 609: The Third Party Replication vendor did not respond to a DatabaseMoveNeeded for database 'DatabaseGuid' on server 'CurrentActiveFQDN' with mount desired = 'MountDesired'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Third Party Replication vendor did not respond to a DatabaseMoveNeeded for database 'DatabaseGuid' on server 'CurrentActiveFQDN' with mount desired = 'MountDesired'. The communication error was: Error

Fields #

Name	Description
`DatabaseGuid`
`CurrentActiveFQDN`
`MountDesired`
`Error`

Event ID 700: Disk heartbeat started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk heartbeat started.

Event ID 701: Disk heartbeat stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk heartbeat stopped.

Event ID 702: Replay Lag Manager successfully enabled replay lag for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager successfully enabled replay lag for database copy 'DatabaseName\ServerName'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`

Event ID 703: Replay Lag Manager failed to enable replay lag for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager failed to enable replay lag for database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`
`Message2`

Event ID 704: Replay Lag Manager requested disabling replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of DisableSuppression.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager requested disabling replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of DisableSuppression. Disable Reason: DisableReason

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`DisableReason`
`DisableSuppression`

Event ID 705: Replay Lag Manager successfully disabled replay lag for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager successfully disabled replay lag for database copy 'DatabaseName\ServerName'. Disable Reason: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 706: Replay Lag Manager failed to disable replay lag for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager failed to disable replay lag for database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`
`Message2`

Event ID 707: Log Replay for database 'DatabaseName' is replaying logs from generation LogGeneration because it is in the required range of the database.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log Replay for database 'DatabaseName' is replaying logs from generation LogGeneration because it is in the required range of the database. (LogFileAge=LogFileAge, ReqRange=LowestGenerationRequired-HighestGenerationRequired)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LogGeneration`
`LogFileAge`
`LowestGenerationRequired`
`HighestGenerationRequired`

Event ID 708: Log Replay for database 'DatabaseName' is replaying logs in the replay lag range.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log Replay for database 'DatabaseName' is replaying logs in the replay lag range. Reason: Reason (LogFileAge=LogFileAge, ReasonCode=ReasonCode)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LogGeneration`
`LogFileAge`
`Reason`
`ReasonCode`

Event ID 709: Log Replay for database 'DatabaseName' is reinstating replay lag.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log Replay for database 'DatabaseName' is reinstating replay lag. (PrevHighestGenToReplay=PrevHighestGenToReplay, HighestGenerationToReplay=HighestGenerationToReplay)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LogGeneration`
`LogFileAge`
`PrevHighestGenToReplay`
`HighestGenerationToReplay`

Event ID 710: Dumpster Redelivery component encountered an error when determining server version numbers for compatability: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster Redelivery component encountered an error when determining server version numbers for compatability: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 711: Re-delivery of messages from the transport dumpster will be attempted for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Re-delivery of messages from the transport dumpster will be attempted for database 'DatabaseName'. Messages originally delivered between StartTimeUtc (UTC) and EndTimeUtc (UTC) will be re-delivered. (IsRequestInOldDumpsterSchema=IsRequestInOldDumpsterSchema, IsRequestFromSafetyNet=IsRequestFromSafetyNet, RequestOrigination=RequestOrigin, RequestGuid=RequestGuid)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PreviousActiveServer`
`LastLogGenBeforeActivation`
`NumberOfLogsLost`
`FailoverTimeUtc`
`StartTimeUtc`
`EndTimeUtc`
`IsRequestInOldDumpsterSchema`
`IsRequestFromSafetyNet`
`RequestOrigin`
`RequestGuid`

Event ID 712: Dumpster redelivery for database 'DatabaseName' failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery for database 'DatabaseName' failed. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`ErrorMessage`
`ExceptionFullString`

Event ID 713: Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' failed [ RequestGuid=RequestGuid ].

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' failed [ RequestGuid=RequestGuid ]. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`RequestCreationTimeUtc`
`RequestKey`
`RequestValue`
`ErrorMessage`
`RequestGuid`

Event ID 714: Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) faile...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) failed (IsRequestFromSafetyNet=IsRequestFromSafetyNet, InPrimaryPhase=InPrimaryPhase, UnresponsivePrimaryServers=UnresponsivePrimaryServers, RequestGuid=RequestGuid). Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`RequestCreationTimeUtc`
`StartTimeUtc`
`EndTimeUtc`
`HubServer`
`RequestKey`
`RequestValue`
`ErrorMessage`
`IsRequestFromSafetyNet`
`InPrimaryPhase`
`UnresponsivePrimaryServers`
`RequestGuid`

Event ID 715: Successfully requested dumpster redelivery to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully requested dumpster redelivery to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC). (ResubmitElapsedTime=ResubmitElapsedTime, IsRequestFromSafetyNet=IsRequestFromSafetyNet, InPrimaryPhase=InPrimaryPhase, UnresponsivePrimaryServers=UnresponsivePrimaryServers, RequestGuid=RequestGuid)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`RequestCreationTimeUtc`
`StartTimeUtc`
`EndTimeUtc`
`HubServer`
`RequestKey`
`RequestValue`
`ResubmitElapsedTime`
`IsRequestFromSafetyNet`
`InPrimaryPhase`
`UnresponsivePrimaryServers`
`RequestGuid`

Event ID 716: Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' is being expired.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' is being expired. [ WasRedeliveryRequired=WasRedeliveryRequired, WasEXORedeliveryRequired=WasEXORedeliveryRequired, MaxDumpsterTime=MaxDumpsterTime, RequestGuid=RequestGuid ]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`RequestCreationTimeUtc`
`RequestKey`
`RequestValue`
`MaxDumpsterTime`
`WasRedeliveryRequired`
`RequestGuid`
`WasEXORedeliveryRequired`

Event ID 717: Active Manager detected remote site connectivity issues but the majority of nodes are still reachable (total server count: TotalServersCount successful count: SuccessfulReplyCount).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager detected remote site connectivity issues but the majority of nodes are still reachable (total server count: TotalServersCount successful count: SuccessfulReplyCount).

Fields #

Name	Description
`TotalServersCount`
`SuccessfulReplyCount`

Event ID 718: Active Manager is postponing the immediate dismount of locally mounted databases since majority of the nodes are reachable.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager is postponing the immediate dismount of locally mounted databases since majority of the nodes are reachable (total server count: TotalServersCount successful count: SuccessfulReplyCount)

Fields #

Name	Description
`TotalServersCount`
`SuccessfulReplyCount`

Event ID 719: Majority node check completed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Majority node check completed. (Elapsed: Elapsed, IsMajority: IsMajority, TotalServersContacted: TotalServersContacted, SuccessfulRepliesReceived: SuccessfulRepliesReceived)

Fields #

Name	Description
`Elapsed`
`IsMajority`
`TotalServersContacted`
`SuccessfulRepliesReceived`

Event ID 720: Majority node check was not attemped since there are no cluster members available to contact.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Majority node check was not attemped since there are no cluster members available to contact.

Event ID 721: LastKnownGoodConfig serialization failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

LastKnownGoodConfig serialization failed. (Mode:Mode, Error:Error)

Fields #

Name	Description
`Mode`
`Error`

Event ID 722: LastKnownGoodConfig initialized from registry.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

LastKnownGoodConfig initialized from registry. (Role: Role, AuthoritativeServer: AuthoritativeServer, Members: Members)

Fields #

Name	Description
`Role`
`AuthoritativeServer`
`Members`

Event ID 723: Periodic database status analyzer skipped mounting database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Periodic database status analyzer skipped mounting database 'DatabaseName'. (ActiveServer: ActiveServer, IsMountAtStartup: IsMountAtStartup, IsAdminDismounted:IsAdminDismounted, IsMountAttemptedAtleastOnce:IsMountAttemptedAtleastOnce, IsStoreGracefullyStoppedOnActive:IsStoreGracefullyStoppedOnActive)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`IsMountAtStartup`
`IsAdminDismounted`
`IsMountAttemptedAtleastOnce`
`IsStoreGracefullyStoppedOnActive`

Event ID 724: Database dismount failed on timeout (databaseGuid='DatabaseGuid', timeout='Timeout').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database dismount failed on timeout (databaseGuid='DatabaseGuid', timeout='Timeout')

Fields #

Name	Description
`DatabaseGuid`
`Timeout`

Event ID 725: FileChecker got 'file in use' error, when trying to access database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FileChecker got 'file in use' error, when trying to access database 'DatabaseName' (DatabaseGuid). Filechecker will try to dismount the database and retry the operation. Error: ExceptionMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ExceptionMessage`

Event ID 726: Acll for database 'DatabaseName' observed highest log generation as HighestGen and copy queue length as CopyQLen.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Acll for database 'DatabaseName' observed highest log generation as HighestGen and copy queue length as CopyQLen.

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`HighestGen`
`CopyQLen`
`ClusterLastLogGen`
`ClusterLastLogTime`
`ClusterLastLogTimeMissing`
`ClusterLastLogException`
`ReplLastLogGen`
`ReplLastLogTime`
`IsStale`
`CollectionTime`

Event ID 727: Active Manager detected remote site connectivity issues and the majority of nodes are not reachable.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager detected remote site connectivity issues and the majority of nodes are not reachable. This could indicate a complete DAG meltdown. (total server count: TotalServersCount successful count: SuccessfulReplyCount).

Fields #

Name	Description
`TotalServersCount`
`SuccessfulReplyCount`

Event ID 728: Skipped bugcheck since another request is already in progress.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Skipped bugcheck since another request is already in progress. (BugcheckReason=BugcheckReason)

Fields #

Name	Description
`BugcheckReason`

Event ID 729: Attempting to cause BugCheck.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempting to cause BugCheck. (LastBootTime=LastBootTime, BugcheckReason=BugcheckReason)

Fields #

Name	Description
`LastBootTime`
`BugcheckReason`

Event ID 730: Skipped bugcheck due to store as registry key 'DisabledRegKey' has disabled it until 'DisabledTimeUtc'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Skipped bugcheck due to store as registry key 'DisabledRegKey' has disabled it until 'DisabledTimeUtc'. (BugcheckReason=BugcheckReason)

Fields #

Name	Description
`BugcheckReason`
`DisabledRegKey`
`DisabledTimeUtc`

Event ID 731: Initiating local Store Rpc to mount database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating local Store Rpc to mount database 'DatabaseGuid'.

Fields #

Name	Description
`DatabaseGuid`
`Flags`

Event ID 732: Successfully finished local mount for database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Successfully finished local mount for database 'DatabaseGuid'.

Fields #

Name	Description
`DatabaseGuid`

Event ID 733: Failed local Store Mount Rpc for database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed local Store Mount Rpc for database 'DatabaseGuid'. Error: ErrorMessage.

Fields #

Name	Description
`DatabaseGuid`
`ErrorMessage`
`Exception`

Event ID 734: Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' is being skipped because it is of an incompatible version.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery request created at RequestCreationTimeUtc (UTC) for database 'DatabaseName' is being skipped because it is of an incompatible version. [ WasRedeliveryRequired=WasRedeliveryRequired, WasEXORedeliveryRequired=WasEXORedeliveryRequired, ServerVersion=ServerVersion, RequestVersion=RequestVersion, RequestGuid=RequestGuid ]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`IsRequestInOldDumpsterSchema`
`RequestCreationTimeUtc`
`RequestKey`
`RequestValue`
`WasRedeliveryRequired`
`ServerVersion`
`RequestVersion`
`RequestGuid`
`WasEXORedeliveryRequired`

Event ID 735: An ExceededDatabaseMaxSize error on database 'DatabaseName' was encountered that triggered a clean dismount attempt.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An ExceededDatabaseMaxSize error on database 'DatabaseName' was encountered that triggered a clean dismount attempt. This dismount failed: Message

Fields #

Name	Description
`DatabaseName`
`Message`

Event ID 736: Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) was a...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery resubmit RPC to HUB Transport server HubServer to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) was a duplicate. The HUB Transport server has already successfully received this request, so this request will be marked as successfully completed. [ RequestGuid=RequestGuid ]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`RequestCreationTimeUtc`
`StartTimeUtc`
`EndTimeUtc`
`HubServer`
`RequestGuid`

Event ID 737: Dumpster redelivery resubmit RPC to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) will be next attempted at NextDueTimeUtc (UTC).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dumpster redelivery resubmit RPC to resubmit messages for database 'DatabaseName' between time periods StartTimeUtc (UTC) and EndTimeUtc (UTC) will be next attempted at NextDueTimeUtc (UTC). [ RequestGuid=RequestGuid ]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`RequestCreationTimeUtc`
`StartTimeUtc`
`EndTimeUtc`
`NextDueTimeUtc`
`RequestGuid`

Event ID 738: Replay Lag Manager suppressed a request to disable replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of DisableSuppression.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager suppressed a request to disable replay lag for database copy 'DatabaseName\ServerName' after a suppression interval of DisableSuppression. Disable Reason: DisableReason

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`DisableReason`
`DisableSuppression`

Event ID 739: The store service is being killed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The store service is being killed. A diagnostic dump will first be attempted.

Event ID 740: A diagnostic dump has been sent prior to killing the store service.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

A diagnostic dump has been sent prior to killing the store service. Reason: Reason. Detail: Detail. Duration: WatsonDuration.

Fields #

Name	Description
`Reason`
`Detail`
`WatsonDuration`
`StackTrace`

Event ID 747: ESE staging flags are configured to: FlagsString (FlagsInt) on MachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ESE staging flags are configured to: FlagsString (FlagsInt) on MachineName.

Fields #

Name	Description
`MachineName`
`FlagsString`
`FlagsInt`

Event ID 748: Log Replay suspend/resume state for database 'DatabaseName' has changed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log Replay suspend/resume state for database 'DatabaseName' has changed. (LastSuspendReason=LastSuspendReasonCode, CurrentSuspendReason=CurrentSuspendReasonCode, CurrentSuspendReasonMessage=CurrentSuspendReasonMessage)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LastSuspendReasonCode`
`CurrentSuspendReasonCode`
`CurrentSuspendReasonMessage`

Event ID 750: Replay Lag Manager requested activating replay lag delay (suspending log replay) for database copy 'DatabaseName\ServerName' after a suppression interval of DelaySuppression.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager requested activating replay lag delay (suspending log replay) for database copy 'DatabaseName\ServerName' after a suppression interval of DelaySuppression. Delay Reason: DelayReason

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`DelaySuppression`
`ResourceLoadState`
`DelayReason`

Event ID 751: Replay Lag Manager successfully activated replay lag delay (suspended log replay) for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager successfully activated replay lag delay (suspended log replay) for database copy 'DatabaseName\ServerName'. Delay Reason: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 752: Replay Lag Manager failed to activate replay lag delay (suspend log replay) for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager failed to activate replay lag delay (suspend log replay) for database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`
`Message2`

Event ID 753: Replay Lag Manager requested deactivating replay lag (resuming log replay) for database copy 'DatabaseName\ServerName' after a suppression interval of EnableSuppression.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager requested deactivating replay lag (resuming log replay) for database copy 'DatabaseName\ServerName' after a suppression interval of EnableSuppression. Reason: UndelayReason

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`EnableSuppression`
`UndelayReason`

Event ID 754: Replay Lag Manager successfully deactivated replay lag (resumed log replay) for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager successfully deactivated replay lag (resumed log replay) for database copy 'DatabaseName\ServerName'. Reason: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 755: Replay Lag Manager failed to deactivate replay lag (resume log replay) for database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager failed to deactivate replay lag (resume log replay) for database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`
`Message2`

Event ID 756: Replay Lag Manager will attempt to deactivate replay lag (resume log replay) for database copy 'DatabaseName\ServerName' because it has reached the maximum allowed l...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Replay Lag Manager will attempt to deactivate replay lag (resume log replay) for database copy 'DatabaseName\ServerName' because it has reached the maximum allowed lag duration. Detailed Reason: UndelayReason

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`EnableSuppression`
`UndelayReason`

Event ID 780: The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for longer than 'ThresholdDuration' duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for longer than 'ThresholdDuration' duration. The IO has been hung for at least 'IOHangDuration' duration. This could indicate a storage issue on the machine which a reboot usually resolves.

Fields #

Name	Description
`Path`
`ThresholdDuration`
`IOHangDuration`

Event ID 781: The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for a very long time (longer than the BugCheck threshold duration of 'ThresholdDuration').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Win32 GetDiskFreeSpaceEx() call for path 'Path' has been pending for a very long time (longer than the BugCheck threshold duration of 'ThresholdDuration'). The IO has been hung for at least 'IOHangDuration' duration. A BugCheck will be attempted to resolve the storage hang.

Fields #

Name	Description
`Path`
`ThresholdDuration`
`IOHangDuration`

Event ID 800: BlockMode replication for database 'DatabaseName' failed to initialize with the passive copy on 'ServerName' : Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockMode replication for database 'DatabaseName' failed to initialize with the passive copy on 'ServerName' : Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 801: BlockModeReplication was unable to drain the write queue for passive database 'DatabaseName' after a timeout of 'TimeoutInterval'.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockModeReplication was unable to drain the write queue for passive database 'DatabaseName' after a timeout of 'TimeoutInterval'.

Fields #

Name	Description
`DatabaseName`
`TimeoutInterval`
`StackTrace`

Event ID 802: Database 'DatabaseName' is not replicated, yet constraint is not set to None in AD.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' is not replicated, yet constraint is not set to None in AD. It is set to 'Constraint'.

Fields #

Name	Description
`DatabaseName`
`Constraint`

Event ID 803: Database 'DatabaseName' is replicated, but constraint 'Constraint' is not supported.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' is replicated, but constraint 'Constraint' is not supported.

Fields #

Name	Description
`DatabaseName`
`Constraint`

Event ID 804: Database 'DatabaseName' last log generation number ServerName received by the passive copy on server 'PassiveLogCopyGeneration' is higher than current active copy generation number ActiveLogCopyGen...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' last log generation number ServerName received by the passive copy on server 'PassiveLogCopyGeneration' is higher than current active copy generation number ActiveLogCopyGeneration.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`PassiveLogCopyGeneration`
`ActiveLogCopyGeneration`

Event ID 805: Database 'DatabaseName' last log generation number PassiveLogCopyGeneration acknowledgement sent by the passive copy on server 'ServerName' is stale.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' last log generation number PassiveLogCopyGeneration acknowledgement sent by the passive copy on server 'ServerName' is stale. It was last received at TimeRecieved UTC.

Fields #

Name	Description
`DatabaseName`
`PassiveLogCopyGeneration`
`ServerName`
`TimeRecieved`

Event ID 806: Database 'DatabaseName' best copy could not be found.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' best copy could not be found. Details: Details

Fields #

Name	Description
`DatabaseName`
`Details`

Event ID 807: Database 'DatabaseName' most up-to-date copy is on server 'ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' most up-to-date copy is on server 'ServerName'. It's last log copied number is PassiveLogCopyGeneration and it was acknowledged at TimeRecieved. Last inspected log number is PassiveLogInspectionGeneration and last replayed log number is PassiveLogReplayGeneration.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`PassiveLogCopyGeneration`
`TimeRecieved`
`PassiveLogInspectionGeneration`
`PassiveLogReplayGeneration`

Event ID 808: Database 'DatabaseGuid' throttling data is updated for the first time after mount.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseGuid' throttling data is updated for the first time after mount.

Fields #

Name	Description
`DatabaseGuid`

Event ID 809: Database 'DatabaseName' throttling constraint is None.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' throttling constraint is None. This database will not be throttled.

Fields #

Name	Description
`DatabaseName`

Event ID 810: Database 'DatabaseName' is throttled based on following values: data protection health is DataProtectionHealth and data availability health is DataAvailabilityHealth.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' is throttled based on following values: data protection health is DataProtectionHealth and data availability health is DataAvailabilityHealth.

Fields #

Name	Description
`DatabaseName`
`DataProtectionHealth`
`DataAvailabilityHealth`

Event ID 811: At initialization, database copy 'DatabaseName\ServerName' has logs in the generation range (LowestGenerationPresent - HighestGenerationPresent) and required logs in the range (LowestGenerationRequ...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

At initialization, database copy 'DatabaseName\ServerName' has logs in the generation range (LowestGenerationPresent - HighestGenerationPresent) and required logs in the range (LowestGenerationRequired - HighestGenerationRequired). [NumberOfPartitionsAttached=NumberOfPartitionsAttached, SecondaryPartitionExcludeReasonCode=SecondaryPartitionExcludeReasonCode, SecondaryPartitionExcludeReason = SecondaryPartitionExcludeReason]

Fields #

Name	Description
`DatabaseName`
`ServerName`
`LowestGenerationRequired`
`HighestGenerationRequired`
`LowestGenerationPresent`
`HighestGenerationPresent`
`NumberOfPartitionsAttached`
`SecondaryPartitionExcludeReasonCode`
`SecondaryPartitionExcludeReason`

Event ID 812: Primary Active Manager is not responding to other servers or it is not in valid role (Pam=ServerName, Role=Role, Exception=Exception, ErrorMessage=ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Primary Active Manager is not responding to other servers or it is not in valid role (Pam=ServerName, Role=Role, Exception=Exception, ErrorMessage=ErrorMessage)

Fields #

Name	Description
`ServerName`
`Role`
`Exception`
`ErrorMessage`

Event ID 813: PAM health monitor encountered an exception while trying to check the health (Error=ErrorMessage, Phase=Phase).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor encountered an exception while trying to check the health (Error=ErrorMessage, Phase=Phase)

Fields #

Name	Description
`ErrorMessage`
`Phase`

Event ID 814: PAM health monitor cancelled the attempt to move PAM since the server changed between verification and recovery.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor cancelled the attempt to move PAM since the server changed between verification and recovery (PamAtVerification=PamAtVerification, PamAtRecovery=PamAtRecovery)

Fields #

Name	Description
`PamAtVerification`
`PamAtRecovery`

Event ID 815: PAM health monitor cancelled the attempt to move PAM since it got valid reply from a PAM server in the DAG (Server=PamServerName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor cancelled the attempt to move PAM since it got valid reply from a PAM server in the DAG (Server=PamServerName)

Fields #

Name	Description
`PamServerName`

Event ID 816: PAM health monitor successfully moved PAM (From=FromServer, To=ToServer).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor successfully moved PAM (From=FromServer, To=ToServer)

Fields #

Name	Description
`FromServer`
`ToServer`

Event ID 817: PAM health monitor could not find any server with valid role to move PAM.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor could not find any server with valid role to move PAM

Event ID 818: Active manager configuration is not initialized.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager configuration is not initialized. (Duration=Duration, Result=Result, Operation=Operation)

Fields #

Name	Description
`Duration`
`Result`
`Operation`

Event ID 819: PAM health monitor is attempting to move PAM (From=FromServer, To=ToServer).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM health monitor is attempting to move PAM (From=FromServer, To=ToServer)

Fields #

Name	Description
`FromServer`
`ToServer`

Event ID 820: AD lookup failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

AD lookup failed: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 821: Seeding to the local copy of database 'DatabaseName' ('DatabaseGuid') failed: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding to the local copy of database 'DatabaseName' ('DatabaseGuid') failed: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`

Event ID 822: CI Seeding has begun for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI Seeding has begun for database 'DatabaseName'. This server is the source now transferring data.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 823: CI Seeding failed for database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI Seeding failed for database 'DatabaseGuid'. This server failed to act as the source of the data. Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 824: CI Seeding encounted an error while processing database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI Seeding encounted an error while processing database 'DatabaseName' (DatabaseGuid). Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 825: DB Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

DB Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid).

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`

Event ID 826: DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid).

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`

Event ID 827: CI Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid). Reason:SeedReason.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`SeedReason`

Event ID 828: CI is trying to resume indexing for the local copy of database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI is trying to resume indexing for the local copy of database 'DatabaseName' (DatabaseGuid).

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`SeedReason`

Event ID 829: Seeding log files failed on the source side while processing database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding log files failed on the source side while processing database 'DatabaseName' (DatabaseGuid). Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 830: Seeding failed on the source side while processing database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding failed on the source side while processing database 'DatabaseName' (DatabaseGuid). Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`ErrorMessage`

Event ID 831: Incremental Reseed (DatabaseName\ServerName) started saving old logs from gen Message1 to gen Message2 to dir Message3.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) started saving old logs from gen Message1 to gen Message2 to dir Message3

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`
`Message3`

Event ID 832: Incremental Reseed (DatabaseName\ServerName) started moving new logs from gen Message1 to gen Message2 from dir Message3.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) started moving new logs from gen Message1 to gen Message2 from dir Message3

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`
`Message3`

Event ID 833: The copy of 'DatabaseName' has been marked for stop.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The copy of 'DatabaseName' has been marked for stop. It was running as CopyRole.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LocalNodeName`
`CopyRole`
`Stack`

Event ID 834: The copy 'DatabaseName\ServerName' is starting with no logs.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy 'DatabaseName\ServerName' is starting with no logs. Global truncation coordination will be used to determine the starting generation.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`

Event ID 835: The copy 'DatabaseName\ServerName' received gen Message1 from global coordinator.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy 'DatabaseName\ServerName' received gen Message1 from global coordinator.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 836: The copy 'DatabaseName\ServerName' found log reset pending with gen Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy 'DatabaseName\ServerName' found log reset pending with gen Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 837: The local copy of 'DatabaseName' is starting with first log to copy at gen StartingGen.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The local copy of 'DatabaseName' is starting with first log to copy at gen StartingGen. Active is ActiveServer

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StartingGen`
`ActiveServer`

Event ID 838: The copy 'DatabaseName\ServerName' failed to get start gen from global coordinator.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy 'DatabaseName\ServerName' failed to get start gen from global coordinator. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 839: The log copier for 'DatabaseName\ServerName' is starting with the lowest generation on the source at gen Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The log copier for 'DatabaseName\ServerName' is starting with the lowest generation on the source at gen Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 840: Database 'DatabaseName' failed to mount on server 'ServerFqdn' due to timeout: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' failed to mount on server 'ServerFqdn' due to timeout: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ServerFqdn`
`ErrorMessage`

Event ID 841: ListMdbStatus failed to server 'NodeName': Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ListMdbStatus failed to server 'NodeName': Message

Fields #

Name	Description
`NodeName`
`Message`

Event ID 842: ListMdbStatus = MdbStatusFlags for database 'DatabaseName' (DatabaseGuid) on MailboxServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ListMdbStatus = MdbStatusFlags for database 'DatabaseName' (DatabaseGuid) on MailboxServer

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`MailboxServer`
`MdbStatusFlags`

Event ID 843: Recovery from ListMdbStatus failure is being attempted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovery from ListMdbStatus failure is being attempted. The local Store service will be terminated.

Event ID 844: Recovery from ListMdbStatus failure is being attempted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovery from ListMdbStatus failure is being attempted. All databases on NodeName will be dismounted.

Fields #

Name	Description
`NodeName`

Event ID 845: Failed to close the backup reader handle for database 'DatabaseName' ('DatabaseGuid').

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Failed to close the backup reader handle for database 'DatabaseName' ('DatabaseGuid'). Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ErrorMessage`

Event ID 846: Database 'DatabaseName' has no copies and is being ignored.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' has no copies and is being ignored.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 847: GetDiskFreeSpaceEx failed with error ErrorCode using path 'DatabasePath' for database DatabaseGuid.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

GetDiskFreeSpaceEx failed with error ErrorCode using path 'DatabasePath' for database DatabaseGuid. Loose truncation is not possible.

Fields #

Name	Description
`DatabaseGuid`
`ErrorCode`
`DatabasePath`

Event ID 848: Low disk space exists on the active (local) copy of database DatabaseGuid.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Low disk space exists on the active (local) copy of database DatabaseGuid. The copy on 'PassiveServerName' last reported generation GenIgnored which is being ignored to allow other copies to truncate.

Fields #

Name	Description
`DatabaseGuid`
`PassiveServerName`
`GenIgnored`

Event ID 849: The IoBufferPool used by block mode replication was initialized with BufferCount buffers.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The IoBufferPool used by block mode replication was initialized with BufferCount buffers. Details: Explanation

Fields #

Name	Description
`BufferCount`
`Explanation`

Event ID 850: Mount status validation failed after database 'DatabaseName' could not be moved from 'ActiveServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Mount status validation failed after database 'DatabaseName' could not be moved from 'ActiveServer'. Active manager expected 'ActiveManagerMountStatus' but got 'StoreMountStatus' from store.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`
`ActiveManagerMountStatus`
`StoreMountStatus`

Event ID 851: Full server reseed is being started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed is being started. Any database copies that have experienced a failure will be reseeded to their existing volumes.

Event ID 852: Full server reseed is first attempting to resume database copy 'DatabaseName\ServerName' to avoid a reseed if possible.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed is first attempting to resume database copy 'DatabaseName\ServerName' to avoid a reseed if possible. A reseed will be attempted in 5 minutes if the database copy is still not in a Healthy state.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`

Event ID 853: Full server reseed failed to resume database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed failed to resume database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 854: Full server reseed encountered an error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed encountered an error. Error: Message

Fields #

Name	Description
`Message`

Event ID 855: Full server reseed has completed kicking off reseeds.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed has completed kicking off reseeds. Number of copies resume was attempted on: Message1 Number of copies reseed was attempted on: Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 856: Full server reseed is now attempting to reseed database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed is now attempting to reseed database copy 'DatabaseName\ServerName'.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`

Event ID 857: Full server reseed failed to reseed database copy 'DatabaseName\ServerName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed failed to reseed database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 858: Full server reseed is being skipped because the Microsoft Exchange Replication service is being stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Full server reseed is being skipped because the Microsoft Exchange Replication service is being stopped.

Event ID 859: Another instance of a full server reseed is already running.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Another instance of a full server reseed is already running.

Event ID 860: Database 'DatabaseName' is active on a disfavored server but cannot be moved because all servers are marked with DatabaseCopyActivationDisabledAndMoveNow.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' is active on a disfavored server but cannot be moved because all servers are marked with DatabaseCopyActivationDisabledAndMoveNow.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 861: Loose truncation is being used on database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Loose truncation is being used on database 'DatabaseName'. Generation LooseTruncGen is used in place of StandardTruncGen.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StandardTruncGen`
`LooseTruncGen`

Event ID 862: Truncation for database 'DatabaseGuid' was unable to find file 'MissingFileName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Truncation for database 'DatabaseGuid' was unable to find file 'MissingFileName'. Normally this is due to a lagging passive and recovery will be automatic.

Fields #

Name	Description
`DatabaseGuid`
`MissingFileName`

Event ID 863: The support api failed to start: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The support api failed to start: Message

Fields #

Name	Description
`Message`

Event ID 864: The TCP listener has started listening on port Port.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The TCP listener has started listening on port Port.

Fields #

Name	Description
`Port`

Event ID 865: Serialization failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Serialization failed: Message

Fields #

Name	Description
`Message`

Event ID 866: Truncation for database 'DatabaseGuid' is paused because a backup is in progress.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Truncation for database 'DatabaseGuid' is paused because a backup is in progress.

Fields #

Name	Description
`DatabaseGuid`

Event ID 867: CI Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid).

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

CI Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid). Reason: SeedReason. Status: Status. ErrorMessage: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`SeedReason`
`Status`
`ErrorMessage`

Event ID 868: The TCP listener failed to start listening on port Port.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The TCP listener failed to start listening on port Port. Error: Error

Fields #

Name	Description
`Port`
`Error`

Event ID 869: Windows is configured for scavenge replication on port Port.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Windows is configured for scavenge replication on port Port.

Fields #

Name	Description
`Port`

Event ID 870: Windows is not configured for scavenge replication.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Windows is not configured for scavenge replication.

Event ID 871: Windows is failed to configure for scavenge replication on port Port.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Windows is failed to configure for scavenge replication on port Port. Error:Error

Fields #

Name	Description
`Port`
`Error`

Event ID 872: Replication for passive copy of DatabaseName is switching to scavenge.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Replication for passive copy of DatabaseName is switching to scavenge. Reason: Reason.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Reason`

Event ID 873: Replication for passive copy of DatabaseName is switching to normal.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Replication for passive copy of DatabaseName is switching to normal. Reason: Reason.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Reason`

Event ID 874: Active Directory is in a failed state.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Directory is in a failed state. ComponentTag: ComponentTag. Error: Error

Fields #

Name	Description
`ComponentTag`
`Error`

Event ID 875: The replication TCP port stored in the registry failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The replication TCP port stored in the registry failed. Operation: Operation. Error Error

Fields #

Name	Description
`Operation`
`Error`

Event ID 876: FileMode for database 'DatabaseName' is connected at gen StartingGen with the active on ActiveServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

FileMode for database 'DatabaseName' is connected at gen StartingGen with the active on ActiveServer

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StartingGen`
`ActiveServer`
`LocalEndPoint`
`SendingEndPoint`

Event ID 877: Log file 'LogFileName' has unexpected signature 'LogFileSig' instead of 'ExpectedSig'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log file 'LogFileName' has unexpected signature 'LogFileSig' instead of 'ExpectedSig'.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`LogFileName`
`LogFileSig`
`ExpectedSig`
`ActualHex`
`ExpectedHex`
`Stack`

Event ID 878: Thread priority was not downgraded: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Thread priority was not downgraded: Message.

Fields #

Name	Description
`Message`

Event ID 879: FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) was defer-attached and hence is outdated with respect to the current log stream.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) was defer-attached and hence is outdated with respect to the current log stream. [CheckpointGeneration: CheckpointGen, MinRequiredGen: MinRequiredGen, LowestGenerationPresent: LowestGenerationPresent]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PartitionID`
`DbState`
`MinRequiredGen`
`CheckpointGen`
`EdbFilePath`
`CheckpointFilePath`
`LowestGenerationPresent`

Event ID 880: FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is not attached.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is not attached. [CheckpointGeneration: CheckpointGen, LastConsistentGen: LastConsistentGen, LowestGenerationPresent: LowestGenerationPresent]

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PartitionID`
`DbState`
`LastConsistentGen`
`CheckpointGen`
`EdbFilePath`
`CheckpointFilePath`
`LowestGenerationPresent`

Event ID 881: FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is missing.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is missing.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`PartitionID`
`EdbFilePath`

Event ID 882: File-mode replication for database 'DatabaseName' is starting with passive PassiveServer at generation LogGen.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

File-mode replication for database 'DatabaseName' is starting with passive PassiveServer at generation LogGen.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LogGen`
`PassiveServer`
`LocalEndPoint`
`ReceivingEndPoint`

Event ID 883: File-mode replication for database 'DatabaseName' is terminating with passive PassiveServer at generation LogGen.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

File-mode replication for database 'DatabaseName' is terminating with passive PassiveServer at generation LogGen.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LogGen`
`PassiveServer`
`LocalEndPoint`
`ReceivingEndPoint`

Event ID 884: Deletion of file 'Message1' which is part of database copy 'DatabaseName\ServerName' failed with error: Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Deletion of file 'Message1' which is part of database copy 'DatabaseName\ServerName' failed with error: Message2

Fields #

Name	Description
`DatabaseName`
`ServerName`
`Message1`
`Message2`

Event ID 900: The passive copy of 'DatabaseName' is starting its components.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The passive copy of 'DatabaseName' is starting its components. ActiveServer=ActiveServer

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`

Event ID 901: The copy of 'DatabaseName' encountered an unusual situation: Details.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The copy of 'DatabaseName' encountered an unusual situation: Details

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Details`

Event ID 902: ACLL starting for 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ACLL starting for 'DatabaseName'. Active is ActiveServer.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`PAMOperationId`

Event ID 903: ACLL for 'DatabaseName' finished after Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ACLL for 'DatabaseName' finished after Duration.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Duration`
`PAMOperationId`

Event ID 904: ACLL for 'DatabaseName' failed after Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ACLL for 'DatabaseName' failed after Duration. Error:PAMOperationId

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Duration`
`PAMOperationId`
`Error`

Event ID 905: Mount for local copy of 'DatabaseName' is starting.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Mount for local copy of 'DatabaseName' is starting.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 906: IncrementalReseed for 'DatabaseName' is replacing OldLog with NewLog.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

IncrementalReseed for 'DatabaseName' is replacing OldLog with NewLog

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`OldLog`
`NewLog`
`LogGen`

Event ID 907: Acll for 'DatabaseName' failed due to an active incompatible operation: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Acll for 'DatabaseName' failed due to an active incompatible operation: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`PAMOperationId`
`Error`

Event ID 908: Mount for 'DatabaseName' failed due to an active incompatible operation: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Mount for 'DatabaseName' failed due to an active incompatible operation: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 909: Database 'DatabaseName' was seeded to TargetServer.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Database 'DatabaseName' was seeded to TargetServer. Success=Success.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TargetServer`
`Success`
`StartTime`
`ElapsedTime`
`TotalBytes`
`BytesPerSecond`
`TotalThrottleDelayTime`
`ThrottleStatus`

Event ID 910: DB Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

DB Seeding has begun for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`EdbFilePath`
`ErrorMessage`

Event ID 911: DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'. Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`EdbFilePath`
`ErrorMessage`

Event ID 912: Seeding file 'EdbFilePath' for the local copy of database 'DatabaseName' (DatabaseGuid) is being skipped because this database file has not been configured or the underlying st...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding file 'EdbFilePath' for the local copy of database 'DatabaseName' (DatabaseGuid) is being skipped because this database file has not been configured or the underlying storage is inaccessible. Reason: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`EdbFilePath`
`ErrorMessage`

Event ID 913: Failed to close the backup reader file handle for 'EdbFilePath' of database 'DatabaseName' ('DatabaseGuid').

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Failed to close the backup reader file handle for 'EdbFilePath' of database 'DatabaseName' ('DatabaseGuid'). Error: ErrorMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`EdbFilePath`
`ErrorMessage`

Event ID 1000: BlockMode replication could not obtain the lock on the timer.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockMode replication could not obtain the lock on the timer. Recovery should be automatic.

Fields #

Name	Description
`DatabaseName`
`LockTimeoutLimit`

Event ID 1001: A client-side network connection to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A client-side network connection to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' succeeded.

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`

Event ID 1002: A client-side attempt to connect to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' failed: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A client-side attempt to connect to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' failed: Error

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`
`Error`

Event ID 1003: Database redundancy health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database redundancy health check failed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1004: Database redundancy health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database redundancy health check passed. Database: DatabaseName Redundancy count: HealthyCopiesCount IsSuppressed: IsSuppressed Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`
`IsSuppressed`

Event ID 1005: Database site-level redundancy health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database site-level redundancy health check failed. You can ignore this error if you have deployed only 1 Active Directory site. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckSiteAlertsDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1006: Database site-level redundancy health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database site-level redundancy health check passed. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckSiteAlertsDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1007: Database availability health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database availability health check failed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1008: Database availability health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database availability health check passed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1009: Database site-level availability health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database site-level availability health check failed. You can ignore this error if you have deployed an Active/Passive datacenter configuration, or if you have deployed only 1 Active Directory site. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckSiteAlertsDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1010: Database site-level availability health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database site-level availability health check passed. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckSiteAlertsDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1011: Health validation check 'CheckName' for database copy 'DatabaseCopyName' produced a Warning.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Health validation check 'CheckName' for database copy 'DatabaseCopyName' produced a Warning. Error: ErrorMessage

Fields #

Name	Description
`DatabaseCopyName`
`CheckName`
`ErrorMessage`

Event ID 1012: Database Health Monitor component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Monitor component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1013: A server-side connection is open with client RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A server-side connection is open with client RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`

Event ID 1014: A server-side connection was closed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A server-side connection was closed. Client RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`

Event ID 1015: A client-side connection was closed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A client-side connection was closed. Server RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`

Event ID 1016: A server-side idle connection is being closed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

A server-side idle connection is being closed. Client RemoteNodeName was idle since IdleSinceUtc (IdleTimespan). Client was using 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

Name	Description
`RemoteNodeName`
`RemoteEndpoint`
`LocalEndpoint`
`IdleSinceUtc`
`IdleTimespan`

Event ID 1017: Database redundancy two-copy health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database redundancy two-copy health check passed. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckRedundancyTwoCopyAlertDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1018: Database redundancy two-copy health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database redundancy two-copy health check failed. You can ignore this error if you have less than 3 database copies configured. This event can be disabled by setting the following regkey to 1: 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters -> DatabaseHealthCheckRedundancyTwoCopyAlertDisabled'. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`ErrorMessage`
`DatabaseGuid`

Event ID 1019: An inconsistency was detected by network discovery: 'Message' Normally this is due to transient network configuration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

An inconsistency was detected by network discovery: 'Message' Normally this is due to transient network configuration.

Fields #

Name	Description
`Message`

Event ID 1020: This server rejected a connection attempt from remote 'RemoteEndpoint' to 'LocalEndpoint'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Network

Description

This server rejected a connection attempt from remote 'RemoteEndpoint' to 'LocalEndpoint'. Error: Error

Fields #

Name	Description
`RemoteEndpoint`
`LocalEndpoint`
`Error`

Event ID 1021: Database 'DatabaseName' appears to have a copy status cached entry that has not been updated recently.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' appears to have a copy status cached entry that has not been updated recently. This could mean that the GetCopyStatus() RPC call is hung. As automatic recovery, the MSExchangeRepl and MSExchangeDagMgmt services will be restarted, followed by a server reboot within 30 mins.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 1022: Some databases on server 'Message1' have copy status cached entries that have not been updated recently.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Some databases on server 'Message1' have copy status cached entries that have not been updated recently. This could mean that the GetCopyStatus() RPC call is hung. As automatic recovery, the MSExchangeRepl and MSExchangeDagMgmt services will be restarted, followed by a server reboot within 30 mins. Affected Databases: Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 1023: Database remote connectivity health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database remote connectivity health check failed. Database: DatabaseName Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 1024: Database remote connectivity health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database remote connectivity health check passed. Database: DatabaseName

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 1025: Health validation check 'CheckName' for database copy 'DatabaseCopyName' is being suppressed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Health validation check 'CheckName' for database copy 'DatabaseCopyName' is being suppressed. Error: ErrorMessage

Fields #

Name	Description
`DatabaseCopyName`
`CheckName`
`ErrorMessage`

Event ID 1026: All databases on server 'Message' have copy status cached entries that have been updated recently.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

All databases on server 'Message' have copy status cached entries that have been updated recently.

Fields #

Name	Description
`Message`

Event ID 1027: PAM monitor failure to restart ClusSvc on Server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM monitor failure to restart ClusSvc on Server. Status of the request: IsSkippedDueToRegistryOverride: IsSkippedDueToRegistryOverride, IsSkippedDueToTimeCheck: IsSkippedDueToTimeCheck, IsThrottled: IsThrottled, Error (if any): ErrorMessage

Fields #

Name	Description
`Server`
`IsSkippedDueToRegistryOverride`
`IsSkippedDueToTimeCheck`
`IsThrottled`
`ErrorMessage`

Event ID 1028: PAM monitor successfully restarted ClusSvc on Server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM monitor successfully restarted ClusSvc on Server.

Fields #

Name	Description
`Server`

Event ID 1029: Database RPC Authentication health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database RPC Authentication health check failed. Database: DatabaseName Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`

Event ID 1030: Database RPC Authentication health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database RPC Authentication health check passed. Database: DatabaseName

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 1031: The Database Health Monitor component found database copies with the following secondary partition health states: HealthyCount=HealthyCount OfflineCount=OfflineCount U...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

The Database Health Monitor component found database copies with the following secondary partition health states: HealthyCount=HealthyCount OfflineCount=OfflineCount UnknownCount=UnknownCount InitializingCount=InitializingCount DisabledCount=DisabledCount StorageUnavailableCount=StorageUnavailableCount StorageOfflineCount=StorageOfflineCount SeedingCount=SeedingCount NotSupportedCount=NotSupportedCount McdbResetsInLastDayCount=McdbResetsInLastDayCount McdbResetsInLastWeekCount=McdbResetsInLastWeekCount McdbResetsInLastMonthCount=McdbResetsInLastMonthCount ---HealthyList--- HealthyList ---OfflineList--- OfflineList ---UnknownList--- UnknownList ---InitializingList--- InitializingList ---DisabledList--- DisabledList ---StorageUnavailableList--- StorageUnavailableList ---StorageOfflineList--- StorageOfflineList ---SeedingList--- SeedingList ---NotSupportedList--- NotSupportedList ---McdbResetsInLastDayList--- McdbResetsInLastDayList

Fields #

Name	Description
`UnknownCount`
`DisabledCount`
`StorageUnavailableCount`
`StorageOfflineCount`
`OfflineCount`
`HealthyCount`
`SeedingCount`
`NotSupportedCount`
`UnknownList`
`DisabledList`
`StorageUnavailableList`
`StorageOfflineList`
`OfflineList`
`HealthyList`
`SeedingList`
`NotSupportedList`
`McdbResetsInLastDayCount`
`McdbResetsInLastDayList`
`McdbResetsInLastWeekCount`
`McdbResetsInLastMonthCount`
`InitializingCount`
`InitializingList`

Event ID 1100: Managed Availability health tracker encountered an error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Managed Availability health tracker encountered an error. Hint:Message, Error:'StackTrace'.

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1101: Initiating move of all active databases requested by a managed availability component (Node=NodeName, Component=ComponentName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating move of all active databases requested by a managed availability component (Node=NodeName, Component=ComponentName).

Fields #

Name	Description
`NodeName`
`ComponentName`

Event ID 1102: Finished moving all active databases requested by a managed availability component (Node=NodeName, Databases=DatabaseCount, MoveComment=MoveComment, Component=ComponentName).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Finished moving all active databases requested by a managed availability component (Node=NodeName, Databases=DatabaseCount, MoveComment=MoveComment, Component=ComponentName).

Fields #

Name	Description
`NodeName`
`DatabaseCount`
`MoveComment`
`ComponentName`

Event ID 1103: Server: ServerName HealthStates: HealthStates.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Server: ServerName HealthStates: HealthStates

Fields #

Name	Description
`ServerName`
`HealthStates`

Event ID 1104: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

Name	Description
`AppLogEventID`
`AppLogEventMessage`
`AppLogEventArgs`

Event ID 1105: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

Name	Description
`AppLogEventID`
`AppLogEventMessage`
`AppLogEventArgs`

Event ID 1106: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

Name	Description
`AppLogEventID`
`AppLogEventMessage`
`AppLogEventArgs`

Event ID 1107: Automatic Reseed Manager component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1108: Automatic Reseed Manager component encountered an error when processing database 'DatabaseName': ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager component encountered an error when processing database 'DatabaseName': ErrorMessage

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ErrorMessage`
`ExceptionFullString`

Event ID 1109: Automatic Reseed Manager is starting repair workflow 'WorkflowName' for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager is starting repair workflow 'WorkflowName' for database 'DatabaseName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1110: Automatic Reseed Manager successfully completed repair workflow 'WorkflowName' for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager successfully completed repair workflow 'WorkflowName' for database 'DatabaseName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1111: Automatic Reseed Manager failed to execute repair workflow 'WorkflowName' for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to execute repair workflow 'WorkflowName' for database 'DatabaseName'. Error: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ErrorMessage`

Event ID 1112: Automatic Reseed Manager has detected a content indexing error for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has detected a content indexing error for database 'DatabaseName'. The catalog may be corrupted and will be reseeded automatically. ContentIndexError: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1113: Automatic Reseed Manager has detected single copy of the content index for database 'DatabaseName' that is in a suitable state for seeding.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has detected single copy of the content index for database 'DatabaseName' that is in a suitable state for seeding.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1114: Automatic Reseed Manager has detected no copy of the content index for database 'DatabaseName' that is in a suitable state for seeding.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has detected no copy of the content index for database 'DatabaseName' that is in a suitable state for seeding.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1115: Unable to read database 'DatabaseName' throttling configuration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Unable to read database 'DatabaseName' throttling configuration. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 1116: Server-level health validation check failed to update the LastRunTime in the local registry.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Server-level health validation check failed to update the LastRunTime in the local registry. Error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1117: Automatic Reseed Manager throttled repair workflow 'WorkflowName' for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager throttled repair workflow 'WorkflowName' for database 'DatabaseName'. Details: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ErrorMessage`

Event ID 1118: Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because of a previous fatal error that is preventing it.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because of a previous fatal error that is preventing it. The workflow will next attempt to assign a spare volume and reseed the database copy. ResumeBlocked Error: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ErrorMessage`

Event ID 1119: Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to resume database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts. The workflow will next attempt to assign a spare volume and reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`MaxRetries`

Event ID 1120: Automatic Reseed Manager failed to reseed database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to reseed database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts. The workflow will next run after 'WorkflowNextRunAfter'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`MaxRetries`
`WorkflowNextRunAfter`

Event ID 1121: Automatic Reseed Manager failed to assign a spare volume for database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to assign a spare volume for database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts. The workflow will next attempt to reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`MaxRetries`

Event ID 1122: Automatic Reseed Manager recently assigned a spare volume for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager recently assigned a spare volume for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'. The workflow will next attempt to reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1123: Automatic Reseed Manager is skipping a reseed of database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because the data protection delay of 'ConfiguredDelay' has n...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager is skipping a reseed of database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because the data protection delay of 'ConfiguredDelay' has not been met. The database copy has only been FailedAndSuspended for a duration of 'FailedElapsedTime'. The workflow will next run after 'WorkflowNextRunAfter'. EdbFilePath: EdbFilePath WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`EdbFilePath`
`FailedElapsedTime`
`ConfiguredDelay`
`WorkflowNextRunAfter`

Event ID 1124: Automatic Reseed Manager is beginning attempt number AttemptNumber of execution stage 'ExecutionStage' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager is beginning attempt number AttemptNumber of execution stage 'ExecutionStage' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ExecutionStage`
`AttemptNumber`

Event ID 1125: Automatic Reseed Manager has successfully assigned spare volume 'VolumeName' mounted at 'ExchangeVolumeMountPoint' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has successfully assigned spare volume 'VolumeName' mounted at 'ExchangeVolumeMountPoint' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'. The workflow will next attempt to reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ExchangeVolumeMountPoint`
`VolumeName`

Event ID 1126: Automatic Reseed Manager failed to execute attempt number AttemptNumber of stage 'ExecutionStage' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to execute attempt number AttemptNumber of stage 'ExecutionStage' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'. ErrorMessage: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ExecutionStage`
`AttemptNumber`
`ErrorMessage`

Event ID 1127: Automatic Reseed Manager has successfully initiated reseed (with -SafeDeleteExistingFiles) for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has successfully initiated reseed (with -SafeDeleteExistingFiles) for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1128: Automatic Reseed Manager is resetting repair workflow 'WorkflowName' for database 'DatabaseName' so that the recovery actions can be attempted again.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager is resetting repair workflow 'WorkflowName' for database 'DatabaseName' so that the recovery actions can be attempted again. The last time the workflow ran was at 'WorkflowLastExecutionTime'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`WorkflowLastExecutionTime`

Event ID 1129: Automatic Reseed Manager has successfully configured the missing mount point for database copy 'DatabaseName' to point to existing volume 'VolumeName' mounted at 'ExchangeVolumeMountPoint...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager has successfully configured the missing mount point for database copy 'DatabaseName' to point to existing volume 'VolumeName' mounted at 'ExchangeVolumeMountPoint', as part of repair workflow 'WorkflowName'. The workflow will next attempt to reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ExchangeVolumeMountPoint`
`VolumeName`

Event ID 1130: Automatic Reseed Manager failed to do in-place reseed for database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because of a previous fatal error that...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to do in-place reseed for database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because of a previous fatal error that is preventing it. InPlaceReseedBlocked Error: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ErrorMessage`

Event ID 1131: The Disk Reclaimer is searching for quarantined disks that can potentially be formatted and reclaimed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer is searching for quarantined disks that can potentially be formatted and reclaimed.

Event ID 1132: The Disk Reclaimer failed to pass the database redundancy health check for one or more databases on this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer failed to pass the database redundancy health check for one or more databases on this server. Reason: Reason

Fields #

Name	Description
`Reason`

Event ID 1133: The Disk Reclaimer failed to reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer failed to reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare. [FormatSucceeded=FormatSucceeded] Error: ErrorMessage

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`FormatSucceeded`
`ErrorMessage`
`Exception`

Event ID 1134: The Disk Reclaimer succeeded to format and reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer succeeded to format and reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Fields #

Name	Description
`VolumeName`
`MountedFolder`

Event ID 1135: The Disk Reclaimer encountered an error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer encountered an error: ErrorMessage

Fields #

Name	Description
`ErrorMessage`

Event ID 1136: The Disk Reclaimer encountered an error when trying to determine if volume 'VolumeName' mounted at 'MountedFolder' can be reclaimed as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer encountered an error when trying to determine if volume 'VolumeName' mounted at 'MountedFolder' can be reclaimed as a spare. Error: ErrorMessage

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ErrorMessage`

Event ID 1137: The Disk Reclaimer started configuring volume mountpoints after Reinstall on this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer started configuring volume mountpoints after Reinstall on this server. Regkey 'Reason' is set.

Fields #

Name	Description
`Reason`

Event ID 1138: The Disk Reclaimer PostInstall configuration is attempting to resume all copies on server 'Server'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer PostInstall configuration is attempting to resume all copies on server 'Server'.

Fields #

Name	Description
`Server`

Event ID 1139: The Disk Reclaimer found one or more unknown databases while configuring mountpoints for volume 'VolumeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer found one or more unknown databases while configuring mountpoints for volume 'VolumeName'. Error: ErrorMessage.

Fields #

Name	Description
`VolumeName`
`ErrorMessage`

Event ID 1140: The Disk Reclaimer PostInstall configuration encountered an error while configuring mountpoints for volume 'VolumeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer PostInstall configuration encountered an error while configuring mountpoints for volume 'VolumeName'. Error: ErrorMessage

Fields #

Name	Description
`VolumeName`
`ErrorMessage`

Event ID 1141: The Disk Reclaimer finished configuring volume mountpoints after Reinstall on this server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer finished configuring volume mountpoints after Reinstall on this server. Attempting to disable regkey 'Reason'.

Fields #

Name	Description
`Reason`

Event ID 1142: The Disk Reclaimer is about to quarantine corrupted disk or volume 'VolumeName' mounted at 'MountedFolder' for format.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer is about to quarantine corrupted disk or volume 'VolumeName' mounted at 'MountedFolder' for format. Error: ErrorMessage.

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ErrorMessage`

Event ID 1143: The Disk Reclaimer skipped reclaiming volume 'VolumeName' mounted at 'MountedFolder'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer skipped reclaiming volume 'VolumeName' mounted at 'MountedFolder'. Error ErrorMessage.

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ErrorMessage`

Event ID 1144: The Disk Reclaimer found 'Count' never mounted active databases on the server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer found 'Count' never mounted active databases on the server. Databases: 'Databases'.

Fields #

Name	Description
`Count`
`Databases`

Event ID 1145: The Disk Reclaimer found never mounted active database: 'Database' missing volume mountpoint.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer found never mounted active database: 'Database' missing volume mountpoint. DiskReclaimer will attempt to assign a mountpoint and mount this database.

Fields #

Name	Description
`Database`

Event ID 1146: The Disk Reclaimer was unable to fixup mountpoint for active database: 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer was unable to fixup mountpoint for active database: 'DatabaseName'. Error ErrorMessage.

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 1147: The Disk Reclaimer was unable to mount active database: 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer was unable to mount active database: 'DatabaseName'. Error ErrorMessage.

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 1148: The Disk Reclaimer completed its attempt to fix volume mountpoints for active databases on server: Server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer completed its attempt to fix volume mountpoints for active databases on server: Server.

Fields #

Name	Description
`Server`

Event ID 1149: The Volume Manager found the following volumes: UnknownVolumeCount=UnknownVolumeCount UnEncryptedEmptySpareVolumeCount=UnEncryptedEmptySpareVolumeCount EncryptingEmptySpareVolumeCount=EncryptingEmp...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Volume Manager found the following volumes: UnknownVolumeCount=UnknownVolumeCount UnEncryptedEmptySpareVolumeCount=UnEncryptedEmptySpareVolumeCount EncryptingEmptySpareVolumeCount=EncryptingEmptySpareVolumeCount EncryptedEmptySpareVolumeCount=EncryptedEmptySpareVolumeCount QuarantinedVolumeCount=QuarantinedVolumeCount NotUsableAsSpareVolumeCount=NotUsableAsSpareVolumeCount ErrorVolumeCount=ErrorVolumeCount ReFSVolumeCount=ReFSVolumeCount ---UnEncryptedEmptySpareVolumeList--- EmptySpareVolumeList ---EncryptingEmptySpareVolumeList--- EncryptingEmptySpareVolumeList ---EncryptedEmptySpareVolumeList--- EncryptedEmptySpareVolumeList ---QuarantinedVolumeList--- QuarantinedVolumeList ---NotUsableAsSpareVolumeList--- NotUsableAsSpareVolumeList ---ErrorVolumeList--- ErrorVolumeList ---UnknownVolumeList--- UnknownVolumeList

Fields #

Name	Description
`UnknownVolumeCount`
`UnEncryptedEmptySpareVolumeCount`
`QuarantinedVolumeCount`
`NotUsableAsSpareVolumeCount`
`ErrorVolumeCount`
`EncryptingEmptySpareVolumeCount`
`EncryptedEmptySpareVolumeCount`
`EmptySpareVolumeList`
`QuarantinedVolumeList`
`NotUsableAsSpareVolumeList`
`ErrorVolumeList`
`UnknownVolumeList`
`EncryptingEmptySpareVolumeList`
`EncryptedEmptySpareVolumeList`
`ReFSVolumeCount`

Event ID 1150: Database active status tracker initialization failed with error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database active status tracker initialization failed with error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1151: The Disk Reclaimer PostInstall configuration found a misconfigured volume 'VolumeName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer PostInstall configuration found a misconfigured volume 'VolumeName'. This volume will be left in the Quarantined state without any database mountpoints and will be formatted by the Disk Reclaimer. Error: ErrorMessage

Fields #

Name	Description
`VolumeName`
`ErrorMessage`

Event ID 1152: The Disk Reclaimer will not attempt to reclaim any quarantined volumes because it found too many (Count) with unknown files.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer will not attempt to reclaim any quarantined volumes because it found too many (Count) with unknown files. Volumes: VolumesStr

Fields #

Name	Description
`Count`
`VolumesStr`

Event ID 1153: Automatic Reseed Manager is being skipped because: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager is being skipped because: Message

Fields #

Name	Description
`Message`

Event ID 1154: The Disk Reclaimer is being skipped because: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer is being skipped because: Message

Fields #

Name	Description
`Message`

Event ID 1155: The Disk Reclaimer encountered an Active Directory error: ErrorMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer encountered an Active Directory error: ErrorMessage

Fields #

Name	Description
`ErrorMessage`

Event ID 1156: Automatic Reseed Manager found that the mount point directory for database 'DatabaseName' was not empty, as part of an attempt to assign the mount point.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager found that the mount point directory for database 'DatabaseName' was not empty, as part of an attempt to assign the mount point. The mount point directory 'SourceDir' has been successfully renamed to 'DestDir'.

Fields #

Name	Description
`DatabaseName`
`SourceDir`
`DestDir`

Event ID 1157: The Disk Reclaimer found there are 'FormattedVolumeCount' volumes which have been formatted after the Disk Reclaimer last run, the formatted volume pathes are 'FormattedVolumePathList'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer found there are 'FormattedVolumeCount' volumes which have been formatted after the Disk Reclaimer last run, the formatted volume pathes are 'FormattedVolumePathList'.

Fields #

Name	Description
`FormattedVolumeCount`
`FormattedVolumePathList`

Event ID 1158: The Disk Reclaimer didn't found any formatted volumes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer didn't found any formatted volumes

Event ID 1160: Cluster API operation seems to be hung.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster API operation seems to be hung. Detecting the nodes that are causing the hang. (API: ApiName, StartTime: StartTime, Context: Context)

Fields #

Name	Description
`ApiName`
`StartTime`
`Context`

Event ID 1161: Hung node detection completed (GUM ID: GumId LockOwner: LockOwner Context: Context).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Hung node detection completed (GUM ID: GumId LockOwner: LockOwner Context: Context)

Fields #

Name	Description
`GumId`
`LockOwner`
`Context`

Event ID 1162: Hung node detection failed (Error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Hung node detection failed (Error: ErrorMessage)

Fields #

Name	Description
`ErrorMessage`
`Exception`

Event ID 1163: Attempt to open the cluster on server ServerName timed out while trying to find the hung nodes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to open the cluster on server ServerName timed out while trying to find the hung nodes. Cluster service kill be attempted on server ServerName.

Fields #

Name	Description
`ServerName`
`ErrorMessage`
`Context`

Event ID 1164: Attempt to kill cluster service was skipped since the registry override IsKillClusterServiceOnClusApiHang is set to false.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to kill cluster service was skipped since the registry override IsKillClusterServiceOnClusApiHang is set to false

Event ID 1165: Sending a request to kill ServiceName service on server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Sending a request to kill ServiceName service on server ServerName

Fields #

Name	Description
`ServiceName`
`ServerName`

Event ID 1166: ServiceName service successfully killed on server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ServiceName service successfully killed on server ServerName

Fields #

Name	Description
`ServiceName`
`ServerName`
`ReplyContext`

Event ID 1167: An attempt to kill ServiceName service on server ServerName failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An attempt to kill ServiceName service on server ServerName failed. Reason: Reason. Is request throttled? - 'IsThrottled', is exception unhandled? - 'IsUnhandledException', Context: ReplyContext

Fields #

Name	Description
`ServiceName`
`ServerName`
`IsThrottled`
`Reason`
`IsUnhandledException`
`ReplyContext`

Event ID 1168: Request received to kill ServiceName service from server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Request received to kill ServiceName service from server ServerName

Fields #

Name	Description
`ServiceName`
`ServerName`
`Context`

Event ID 1169: Killing process ProcessName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Killing process ProcessName. (Service: ServiceName, ProcessId: ProcessId)

Fields #

Name	Description
`ServiceName`
`ProcessName`
`ProcessId`
`Context`

Event ID 1170: Hung node action skipped since gum id change was observed in the detection.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Hung node action skipped since gum id change was observed in the detection. (LocalGumId=LocalGumId, RemoteGumId=RemoteGumId)

Fields #

Name	Description
`LocalGumId`
`RemoteGumId`
`LockOwnerName`
`HungNodesMask`

Event ID 1171: Incremental Reseed (DatabaseName\ServerName) failed to copy log generation Message2 from the source server after Message1 retries.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed (DatabaseName\ServerName) failed to copy log generation Message2 from the source server after Message1 retries. This means that the source has not yet generated the required log file. The operation will be retried again soon. [Active highest numbered log: Message3, Number of Logs Rolled: Message4]

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`
`Message2`
`Message3`
`Message4`

Event ID 1172: Bandwidth Monitor is now running.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Bandwidth Monitor is now running.

Event ID 1173: Bandwidth Monitor stopped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Bandwidth Monitor stopped.

Event ID 1174: Bandwidth Monitor raised exception: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Bandwidth Monitor raised exception: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1180: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual resume operation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual resume operation.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1181: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual reseed operation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual reseed operation.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1182: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic resume operation performed by ...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic resume operation performed by the Automatic Reseed workflow.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1183: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic reseed to a spare volume perfo...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic reseed to a spare volume performed by the Automatic Reseed workflow.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1184: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an in-place automatic reseed performed by t...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an in-place automatic reseed performed by the Automatic Reseed workflow.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1185: An in-place reseed has been requested for the local copy of database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

An in-place reseed has been requested for the local copy of database 'DatabaseGuid'.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 1186: The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'. It does not have the expected number of database mount points. Expected: ExpectedCount, Actual: ActualCount

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ExpectedCount`
`ActualCount`

Event ID 1187: The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'. It does not have the expected number of database directories. There may be older database files still present on this volume that were not cleaned up by the Disk Reclaimer. Expected: ExpectedCount, Actual: ActualCount

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ExpectedCount`
`ActualCount`

Event ID 1188: Automatic Reseed Manager found never mounted active database 'Database' missing volume mountpoint.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager found never mounted active database 'Database' missing volume mountpoint. It will attempt to assign a mountpoint and mount this database.

Fields #

Name	Description
`Database`

Event ID 1189: Automatic Reseed Manager allocated volume 'VolumeName' for never mounted active database 'Database'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager allocated volume 'VolumeName' for never mounted active database 'Database'.

Fields #

Name	Description
`Database`
`VolumeName`

Event ID 1190: Automatic Reseed Manager was unable to fixup mountpoint for active database: 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager was unable to fixup mountpoint for active database: 'DatabaseName'. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 1191: Automatic Reseed Manager was unable to mount active database: 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager was unable to mount active database: 'DatabaseName'. Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`ErrorMessage`

Event ID 1192: Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because its database mount point is missing.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because its database mount point is missing. The workflow will next attempt to assign a spare volume and reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1193: Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because the copy is being forced to reseed to a spare ...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager skipped resuming database copy 'DatabaseName' as part of repair workflow 'WorkflowName' because the copy is being forced to reseed to a spare volume. This usually happens because the volume is corrupt. The workflow will next attempt to assign a spare volume and reseed the database copy. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`

Event ID 1194: A reseed to spare volume has been requested for the local copy of database 'DatabaseGuid'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

A reseed to spare volume has been requested for the local copy of database 'DatabaseGuid'. All databases on the same volume will be failed over and marked as FailedAndSuspended.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 1195: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic reseed to a spare volume perfo...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to an automatic reseed to a spare volume performed by the Automatic Reseed workflow. The spare volume assignment was forced, which usually happens because the volume is corrupt.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1196: Automatic Reseed Manager determined that the secondary partition of database 'DatabaseName' recovered from an Offline state due to an in-place automatic rese...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that the secondary partition of database 'DatabaseName' recovered from an Offline state due to an in-place automatic reseed performed by the Automatic Reseed workflow.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1197: Automatic Reseed Manager determined that the secondary partition of database 'DatabaseName' recovered from an unhealthy (usually Offline) state due to a manu...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager determined that the secondary partition of database 'DatabaseName' recovered from an unhealthy (usually Offline) state due to a manual reseed operation.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`AttemptNumber`

Event ID 1198: Automatic Reseed Manager failed to reseed the secondary partition of database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attem...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Automatic Reseed Manager failed to reseed the secondary partition of database copy 'DatabaseName' as part of repair workflow 'WorkflowName' after a maximum of MaxRetries attempts. The workflow will next run after 'WorkflowNextRunAfter'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`MaxRetries`
`WorkflowNextRunAfter`

Event ID 1210: Attempt to initiate system failover for replay service down failed for server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to initiate system failover for replay service down failed for server ServerName. (Error: Error)

Fields #

Name	Description
`ServerName`
`Error`

Event ID 1211: System failover skipped for server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

System failover skipped for server ServerName. (Reason: Reason, Phase: Phase)

Fields #

Name	Description
`ServerName`
`Reason`
`Phase`

Event ID 1212: Throttling check did not allow system failover to proceed for server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Throttling check did not allow system failover to proceed for server ServerName. (TooSoonPerNode:IsActionCalledTooSoonPerNode, TooSoonAcrossDag:IsActionCalledTooSoonAcrossDag, MaxPerNodeExceeded:IsMaxActionsPerNodeExceeded, MaxAcrossDagExceeded:IsMaxActionsAcrossDagExceeded)

Fields #

Name	Description
`ServerName`
`IsActionCalledTooSoonPerNode`
`IsActionCalledTooSoonAcrossDag`
`IsMaxActionsPerNodeExceeded`
`IsMaxActionsAcrossDagExceeded`
`MostRecentActionDataForNode`
`MostRecentActionDataAcrossDag`
`ActionsCountPerNode`
`ActionsCountAcrossDag`
`MinDurationBetweenActionsPerNode`
`MaxCheckDurationPerNode`
`MaxAllowedActionsPerNode`
`MinDurationBetweenActionsAcrossDag`
`MaxCheckDurationAcrossDag`
`MaxAllowedActionsAcrossDag`

Event ID 1213: Throttling check allowed system failover to proceed for server ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Throttling check allowed system failover to proceed for server ServerName.

Fields #

Name	Description
`ServerName`
`MostRecentActionDataForNode`
`MostRecentActionDataAcrossDag`
`ActionsCountPerNode`
`ActionsCountAcrossDag`
`MinDurationBetweenActionsPerNode`
`MaxCheckDurationPerNode`
`MaxAllowedActionsPerNode`
`MinDurationBetweenActionsAcrossDag`
`MaxCheckDurationAcrossDag`
`MaxAllowedActionsAcrossDag`

Event ID 1214: Failed to initialize throttled action traker state from cluster database.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed to initialize throttled action traker state from cluster database. (Action: ActionName, MaxHistory=MaxHistorySize, Error: Error)

Fields #

Name	Description
`ActionName`
`MaxHistorySize`
`Error`

Event ID 1215: Failover on replay down feature is disabled with registry override.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failover on replay down feature is disabled with registry override

Event ID 1216: Failover on replay down tracker is not initialized.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failover on replay down tracker is not initialized

Event ID 1217: Starting action Action for cluster node NodeName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Starting action Action for cluster node NodeName

Fields #

Name	Description
`NodeName`
`Action`
`DurationJoiningCheck`
`DurationInProgressCheck`
`InProgressState`
`NodeState`

Event ID 1218: Completed action Action for cluster node NodeName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Completed action Action for cluster node NodeName

Fields #

Name	Description
`NodeName`
`Action`
`InProgressState`
`NodeState`
`Error`

Event ID 1219: Cluster node action Action is blocked for NodeName since there are operations still pending.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster node action Action is blocked for NodeName since there are operations still pending

Fields #

Name	Description
`NodeName`
`Action`
`InProgressState`

Event ID 1220: Cluster node action Action is blocked for NodeName since there are nodes that are in Joining state.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster node action Action is blocked for NodeName since there are nodes that are in Joining state

Fields #

Name	Description
`NodeName`
`Action`
`JoiningNodes`

Event ID 1230: Cached last log updater failed to update last log generation info.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cached last log updater failed to update last log generation info. (Count: EntriesCount)

Fields #

Name	Description
`EntriesCount`
`ErrorMessage`

Event ID 1231: An rpc request to PAM to update last log generation info failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An rpc request to PAM to update last log generation info failed. (Role: Role)

Fields #

Name	Description
`Role`
`LastUpdatedTimeBasedOnPAM`
`ErrorMessage`

Event ID 1232: Initiating cluster database updates from local nodes in stead of Primary Active Manager (LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Initiating cluster database updates from local nodes in stead of Primary Active Manager (LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb)

Fields #

Name	Description
`FirstLocalUpdateTime`
`LastServerUpdateTimeAsPerClusdb`
`LastServerUpdateTimeAsPerPam`
`BatcherWriterStartTime`
`RpcError`

Event ID 1233: Continuing cluster database updates locally (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Continuing cluster database updates locally (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb)

Fields #

Name	Description
`FirstLocalUpdateTime`
`LastServerUpdateTimeAsPerClusdb`
`LastServerUpdateTimeAsPerPam`
`BatcherWriterStartTime`
`RpcError`

Event ID 1234: Switching back to PAM based to cluster database updates (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Switching back to PAM based to cluster database updates (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb)

Fields #

Name	Description
`FirstLocalUpdateTime`
`LastServerUpdateTimeAsPerClusdb`
`LastServerUpdateTimeAsPerPam`
`BatcherWriterStartTime`
`RpcError`

Event ID 1235: Database 'DatabaseName' copy on server 'ServerName' is too far behind.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database 'DatabaseName' copy on server 'ServerName' is too far behind. Copy queue is: CopyQueue and replay queue is ReplayQueue.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`CopyQueue`
`ReplayQueue`

Event ID 1236: After TimeoutInSeconds seconds the SocketStream leaked resources to allow its termination processing to continue.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

After TimeoutInSeconds seconds the SocketStream leaked resources to allow its termination processing to continue.

Fields #

Name	Description
`TimeoutInSeconds`

Event ID 1237: SocketStream could not obtain buffer space.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SocketStream could not obtain buffer space. Memory fragmentation may result.

Event ID 1238: Database file 'EdbFilePath' for database 'DatabaseName' finished seeding.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Database file 'EdbFilePath' for database 'DatabaseName' finished seeding. Success=Success. Duration was ElapsedTime with average throughput of Throughput bytes/sec and compression factor of CompressionFactor.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ElapsedTime`
`Throughput`
`CompressionFactor`
`DecompressedBytes`
`CompressedBytes`
`SourceServer`
`CompressionConfig`
`Success`
`TotalThrottleDelayTime`
`ThrottleStatus`
`EdbFilePath`
`LocalEndPoint`
`SendingEndPoint`

Event ID 1239: Negotiation of compression with server 'RemoteNodeName' failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Negotiation of compression with server 'RemoteNodeName' failed. Further negotiation will not be attempted until service restart.

Fields #

Name	Description
`RemoteNodeName`
`RequestedConfiguration`
`Exception`

Event ID 1240: Remote server 'RemoteNodeName' passed an unrecognized compression configuration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Remote server 'RemoteNodeName' passed an unrecognized compression configuration. Compression will not be attempted. Configuration needs to be corrected by an administrator.

Fields #

Name	Description
`RemoteNodeName`
`RequestedConfiguration`
`Exception`

Event ID 1241: PAM Monitor is attempting to perform the recovery.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM Monitor is attempting to perform the recovery. Server roles view: ServerView

Fields #

Name	Description
`ServerView`

Event ID 1242: PAM move cancelled since majority are not running as SAM (Total: TotalServersInDag, SAM: TotalServersInSamRole, MinimumRequired: MinimumRequired).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

PAM move cancelled since majority are not running as SAM (Total: TotalServersInDag, SAM: TotalServersInSamRole, MinimumRequired: MinimumRequired)

Fields #

Name	Description
`TotalServersInDag`
`TotalServersInSamRole`
`MinimumRequired`

Event ID 1243: Database operation 'RequestedOperationClass' is not enqueued since database queue is already busy running an action 'InProgressOperationClass' (remaining actions in queue: QueueLength).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database operation 'RequestedOperationClass' is not enqueued since database queue is already busy running an action 'InProgressOperationClass' (remaining actions in queue: QueueLength)

Fields #

Name	Description
`DatabaseGuid`
`QueueLength`
`RequestedOperationClass`
`RequestedOperationUniqueId`
`RequestedOperationDetails`
`InProgressOperationClass`
`InProgressOperationUniqueId`
`InProgressOperationDetails`
`NextOperationClass`
`NextOperationUniqueId`
`NextOperationDetails`

Event ID 1244: MonitoredDatabase for database 'DatabaseName' failed to start: ExceptionMessage HRESULT=HRESULT.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

MonitoredDatabase for database 'DatabaseName' failed to start: ExceptionMessage HRESULT=HRESULT.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ExceptionMessage`
`HRESULT`
`FullException`
`DatabasePath`

Event ID 1245: Attempt to query bitlocked failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to query bitlocked failed: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1246: Seeding starts for local copy of database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding starts for local copy of database 'DatabaseName'. Global truncation reports InitialGlobalMin initially yielding FinalGlobalMin.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`InitialGlobalMin`
`FinalGlobalMin`

Event ID 1247: Seeding for local copy of database 'DatabaseName' failed to establish divergence check file 'DivergenceCheckFile' : Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding for local copy of database 'DatabaseName' failed to establish divergence check file 'DivergenceCheckFile' : Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`DivergenceCheckFile`
`Error`

Event ID 1248: Incremental seeding for local copy of database 'DatabaseName' failed to send the page list of size NumPages : Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental seeding for local copy of database 'DatabaseName' failed to send the page list of size NumPages : Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`NumPages`
`Error`

Event ID 1249: Seeding for local copy of database 'DatabaseName' was cancelled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Seeding for local copy of database 'DatabaseName' was cancelled. AdminRequested=AdminRequested.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`AdminRequested`

Event ID 1250: Cluster batch writer failed while attempting operation 'Operation' (error: ErrorMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster batch writer failed while attempting operation 'Operation' (error: ErrorMessage).

Fields #

Name	Description
`Operation`
`ErrorMessage`

Event ID 1251: The MonitoredDatabase for database 'DatabaseName' was requested to stop at StartOfCleanupUtc which took StopDuration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The MonitoredDatabase for database 'DatabaseName' was requested to stop at StartOfCleanupUtc which took StopDuration. EOL at EndOfLogGeneration EndOfLogUtc

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StopDuration`
`StartOfCleanupUtc`
`EndOfLogGeneration`
`EndOfLogUtc`

Event ID 1252: The Disk Reclaimer has removed the mountpoint 'MountPoint'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer has removed the mountpoint 'MountPoint'.

Fields #

Name	Description
`MountPoint`

Event ID 1253: The Disk Reclaimer has added the mountpoint 'MountPoint' => 'Volume'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer has added the mountpoint 'MountPoint' => 'Volume'.

Fields #

Name	Description
`MountPoint`
`Volume`

Event ID 1254: The Disk Reclaimer has created the folder for database 'Database' at 'Folder'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer has created the folder for database 'Database' at 'Folder'.

Fields #

Name	Description
`Database`
`Folder`

Event ID 1255: Automatic Reseed Manager failed to execute attempt number AttemptNumber of stage 'ExecutionStage' for database copy 'DatabaseName' as part of repair workflow 'WorkflowName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`WorkflowName`
`WorkflowLaunchReason`
`ExecutionStage`
`AttemptNumber`
`ErrorMessage`

Event ID 1256: The Disk Reclaimer encountered an error when trying to determine which database files exist on volume 'VolumeName' mounted at 'MountedFolder'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The Disk Reclaimer encountered an error when trying to determine which database files exist on volume 'VolumeName' mounted at 'MountedFolder'. Error: ErrorMessage.

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`ErrorMessage`

Event ID 1270: The secondary partition status for the local copy of database 'DatabaseName' could not be overridden: Error: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The secondary partition status for the local copy of database 'DatabaseName' could not be overridden: Error: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 1300: Start gathering hung node information via RPC calls (List of servers: ListOfServers).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Start gathering hung node information via RPC calls (List of servers: ListOfServers)

Fields #

Name	Description
`ListOfServers`

Event ID 1301: Start gathering cluster node status (ClusterOpen node: ClusterOpenTarget).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Start gathering cluster node status (ClusterOpen node: ClusterOpenTarget)

Fields #

Name	Description
`ClusterOpenTarget`

Event ID 1302: Hung Node information gathering completed (HungNodeInfo: HungNodeInfo).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Hung Node information gathering completed (HungNodeInfo: HungNodeInfo)

Fields #

Name	Description
`HungNodeInfo`

Event ID 1303: Hung Node information analysis completed (HungNodeAction: HungNodeAction).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Hung Node information analysis completed (HungNodeAction: HungNodeAction)

Fields #

Name	Description
`HungNodeAction`

Event ID 1310: Start recovery action for cluster node hung (Target servers: TargetServers).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Start recovery action for cluster node hung (Target servers: TargetServers)

Fields #

Name	Description
`TargetServers`

Event ID 1311: Requesting remote reboot (target servers: RebootServers) and restart of clussvc service (target servers: RestartServers) of hung nodes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Requesting remote reboot (target servers: RebootServers) and restart of clussvc service (target servers: RestartServers) of hung nodes

Fields #

Name	Description
`RebootServers`
`RestartServers`

Event ID 1320: Attempt to remote reboot of target node succeeded (Target: Targets, DebugMessage: ActionMessage).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to remote reboot of target node succeeded (Target: Targets, DebugMessage: ActionMessage)

Fields #

Name	Description
`Targets`
`ActionMessage`

Event ID 1321: Attempt to remote reboot of target node failed or throttled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to remote reboot of target node failed or throttled. (Target: Targets, DebugMessage: ActionMessage)

Fields #

Name	Description
`Targets`
`ActionMessage`

Event ID 1322: Attempt to evict target node succeeded (Target: Targets).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to evict target node succeeded (Target: Targets)

Fields #

Name	Description
`Targets`

Event ID 1323: Total up node check failed for evict target node action.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Total up node check failed for evict target node action. (Target: Targets, Threshold: Threshold, UpNodes: UpNodes, TotalNodes: TotalNodes, Default number of nodes in a DAG: DefaultNumberOfNodesInDAG)

Fields #

Name	Description
`Targets`
`Threshold`
`UpNodes`
`TotalNodes`
`DefaultNumberOfNodesInDAG`

Event ID 1324: Total up node check succeeded for evict target node action.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Total up node check succeeded for evict target node action. (Target: Targets, Threshold: Threshold, UpNodes: UpNodes, TotalNodes: TotalNodes, Default number of nodes in a DAG: DefaultNumberOfNodesInDAG)

Fields #

Name	Description
`Targets`
`Threshold`
`UpNodes`
`TotalNodes`
`DefaultNumberOfNodesInDAG`

Event ID 1325: Attempt to evict target node failed or throttled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempt to evict target node failed or throttled. (Target: Targets, DebugMessage: DebugMessage)

Fields #

Name	Description
`Targets`
`DebugMessage`

Event ID 1326: Recovering ClusDB hang by attempting to restart ClusSvc on the following (individually identified as potential culprits) servers: Targets.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovering ClusDB hang by attempting to restart ClusSvc on the following (individually identified as potential culprits) servers: Targets

Fields #

Name	Description
`Targets`

Event ID 1327: Recovering ClusDB hang by attempting to restart clussvc on all nodes (Up, Joining and Paused) in the DAG: Targets.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovering ClusDB hang by attempting to restart clussvc on all nodes (Up, Joining and Paused) in the DAG: Targets

Fields #

Name	Description
`Targets`

Event ID 1328: Restarting an individual node was throttled (ClusDB hang recovery).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Restarting an individual node was throttled (ClusDB hang recovery). Server: Target

Fields #

Name	Description
`Target`

Event ID 1329: Restarting clussvc on a node as part of restarting all nodes in the DAG was throttled (ClusDB hang recovery).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Restarting clussvc on a node as part of restarting all nodes in the DAG was throttled (ClusDB hang recovery). Server: Target

Fields #

Name	Description
`Target`

Event ID 1330: Cluster database periodic cleanup failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup failed. (Category: Category, Error: Error)

Fields #

Name	Description
`Category`
`Error`

Event ID 1331: Cluster database periodic cleanup skipped.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup skipped. (Category: Category, Reason: Reason)

Fields #

Name	Description
`Category`
`Reason`

Event ID 1332: Cluster database periodic cleanup batch operation failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup batch operation failed. (Category: Category, Error: Error)

Fields #

Name	Description
`Category`
`Error`
`KeyName`
`IsDeleteKey`
`BatchNumber`
`ItemsInBatch`
`TotalItemsToDelete`
`FilteredItemsToDelete`

Event ID 1333: Cluster database periodic cleanup did not detect any stale databases or servers.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup did not detect any stale databases or servers.

Event ID 1334: Cluster database periodic cleanup for key ParentKeyName completed (TotalItemsDeleted: TotalItemsDeleted, ItemType: ItemType, DurationMs: DurationMilliseconds).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup for key ParentKeyName completed (TotalItemsDeleted: TotalItemsDeleted, ItemType: ItemType, DurationMs: DurationMilliseconds).

Fields #

Name	Description
`Category`
`ParentKeyName`
`TotalItemsDeleted`
`ItemType`
`TotalBatchRequests`
`TotalFailedBatchRequests`
`DurationMilliseconds`

Event ID 1335: Cluster database periodic cleanup detected DatabaseCountWaitingForConfirmation stale database entries and ServerCountWaitingForConfirmation stale server entries.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup detected DatabaseCountWaitingForConfirmation stale database entries and ServerCountWaitingForConfirmation stale server entries.

Fields #

Name	Description
`DatabaseCountWaitingForConfirmation`
`ServerCountWaitingForConfirmation`

Event ID 1336: Cluster database periodic cleanup analyze failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Cluster database periodic cleanup analyze failed. (Category: Category, Error: Error)

Fields #

Name	Description
`Category`
`Error`

Event ID 1340: Recovering ClusDB hang by attempting to restart clussvc on all nodes is blocked: GumIdState.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovering ClusDB hang by attempting to restart clussvc on all nodes is blocked: GumIdState

Fields #

Name	Description
`GumIdState`

Event ID 1381: Prereqs for offline defragmentation process of database Database completed successfully.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Prereqs for offline defragmentation process of database Database completed successfully. It took Duration minutes to complete.

Fields #

Name	Description
`Database`
`Duration`

Event ID 1382: Prereqs for offline defragmentation process of database Database failed (it took Duration minutes to fail).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Prereqs for offline defragmentation process of database Database failed (it took Duration minutes to fail). Prereqs that failed: 'PrereqsFailed'. Error: ErrorMessage

Fields #

Name	Description
`Database`
`Duration`
`PrereqsFailed`
`ErrorMessage`

Event ID 1383: Dismount of database Database and suspending its copies (for offline defragmentation) completed successfully.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dismount of database Database and suspending its copies (for offline defragmentation) completed successfully. It took Duration minutes to complete.

Fields #

Name	Description
`Database`
`Duration`

Event ID 1384: Dismount of database Database or suspending its copies (for offline defragmentation) failed (it took Duration minutes to fail).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dismount of database Database or suspending its copies (for offline defragmentation) failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

Name	Description
`Database`
`Duration`
`ErrorMessage`

Event ID 1385: EDB file defragmentation stage and integrity check of database Database completed successfully.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

EDB file defragmentation stage and integrity check of database Database completed successfully. It took Duration minutes to complete.

Fields #

Name	Description
`Database`
`Duration`

Event ID 1386: EDB file defragmentation stage and integrity check of database Database failed (it took Duration minutes to fail).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

EDB file defragmentation stage and integrity check of database Database failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

Name	Description
`Database`
`Duration`
`ErrorMessage`

Event ID 1387: Final stage (mount database and reseeding copies) of offline defragmentation of database Database completed successfully.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Final stage (mount database and reseeding copies) of offline defragmentation of database Database completed successfully. It took Duration minutes to complete.

Fields #

Name	Description
`Database`
`Duration`

Event ID 1388: Final stage (mount database and reseeding copies) of offline defragmentation of database Database failed (it took Duration minutes to fail).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Final stage (mount database and reseeding copies) of offline defragmentation of database Database failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

Name	Description
`Database`
`Duration`
`ErrorMessage`

Event ID 1389: Recovering from incosistent state (left behind by one of the stages of offline defragmentation) for database Database completed successfully.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovering from incosistent state (left behind by one of the stages of offline defragmentation) for database Database completed successfully. It took Duration minutes to complete.

Fields #

Name	Description
`Database`
`Duration`

Event ID 1390: Recovering from incosistent state (left behind by one of the stages of offline defragmentation) for database Database failed (it took Duration minutes to fail).

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Recovering from incosistent state (left behind by one of the stages of offline defragmentation) for database Database failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

Name	Description
`Database`
`Duration`
`ErrorMessage`

Event ID 1400: AD configuration is not available : Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

AD configuration is not available : Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1401: AD configuration refresh took excessive time : TotalDuration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

AD configuration refresh took excessive time : TotalDuration.

Fields #

Name	Description
`TotalDuration`

Event ID 1402: AD configuration refresh failed : Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

AD configuration refresh failed : Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1403: Process ProcessName is using MeasuredConsumption MB of memory.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Process ProcessName is using MeasuredConsumption MB of memory. Warning threshold is WarningLimit. Error limit is ErrorLimit. Memory type is ResourceClass.

Fields #

Name	Description
`ProcessName`
`MeasuredConsumption`
`WarningLimit`
`ErrorLimit`
`ResourceClass`

Event ID 1404: Process ProcessName is using MeasuredConsumption handles.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Process ProcessName is using MeasuredConsumption handles. Warning threshold is WarningLimit. Error limit is ErrorLimit. Handle type is ResourceClass.

Fields #

Name	Description
`ProcessName`
`MeasuredConsumption`
`WarningLimit`
`ErrorLimit`
`ResourceClass`

Event ID 1405: Process ProcessName is using MeasuredConsumption threads.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Process ProcessName is using MeasuredConsumption threads. Warning threshold is WarningLimit. Error limit is ErrorLimit.

Fields #

Name	Description
`ProcessName`
`MeasuredConsumption`
`WarningLimit`
`ErrorLimit`
`ResourceClass`

Event ID 1406: SetServerComponentState was run: Server=Server Requester=Requester Component=Component State=State CmdType=CmdType.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SetServerComponentState was run: Server=Server Requester=Requester Component=Component State=State CmdType=CmdType

Fields #

Name	Description
`Server`
`Requester`
`Component`
`State`
`CmdType`

Event ID 1500: Database Health Tracker component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1501: Database Health Tracker is now running as the Primary role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker is now running as the Primary role. It will maintain and push out updates of the health information to the rest of the DAG member servers.

Event ID 1502: Database Health Tracker is currently running as the 'Role' role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker is currently running as the 'Role' role.

Fields #

Name	Description
`Role`

Event ID 1503: Database Health Tracker, running as the Primary role, failed to persist the health information.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker, running as the Primary role, failed to persist the health information. Error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1504: Database Health Tracker, running as a Secondary role, failed to persist the health information.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker, running as a Secondary role, failed to persist the health information. Error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1505: Database Health Tracker failed to initialize the health information from the persisted file.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker failed to initialize the health information from the persisted file. Error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1506: Remote operation 'OperationName' timed out to one or more servers after 'Timeout'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Remote operation 'OperationName' timed out to one or more servers after 'Timeout'.

Fields #

Name	Description
`OperationName`
`Timeout`

Event ID 1507: Remote operation 'OperationName' failed to one or more servers.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Remote operation 'OperationName' failed to one or more servers. Error: Message

Fields #

Name	Description
`OperationName`
`Message`
`StackTrace`

Event ID 1508: During startup, the Primary candidate role failed to get back any successful responses for operation 'OperationName' to other DAG member servers.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

During startup, the Primary candidate role failed to get back any successful responses for operation 'OperationName' to other DAG member servers. The node will *NOT* take over as the Primary role.

Fields #

Name	Description
`OperationName`

Event ID 1509: During startup, the Primary candidate role determined that a new health information table needs to be created and pushed out to the rest of the DAG...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

During startup, the Primary candidate role determined that a new health information table needs to be created and pushed out to the rest of the DAG member servers.

Event ID 1510: During startup, the Primary candidate role is ignoring the older health information table of update time 'OtherUpdateTimeUtc' retrieved from another DAG member ser...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

During startup, the Primary candidate role is ignoring the older health information table of update time 'OtherUpdateTimeUtc' retrieved from another DAG member server. The local update time is 'LocalUpdateTimeUtc'.

Fields #

Name	Description
`OtherUpdateTimeUtc`
`LocalUpdateTimeUtc`

Event ID 1511: Secondary role received an older health information table of update time 'OtherUpdateTimeUtc' from the Primary server.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Secondary role received an older health information table of update time 'OtherUpdateTimeUtc' from the Primary server. The local update time is 'LocalUpdateTimeUtc'. The local health information will be overwritten.

Fields #

Name	Description
`OtherUpdateTimeUtc`
`LocalUpdateTimeUtc`

Event ID 1512: The Monitoring WCF service failed to register its endpoint.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

The Monitoring WCF service failed to register its endpoint. Error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 1513: During startup, the Primary candidate role is updating its health information table of update time 'LocalUpdateTimeUtc' with one retrieved from server 'OtherServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

During startup, the Primary candidate role is updating its health information table of update time 'LocalUpdateTimeUtc' with one retrieved from server 'OtherServer'. The remote server's update time is 'OtherUpdateTimeUtc', and its create time is 'OtherCreateTimeUtc'.

Fields #

Name	Description
`OtherServer`
`OtherUpdateTimeUtc`
`OtherCreateTimeUtc`
`LocalUpdateTimeUtc`

Event ID 1514: Database Health Tracker could not initialize the health information from the persisted file 'Message', because the file was not found.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker could not initialize the health information from the persisted file 'Message', because the file was not found.

Fields #

Name	Description
`Message`

Event ID 1515: Database Health Tracker is initializing the health information from the persisted file modified at 'LastUpdateTimeUtc UTC' even though it is too old.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database Health Tracker is initializing the health information from the persisted file modified at 'LastUpdateTimeUtc UTC' even though it is too old. [Age of file: LastUpdateTimeDiff, Age Threshold: UpdateThreshold].

Fields #

Name	Description
`LastUpdateTimeUtc`
`LastUpdateTimeDiff`
`UpdateThreshold`

Event ID 1516: During startup, the Primary candidate role will initialize the health information from another DAG member server even though it is too old.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

During startup, the Primary candidate role will initialize the health information from another DAG member server even though it is too old. The modified time is: 'LastUpdateTimeUtc UTC'. [Age of file: LastUpdateTimeDiff, Age Threshold: UpdateThreshold].

Fields #

Name	Description
`LastUpdateTimeUtc`
`LastUpdateTimeDiff`
`UpdateThreshold`

Event ID 1517: Failover sequence number for database guid DatabaseGuid is not based on time due to time skew.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failover sequence number for database guid DatabaseGuid is not based on time due to time skew. It is now FailoverSequenceNumber.

Fields #

Name	Description
`DatabaseGuid`
`FailoverSequenceNumber`

Event ID 1518: The Monitoring WCF service started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

The Monitoring WCF service started. Endpoint(s): Endpoints

Fields #

Name	Description
`Endpoints`

Event ID 1600: Database potential redundancy health check passed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database potential redundancy health check passed. Database: DatabaseName Redundancy count: HealthyCopiesCount Passive redundancy count: HealthyPassiveCopiesCount Total passive copies found: TotalPassiveCopiesCount Total passive copies required: TotalPassiveCopiesRequired IsSuppressed: IsSuppressed Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`HealthyPassiveCopiesCount`
`TotalPassiveCopiesCount`
`TotalPassiveCopiesRequired`
`ErrorMessage`
`DatabaseGuid`
`IsSuppressed`

Event ID 1601: Database potential redundancy health check failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database potential redundancy health check failed. Database: DatabaseName Redundancy count: HealthyCopiesCount Passive redundancy count: HealthyPassiveCopiesCount Total passive copies found: TotalPassiveCopiesCount Total passive copies required: TotalPassiveCopiesRequired Error: ErrorMessage

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`HealthyPassiveCopiesCount`
`TotalPassiveCopiesCount`
`TotalPassiveCopiesRequired`
`ErrorMessage`
`DatabaseGuid`

Event ID 1602: Databases on server Message have passed the check for potential database redundancy issue.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Databases on server Message have passed the check for potential database redundancy issue.

Fields #

Name	Description
`Message`

Event ID 1603: Some databases on server LocalMachineName will potentially have insufficient data redundancy, which has been caused by server RemoteMachineName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Some databases on server LocalMachineName will potentially have insufficient data redundancy, which has been caused by server RemoteMachineName. Databases: ErrorMessage

Fields #

Name	Description
`LocalMachineName`
`RemoteMachineName`
`ErrorMessage`

Event ID 1604: Database potential redundancy health check failed, but not enough total passive copies have been found to be certain about the issue.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Database potential redundancy health check failed, but not enough total passive copies have been found to be certain about the issue. Database: DatabaseName Redundancy count: HealthyCopiesCount Passive redundancy count: HealthyPassiveCopiesCount Total passive copies found: TotalPassiveCopiesCount Total passive copies required: TotalPassiveCopiesRequired Error: ErrorMessage DatabaseGuid: DatabaseGuid

Fields #

Name	Description
`DatabaseName`
`HealthyCopiesCount`
`HealthyPassiveCopiesCount`
`TotalPassiveCopiesCount`
`TotalPassiveCopiesRequired`
`ErrorMessage`
`DatabaseGuid`

Event ID 1605: Server level database potential redundancy issue has been detected for two or more servers (Message1), will notify Active Monitoring to do recovery actio...

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Server level database potential redundancy issue has been detected for two or more servers (Message1), will notify Active Monitoring to do recovery actions on the first server 'Message2'

Fields #

Name	Description
`Message1`
`Message2`

Event ID 1606: FailedCopies Database Copies out of NumberOfCopies have a growing Log Copy queue on ServerName.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

FailedCopies Database Copies out of NumberOfCopies have a growing Log Copy queue on ServerName

Fields #

Name	Description
`FailedCopies`
`NumberOfCopies`
`ServerName`

Event ID 2000: AvailabilitySensorError component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

AvailabilitySensorError component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 2001: Database scanning during passive replay is disabled on 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database scanning during passive replay is disabled on 'DatabaseName'. Explanation: Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 2002: Database scanning during passive replay is enabled on 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database scanning during passive replay is enabled on 'DatabaseName'. Explanation: Message1.

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 2003: The log copier for database 'DatabaseName' found divergence at generation DivergedGeneration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The log copier for database 'DatabaseName' found divergence at generation DivergedGeneration. The active server was ActiveServer.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`DivergedGeneration`
`ActiveServer`

Event ID 2004: The log copier for database 'DatabaseName' could not verify divergence at generation DivergedGeneration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The log copier for database 'DatabaseName' could not verify divergence at generation DivergedGeneration. The active server was ActiveServer. The exception was: Exception

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`DivergedGeneration`
`ActiveServer`
`Exception`

Event ID 2005: The log copier for database 'DatabaseName' is terminating because server ActiveServer is not in the expected active role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The log copier for database 'DatabaseName' is terminating because server ActiveServer is not in the expected active role.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`

Event ID 2006: The ESE LogConsumer for database 'DatabaseName' failed during termination: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

The ESE LogConsumer for database 'DatabaseName' failed during termination: Message1

Fields #

Name	Description
`DatabaseName`
`ServerName`
`DatabaseGuid`
`Message1`

Event ID 2007: BlockMode terminated for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

BlockMode terminated for database 'DatabaseName'. CurrentGen=CurrentGen HeldGen=HeldGen

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`CurrentGen`
`HeldGen`

Event ID 2008: ACLL completed with minor loss due to LazyCommit while performing switchover on shutdown for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL completed with minor loss due to LazyCommit while performing switchover on shutdown for database 'DatabaseName'

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 2009: Prior to mounting database 'DatabaseName' possible loss due LazyCommit was recorded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Prior to mounting database 'DatabaseName' possible loss due LazyCommit was recorded. Loss window: Start=LossStart End=LossEnd

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LossStart`
`LossEnd`
`ResultingStart`
`ResultingEnd`

Event ID 2010: Prior to mounting database 'DatabaseName' possible loss due LazyCommit could not be determined.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Prior to mounting database 'DatabaseName' possible loss due LazyCommit could not be determined. Error=Message

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Message`

Event ID 2011: After mounting database 'DatabaseName' redelivery was performed for possible loss due LazyCommit.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

After mounting database 'DatabaseName' redelivery was performed for possible loss due LazyCommit. Loss window: Start=LossStart End=LossEnd

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LossStart`
`LossEnd`
`LossString`

Event ID 2012: After mounting database 'DatabaseName' possible loss due LazyCommit could not be processed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

After mounting database 'DatabaseName' possible loss due LazyCommit could not be processed. Error=Message

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Message`

Event ID 2013: ACLL failed for database 'DatabaseName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL failed for database 'DatabaseName'. PAM active server = ExpectedActiveServer but local copy has active = ActiveServerBeingUsed.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ExpectedActiveServer`
`ActiveServerBeingUsed`

Event ID 2014: Database 'DatabaseName' cannot be moved because the active copy on server 'ActiveServer' is currently being used to seed another copy.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database 'DatabaseName' cannot be moved because the active copy on server 'ActiveServer' is currently being used to seed another copy.

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`ActiveServer`

Event ID 2015: Sent CAFE notification to endpoint Endpoint (json: 'JsonPayload').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Sent CAFE notification to endpoint Endpoint (json: 'JsonPayload'). FEServer: FEServer. Result: Result.

Fields #

Name	Description
`Endpoint`
`JsonPayload`
`FEServer`
`Result`

Event ID 2016: Failed CAFE notification to endpoint Endpoint (json: 'JsonPayload').

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Failed CAFE notification to endpoint Endpoint (json: 'JsonPayload'). FEServer: FEServer. Result: Result. FailureMessage: FailureMessage.

Fields #

Name	Description
`Endpoint`
`JsonPayload`
`FEServer`
`Result`
`FailureMessage`

Event ID 2017: InvokeWithTimeout perf: MaxDelay MaxDelayInUsec uSec.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

InvokeWithTimeout perf: MaxDelay MaxDelayInUsec uSec. MaxConcurrentWorkers = MaxConcurrentWorkers. CountInWorstBucket = CountInWorstBucket. WorstBucket = DelayForWorstBucket uSec. Measured over MeasurementWindow.

Fields #

Name	Description
`MaxDelayInUsec`
`MaxConcurrentWorkers`
`MeasurementWindow`
`CountInWorstBucket`
`DelayForWorstBucket`
`OtherBuckets`

Event ID 2018: ThreadPool: CurrentWorkers CurrentWorkerThreads.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ThreadPool: CurrentWorkers CurrentWorkerThreads. MinWorkers MinWorkerThreads. MaxWorkers MaxWorkerThreads. CurrentIOThreads CurrentIOThreads. MinIO MinIOThreads. MaxIO MaxIOThreads.

Fields #

Name	Description
`CurrentWorkerThreads`
`MinWorkerThreads`
`MaxWorkerThreads`
`CurrentIOThreads`
`MinIOThreads`
`MaxIOThreads`
`ProcessThreadCount`

Event ID 2019: SafetyNet request 'StoreValueName' for database 'DatabaseName' failed to deserialize: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SafetyNet request 'StoreValueName' for database 'DatabaseName' failed to deserialize: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StoreValueName`
`Error`

Event ID 2020: SafetyNet request 'StoreValueName' for database 'DatabaseName' has expired.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SafetyNet request 'StoreValueName' for database 'DatabaseName' has expired.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`StoreValueName`

Event ID 2021: SafetyNet for database 'DatabaseName' failed due to a serialization error: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SafetyNet for database 'DatabaseName' failed due to a serialization error: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 2022: The local copy of database 'DatabaseName' was marked Disconnected but BlockMode is active.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The local copy of database 'DatabaseName' was marked Disconnected but BlockMode is active. Resetting to Healthy.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 2023: The local copy of database 'DatabaseName' has entered BlockMode Replication.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

The local copy of database 'DatabaseName' has entered BlockMode Replication.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`

Event ID 2024: Passive BlockMode for database 'DatabaseName' failed to receive a response from ActiveServer after TimeoutInterval.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to receive a response from ActiveServer after TimeoutInterval.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`TimeoutInterval`

Event ID 2025: Passive BlockMode for database 'DatabaseName' failed to ping active ActiveServer : Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to ping active ActiveServer : Error.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Error`

Event ID 2026: Passive BlockMode for database 'DatabaseName' failed to initialize.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to initialize. Active was ActiveServer. Error: Error.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Error`

Event ID 2027: Passive BlockMode for database 'DatabaseName' failed to read data.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to read data. Active was ActiveServer. Error: Error.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Error`

Event ID 2028: Passive BlockMode for database 'DatabaseName' failed due to a local consumer problem.

Provider: Microsoft-Exchange-HighAvailability
Channel: BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed due to a local consumer problem. Active was ActiveServer. Error: Error.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Error`

Event ID 2029: FileIOErrorOnSource for database 'DatabaseName': Corrupt: TreatedAsCorrupt.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FileIOErrorOnSource for database 'DatabaseName': Corrupt: TreatedAsCorrupt. Err: Exception

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`TreatedAsCorrupt`
`Exception`
`PartnerNodeName`

Event ID 2030: The copy of 'DatabaseName' has a loss window from LossStart to LossEnd.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of 'DatabaseName' has a loss window from LossStart to LossEnd. No redelivery request was found.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LossStart`
`LossEnd`
`SafetyNetRanges`

Event ID 2031: The copy of 'DatabaseName' has a loss window from LossStart to LossEnd that is covered by redelivery.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of 'DatabaseName' has a loss window from LossStart to LossEnd that is covered by redelivery.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LossStart`
`LossEnd`
`RedeliveryKey`
`RedeliveryRecord`

Event ID 2032: LossVerification during IncrementalReseed failed: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

LossVerification during IncrementalReseed failed: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 2033: SetBlockFlags failed during failure item processing for database 'DatabaseName' : Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

SetBlockFlags failed during failure item processing for database 'DatabaseName' : Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 2034: Incremental Reseed failed for database 'DatabaseName' because DivergenceInLogs logs of divergence exist but the limit is MaxDivergenceAllowed logs.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed failed for database 'DatabaseName' because DivergenceInLogs logs of divergence exist but the limit is MaxDivergenceAllowed logs.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`DivergenceInLogs`
`MaxDivergenceAllowed`

Event ID 2035: Incremental Reseed failed for database 'DatabaseName' because LogsToCopy logs must be copied to cover page-patch but the limit is MaxLogsAllowed logs.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Incremental Reseed failed for database 'DatabaseName' because LogsToCopy logs must be copied to cover page-patch but the limit is MaxLogsAllowed logs.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LogsToCopy`
`MaxLogsAllowed`

Event ID 2036: MonitoredDatabase for database 'DatabaseName' is starting.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

MonitoredDatabase for database 'DatabaseName' is starting. IsActive=IsActive.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`IsActive`

Event ID 2037: MonitoredDatabase for database 'DatabaseName' has started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

MonitoredDatabase for database 'DatabaseName' has started. IsActive=IsActive. Duration=Duration. EOL=EndOfLogGeneration EndOfLogUtc

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`IsActive`
`Duration`
`EndOfLogGeneration`
`EndOfLogUtc`

Event ID 2038: The active copy for database 'DatabaseGuid' could not be determined: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The active copy for database 'DatabaseGuid' could not be determined: Error

Fields #

Name	Description
`DatabaseGuid`
`Error`
`Stack`

Event ID 2039: The configuration for the local copy of database 'DatabaseName' could not be determined: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The configuration for the local copy of database 'DatabaseName' could not be determined: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 2040: The active copy for database 'DatabaseName' is ActiveCopy.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The active copy for database 'DatabaseName' is ActiveCopy. It was determined by Authority at DeterminationUTC UTC

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveCopy`
`Authority`
`DeterminationUTC`

Event ID 2041: A network error happened at LocationTag: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

A network error happened at LocationTag: Error

Fields #

Name	Description
`Error`
`LocationTag`
`ObjectName`
`ConnectionWasInScavenge`

Event ID 2042: A network timeout happened at LocationTag: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

A network timeout happened at LocationTag: Error

Fields #

Name	Description
`Error`
`LocationTag`
`ObjectName`
`ConnectionWasInScavenge`

Event ID 2043: The secondary database partition 'SecondaryEdbFilePath' of database 'DatabaseName' failed to reseed after the primary partition was succesfully page-patched.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The secondary database partition 'SecondaryEdbFilePath' of database 'DatabaseName' failed to reseed after the primary partition was succesfully page-patched. The primary database is healthy and mountable. Reseed failure: SeedError PreviousStartupMessage: PreviousStartupMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`SecondaryEdbFilePath`
`SeedError`
`PreviousStartupMessage`

Event ID 2050: Suspend log replay requested for database guid=DatabaseGuid, reason='SuspendReason'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend log replay requested for database guid=DatabaseGuid, reason='SuspendReason'.

Fields #

Name	Description
`DatabaseGuid`
`SuspendReason`
`SuspendReasonCode`

Event ID 2051: Suspend log replay for database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend log replay for database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 2052: Suspend log replay for database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Suspend log replay for database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 2053: Resume log replay requested for database guid=DatabaseGuid.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume log replay requested for database guid=DatabaseGuid.

Fields #

Name	Description
`DatabaseGuid`

Event ID 2054: Resume log replay for database guid=DatabaseGuid succeeded.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume log replay for database guid=DatabaseGuid succeeded.

Fields #

Name	Description
`DatabaseGuid`

Event ID 2055: Resume log replay for database guid=DatabaseGuid failed: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Resume log replay for database guid=DatabaseGuid failed: Message

Fields #

Name	Description
`DatabaseGuid`
`Message`

Event ID 2056: RedundancySensorError component encountered an error: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

RedundancySensorError component encountered an error: Message

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 2057: Loss redelivery after incremental reseed for database 'DatabaseName' failed: Error.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Loss redelivery after incremental reseed for database 'DatabaseName' failed: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`

Event ID 2058: The copy of 'DatabaseName' has a loss window from LossStart to LossEnd for which redelivery was requested after incremental reseed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The copy of 'DatabaseName' has a loss window from LossStart to LossEnd for which redelivery was requested after incremental reseed.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LossStart`
`LossEnd`

Event ID 2059: The DAG is configured with ActivityState 'DagActivityState' so the MaxPreferredDatabases check in BCS is treated like MaxActiveDatabases.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The DAG is configured with ActivityState 'DagActivityState' so the MaxPreferredDatabases check in BCS is treated like MaxActiveDatabases.

Fields #

Name	Description
`DagActivityState`

Event ID 2060: The passive copy of 'DatabaseName' has stopped with last log copied at LastLogCopied and inspected at LastLogInspected.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The passive copy of 'DatabaseName' has stopped with last log copied at LastLogCopied and inspected at LastLogInspected.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`LastLogCopied`
`LastLogInspected`

Event ID 2061: The LogCopier for 'DatabaseName' halted communication after ACLL.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

The LogCopier for 'DatabaseName' halted communication after ACLL. FileMode duration: FileModeDuration BlockMode duration: BlockModeDuration.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`FileModeDuration`
`BlockModeDuration`

Event ID 2062: The active copy for database DatabaseGuid ignored CircularLogging because there are CurrentCopyCount copies but ExpectedCopyCount are expected.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The active copy for database DatabaseGuid ignored CircularLogging because there are CurrentCopyCount copies but ExpectedCopyCount are expected.

Fields #

Name	Description
`DatabaseGuid`
`CurrentCopyCount`
`ExpectedCopyCount`

Event ID 2063: Move back to server 'TargetServerName' completed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Move back to server 'TargetServerName' completed. Moved NumberOfDatabasesProcessed database(s) using NumberOfBatches batch(es) in ElapsedTime. NumberOfDatabasesSkipped database(s) not moved because they are either already active, or not preferred.

Fields #

Name	Description
`TargetServerName`
`NumberOfDatabasesProcessed`
`NumberOfBatches`
`ElapsedTime`
`NumberOfDatabasesSkipped`

Event ID 2064: Move back to server 'TargetServerName' timed out after ElapsedTime.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Move back to server 'TargetServerName' timed out after ElapsedTime. Moved NumberOfDatabasesProcessed database(s) in NumberOfBatches batch(es). Up to NumberOfDatabasesSkipped database(s) left to move.

Fields #

Name	Description
`TargetServerName`
`NumberOfDatabasesProcessed`
`NumberOfBatches`
`ElapsedTime`
`NumberOfDatabasesSkipped`

Event ID 2065: Microsoft Exchange Server Locator Service failed to find active server for database 'Database'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Microsoft Exchange Server Locator Service failed to find active server for database 'Database'. Error: Error

Fields #

Name	Description
`Database`
`Error`

Event ID 2066: Microsoft Exchange Server Locator Service failed to find active servers for the database availability group.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Microsoft Exchange Server Locator Service failed to find active servers for the database availability group. Error: Error

Fields #

Name	Description
`Error`

Event ID 2070: Active Manager configuration refresh failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active Manager configuration refresh failed. Error: ErrorMessage

Fields #

Name	Description
`ErrorMessage`

Event ID 2071: Active manager skipped initiating failover for a NodeName due to nodedown event since current HA provider does not support node notifications yet.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager skipped initiating failover for a NodeName due to nodedown event since current HA provider does not support node notifications yet. (Provider: Provider)

Fields #

Name	Description
`Provider`
`NodeName`

Event ID 2072: Active manager skipped initiating failover for a NodeName due to nodedown (confirmed) event since current HA provider does not support node notifications...

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager skipped initiating failover for a NodeName due to nodedown (confirmed) event since current HA provider does not support node notifications yet. (Provider: Provider)

Fields #

Name	Description
`Provider`
`NodeName`

Event ID 2073: Active manager skipped dismounting all locally mounted databases for TriggerEvent event since the current provider is not Windows Failover clustering.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Active manager skipped dismounting all locally mounted databases for TriggerEvent event since the current provider is not Windows Failover clustering. (Provider: Provider)

Fields #

Name	Description
`Provider`
`TriggerEvent`

Event ID 2074: Loose truncation on database DatabaseGuid was performed due to low space.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Loose truncation on database DatabaseGuid was performed due to low space.

Fields #

Name	Description
`DatabaseGuid`
`FreeSpaceInMB`
`MinDiskFreeSpaceThresholdInMB`
`NormalTruncationGen`
`ProtectedCopiesTruncationGen`
`LooseTruncationGenUsed`
`MinGenRequiredByActive`
`CircularLogging`

Event ID 2075: Truncation on database DatabaseGuid is being performed.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Truncation on database DatabaseGuid is being performed.

Fields #

Name	Description
`DatabaseGuid`
`MinGenFromAllPassives`
`MinGenFromProtectedPassives`
`TruncationGenUsed`
`MinGenRequiredByActive`
`CircularLogging`

Event ID 2076: Loose truncation on database DatabaseGuid was performed due to excess log buildup.

Provider: Microsoft-Exchange-HighAvailability
Channel: TruncationDebug

Description

Loose truncation on database DatabaseGuid was performed due to excess log buildup.

Fields #

Name	Description
`DatabaseGuid`
`NormalTruncationGen`
`ProtectedCopiesTruncationGen`
`LooseTruncationGenUsed`
`MinGenRequiredByActive`
`CircularLogging`

Event ID 2077: Microsoft Exchange Server Locator Service Logger failed to commit log information.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Microsoft Exchange Server Locator Service Logger failed to commit log information. Error: Error

Fields #

Name	Description
`Error`

Event ID 2078: Rebalance for CPU found work.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Rebalance for CPU found work.

Fields #

Name	Description
`SourceServers`
`TargetServers`
`IgnoredServers`

Event ID 2079: Rebalance for CPU ignored database 'DatabaseName' because: Reason.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Rebalance for CPU ignored database 'DatabaseName' because: Reason

Fields #

Name	Description
`DatabaseName`
`Reason`

Event ID 2080: Rebalance for CPU moved database 'DatabaseName' from OldActive to NewActive.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Rebalance for CPU moved database 'DatabaseName' from OldActive to NewActive.

Fields #

Name	Description
`DatabaseName`
`OldActive`
`NewActive`

Event ID 2081: Rebalance for CPU timed out after Timeout.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Rebalance for CPU timed out after Timeout.

Fields #

Name	Description
`Timeout`

Event ID 2082: Forced mount for database 'DatabaseName' failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Forced mount for database 'DatabaseName' failed. Error: Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Error`
`AmFlags`
`StoreFlags`

Event ID 2083: Forced mount for database 'DatabaseName' is being attempted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Forced mount for database 'DatabaseName' is being attempted.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`AmFlags`
`StoreFlags`

Event ID 2084: Forced mount for database 'DatabaseName' checked server ServerChecked to determine EDB existence = EDBFound.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Forced mount for database 'DatabaseName' checked server ServerChecked to determine EDB existence = EDBFound.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ServerChecked`
`EDBFound`

Event ID 2090: Database move supporting operations performance details.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Database move supporting operations performance details

Fields #

Name	Description
`UniqueId`
`DatabaseName`
`DatabaseGuid`
`MoveAllOrNoneWaitElapsedTime`
`DismountElapsedTime`
`UpdateAdPropertiesElapsedTime`
`CheckIfMoveApplicableElapsedTime`
`MoveSuppressionCheckElapsedTime`

Event ID 2091: Global truncation for 'DatabaseName' on active ActiveServer took Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Global truncation for 'DatabaseName' on active ActiveServer took Duration.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Duration`
`GenerationSent`

Event ID 2092: LogCopier for database 'DatabaseName' connected to active ActiveServer detected poor performance of Thruput bytes/sec.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

LogCopier for database 'DatabaseName' connected to active ActiveServer detected poor performance of Thruput bytes/sec.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`ActiveServer`
`Thruput`
`MinThruput`
`DetectionWindow`

Event ID 2093: TcpStats report from Context=Context.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

TcpStats report from Context=Context. Client=Client. Server=Server.

Fields #

Name	Description
`Context`
`Client`
`Server`
`BANDWIDTH_ROD`
`FINE_RTT_ROD`
`OBS_REC_ROD`
`PATH_ROD`
`REC_ROD`
`SEND_BUFF_ROD`
`SND_CONG_ROD`

Event ID 2094: TcpStats internal failure.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

TcpStats internal failure. Context=Context. Error=Error

Fields #

Name	Description
`Context`
`Error`

Event ID 2095: LogCopyServer for database 'DatabaseName' sending data to passive PassiveServer detected poor performance of Thruput bytes/sec.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

LogCopyServer for database 'DatabaseName' sending data to passive PassiveServer detected poor performance of Thruput bytes/sec.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`PassiveServer`
`Thruput`
`MinThruput`
`DetectionWindow`

Event ID 2096: ListMDBStatus for server Server failed while hosting actives=HostingActives with exception=Exception.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ListMDBStatus for server Server failed while hosting actives=HostingActives with exception=Exception

Fields #

Name	Description
`Server`
`HostingActives`
`Exception`

Event ID 2097: Local copy of database 'DatabaseName' was hung for restartInterval='RestartInterval' prepareToStopInterval='PrepareToStopInterval'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Local copy of database 'DatabaseName' was hung for restartInterval='RestartInterval' prepareToStopInterval='PrepareToStopInterval'.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`RestartInterval`
`PrepareToStopInterval`
`HangLimit`
`WasDisconnected`
`RecoveryWillBeAttempted`
`RequestRestartStack`

Event ID 2098: Log 'FileName' failed to open after 'DurationOfOpen' with error Exception.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Log 'FileName' failed to open after 'DurationOfOpen' with error Exception

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`FileName`
`DurationOfOpen`
`Exception`

Event ID 2099: Dismount database 'DatabaseName' attempted from CallerContext.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Dismount database 'DatabaseName' attempted from CallerContext. Success=Success.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`CallerContext`
`Success`
`ServerFqdn`
`Flags`
`Duration`
`Error`

Event ID 2100: The Message1 has been Message2.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Message1 has been Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 2101: The callback to update Network Throttling configuration failed with: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The callback to update Network Throttling configuration failed with: Message1. Stack Trace: Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 2102: The IsPrimaryTable operation from Azure storage table (IsPrimary:IsPrimaryTable) failed with: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The IsPrimaryTable operation from Azure storage table (IsPrimary:IsPrimaryTable) failed with: Message. Stack Trace: StackTrace

Fields #

Name	Description
`IsPrimaryTable`
`Operation`
`Message`
`StackTrace`

Event ID 2103: The operation to retrieve the storage configuration from Torus Secret failed with: Message1.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The operation to retrieve the storage configuration from Torus Secret failed with: Message1. Stack Trace: Message2

Fields #

Name	Description
`Message1`
`Message2`

Event ID 2104: Operation:Operation; SourceLocation:SourceLocation; DestinationLocation:DestinationLocation; OperationMessage:Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Operation:Operation; SourceLocation:SourceLocation; DestinationLocation:DestinationLocation; OperationMessage:Message

Fields #

Name	Description
`Operation`
`SourceLocation`
`DestinationLocation`
`Message`

Event ID 2130: Restart RI for database 'DatabaseName' requested.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Restart RI for database 'DatabaseName' requested. Requestor=Requestor. Reason=Reason.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Requestor`
`Reason`
`AdminVisible`
`PrepareToStop`
`Context`
`Exception`
`ChangeHintsReason`
`IsFirstRequest`
`ConfigType`
`StackTrace`

Event ID 2131: RI for database 'DatabaseName' has been selected for restart.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

RI for database 'DatabaseName' has been selected for restart. Reason=Reason, ReasonMessage: ReasonMessage

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Reason`
`ConfigType`
`ConfigChanged`
`ConfigChangeFlags`
`ForceRestart`
`ReasonMessage`

Event ID 2132: Component 'ComponentName' instance 'InstanceName' stopped after 'StopDuration'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Component 'ComponentName' instance 'InstanceName' stopped after 'StopDuration'.

Fields #

Name	Description
`ComponentName`
`InstanceName`
`StopDuration`
`PrepareToStopTime`
`StartOfStopTime`
`EndOfStopTime`

Event ID 2133: Registry value EnableCounterForIoctl could not be set.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

Registry value EnableCounterForIoctl could not be set. This is required for DiskLatencySensor.

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 2134: There was an error reading disk performance data.

Provider: Microsoft-Exchange-HighAvailability
Channel: Monitoring

Description

There was an error reading disk performance data.

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 2135: Restart RI for database 'DatabaseName' has been deferred.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Restart RI for database 'DatabaseName' has been deferred. Reason=Reason.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Reason`

Event ID 2136: ReplayDiagnosticsHandler failed to start: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ReplayDiagnosticsHandler failed to start: Message

Fields #

Name	Description
`Message`

Event ID 2137: Lossy ACLL for database 'DatabaseName' contacted SourceNode to check for additional log data.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Lossy ACLL for database 'DatabaseName' contacted SourceNode to check for additional log data.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`SourceNode`
`HighestFullLogGen`
`HighestBlockModePos`
`ConnectionLatency`
`QueryLatency`
`LastKnownGenFromRepl`
`LastKnownGenFromDxStore`
`TimeoutUsed`
`Exception`

Event ID 2138: Lossy ACLL for database 'DatabaseName' running on RequestingNode contacted this server to check for additional log data.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Lossy ACLL for database 'DatabaseName' running on RequestingNode contacted this server to check for additional log data.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`RequestingNode`
`PamOperationId`
`OldActiveServer`
`HighestLogGenOnRequestor`
`HighestGenFromRepl`
`HighestGenFromDxStore`
`LastBlockModePos`
`DurationToSendReply`
`TotalLogsSent`
`FirstGenSent`
`BlockModeGenSent`
`TimeToClose`
`Error`

Event ID 2139: Lossy ACLL for database 'DatabaseName' used BlockMode generation Generation.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Lossy ACLL for database 'DatabaseName' used BlockMode generation Generation. For remote ACLL=IsRemote.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Generation`
`LastPos`
`LastUtc`
`IsRemote`
`Error`

Event ID 2140: The attempt to truncate local logs for database 'DatabaseName' failed: Exception.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The attempt to truncate local logs for database 'DatabaseName' failed: Exception

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Exception`
`HRESULT`
`FailureTag`

Event ID 2141: The ServiceName service is starting.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The ServiceName service is starting. Extra time requested: AdditionalTime. BackgroundStart=BackgroundStartup

Fields #

Name	Description
`ServiceName`
`AdditionalTime`
`BackgroundStartup`

Event ID 2142: The Message service is stopping without waiting for an incomplete startup to finish.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Message service is stopping without waiting for an incomplete startup to finish.

Fields #

Name	Description
`Message`

Event ID 2143: An override was used to configure the copy of 'DatabaseName' as Role.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An override was used to configure the copy of 'DatabaseName' as Role.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Role`
`StartUtc`
`Duration`
`FqdnOfActiveCopy`

Event ID 2144: Probing file 'FileName' failed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Probing file 'FileName' failed. Win32=Win32Err. Err=Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`FileName`
`Win32Err`
`Error`

Event ID 2145: ACLL driven dismount database 'DatabaseName' succeeded after Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL driven dismount database 'DatabaseName' succeeded after Duration. DurableDismount=DurableDismountObtained.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`DurableDismountObtained`
`Duration`

Event ID 2146: ACLL driven dismount database 'DatabaseName' failed after Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL driven dismount database 'DatabaseName' failed after Duration. Error=Error

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Duration`
`Error`

Event ID 2147: ACLL driven dismount database 'DatabaseName' failed due to timeout after Duration.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ACLL driven dismount database 'DatabaseName' failed due to timeout after Duration.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`Duration`

Event ID 2148: ACLL probe of the EDB for 'DatabaseName' took DurationInMicrosec microseconds.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

ACLL probe of the EDB for 'DatabaseName' took DurationInMicrosec microseconds. DismountNeeded=DismountNeeded

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`DurationInMicrosec`
`DismountNeeded`

Event ID 2149: ProcessAffinity for ServiceName was set successfully=SuccessfullySet.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

ProcessAffinity for ServiceName was set successfully=SuccessfullySet.

Fields #

Name	Description
`ServiceName`
`SuccessfullySet`
`NumProcessors`
`AffinityMask`
`PriorityClass`
`MaxCpu`
`Error`

Event ID 2500: Attempted to upgrade FPGA image from version RpdVersionOnFlash to RpdVersionOnDisk.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Attempted to upgrade FPGA image from version RpdVersionOnFlash to RpdVersionOnDisk. The upgrade Status. Timing Sequence: TimingSequence.

Fields #

Name	Description
`TimingSequence`
`RpdVersionOnFlash`
`RpdVersionOnDisk`
`Status`

Event ID 2501: An attempt to initialize the FPGA was abandoned because the service is stopping.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An attempt to initialize the FPGA was abandoned because the service is stopping. Timing Sequence: TimingSequence.

Fields #

Name	Description
`TimingSequence`

Event ID 2502: An exception was thrown while trying to perform an operation on the FPGA.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

An exception was thrown while trying to perform an operation on the FPGA. The reported error code was ErrorCode. Exception message: Message

Fields #

Name	Description
`ErrorCode`
`Message`

Event ID 2503: Operation failed with error: ErrorCode.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Operation failed with error: ErrorCode

Fields #

Name	Description
`Operation`
`ErrorCode`

Event ID 2504: FpgaCoreLib.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FpgaCoreLib.dll couldn't be loaded. Fpga initialization will be skipped.

Event ID 3000: Microsoft Exchange Server 'RequestingMachineName' initiated bug check for server 'TargetMachineName'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Microsoft Exchange Server 'RequestingMachineName' initiated bug check for server 'TargetMachineName'. (Source: Source, Identity: Identity)

Fields #

Name	Description
`BugcheckId`
`InitiatedTimeUtc`
`RequestedTimeUtc`
`Source`
`Identity`
`Context`
`Reason`
`ProcessToKill`
`RequestingMachineName`
`TargetMachineName`
`RequestingProcessName`

Event ID 3001: Triggered Active manager configuration refresh since PAM change notification received from server 'ReportingServer'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Triggered Active manager configuration refresh since PAM change notification received from server 'ReportingServer' (ReportingServerPrevRole: 'ReportingServerPreviousAmRole', LocalServerPamView: 'LocalServerViewOfPam', LocalServerAmRole: 'LocalServerAmRole').

Fields #

Name	Description
`ReportingServer`
`ReportingServerPreviousAmRole`
`LocalServerViewOfPam`
`LocalServerAmRole`

Event ID 3002: Received PAM change notification received from server 'ReportingServer' but skipped config refresh.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Received PAM change notification received from server 'ReportingServer' but skipped config refresh (ReportingServerPrevRole: 'ReportingServerPreviousAmRole', LocalServerPamView: 'LocalServerViewOfPam', LocalServerAmRole: 'LocalServerAmRole', IsConfigManagerValid: 'IsConfigManagerValid').

Fields #

Name	Description
`ReportingServer`
`ReportingServerPreviousAmRole`
`LocalServerViewOfPam`
`LocalServerAmRole`
`IsConfigManagerValid`

Event ID 3003: The DB copies 'DBNames' on Volume with volume id 'VolumeId' have been forcefully failed and suspended by VolumeForceSuspenderForReformat.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The DB copies 'DBNames' on Volume with volume id 'VolumeId' have been forcefully failed and suspended by VolumeForceSuspenderForReformat.

Fields #

Name	Description
`VolumeId`
`DBNames`

Event ID 3004: The volume 'VolumeId' was forcefully formatted.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

The volume 'VolumeId' was forcefully formatted.

Fields #

Name	Description
`VolumeId`

Event ID 3005: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Message

Fields #

Name	Description
`Message`

Event ID 3006: Found an empty encrypted NTFS spare : VolumeId.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Found an empty encrypted NTFS spare : VolumeId

Fields #

Name	Description
`VolumeId`

Event ID 3007: Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Message

Fields #

Name	Description
`Message`

Event ID 3008: Found a potential ReFS volume for force dismount : VolumeId.

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

Found a potential ReFS volume for force dismount : VolumeId. Now checking to see if databases on volume have enough redundancy.

Fields #

Name	Description
`VolumeId`

Event ID 3009: ReFStoNTFS reformat failed server prereqs for failed and suspended, seeding copies: Number of failed and suspended copies, seeding on the server '%...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

ReFStoNTFS reformat failed server prereqs for failed and suspended, seeding copies: Number of failed and suspended copies, seeding on the server 'ServerName' should be less than 'Threshold'

Fields #

Name	Description
`ServerName`
`Threshold`

Event ID 3010: ReFStoNTFS reformat failed dag prereqs for failed and suspended, seeding copies: Number of failed and suspended, seeding copies on the dag 'ServerName' sho...

Provider: Microsoft-Exchange-HighAvailability
Channel: Seeding

Description

ReFStoNTFS reformat failed dag prereqs for failed and suspended, seeding copies: Number of failed and suspended, seeding copies on the dag 'ServerName' should be less than 'Threshold'

Fields #

Name	Description
`ServerName`
`Threshold`

Event ID 3013: Avg FFB on DatabaseName was AvgLatencyInMsec mSec.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

Avg FFB on DatabaseName was AvgLatencyInMsec mSec.

Fields #

Name	Description
`DatabaseGuid`
`DatabaseName`
`MaxLatencyInMsec`
`MinLatencyInMsec`
`AvgLatencyInMsec`
`TotalFlushes`
`MeasurementWindow`
`Buckets`

Event ID 3014: Full reseed for database 'DatabaseName\MachineName' finished.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Full reseed for database 'DatabaseName\MachineName' finished. (Primary partition: Overall Seed = PrimaryPartitionOverallElapsedTime, Stream Edb file = PrimaryPartitionStreamFileElapsedTime, Deploy file and divergence check = PrimaryPartitionDeployFileAtEndOfSeedElapsedTime, Delete log files = PrimaryPartitionDeleteLogFilesElapsedTime, Update DBHeader From Trailer = PrimaryPartitionUpdateDBHeaderFromTrailerElapsedTime, Divergence Checking = PrimaryPartitionDivergenceCheckingElapsedTime, Flush Changes = PrimaryPartitionFlushChangesElapsedTime). (Secondary partition: Overall Seed = SecondaryPartitionOverallElapsedTime, Stream Edb file = SecondaryPartitionStreamFileElapsedTime, Deploy file and divergence check = SecondaryPartitionDeployFileAtEndOfSeedElapsedTime, Delete log files = SecondaryPartitionDeleteLogFilesElapsedTime, Update DBHeader From Trailer = SecondaryPartitionUpdateDBHeaderFromTrailerElapsedTime, Divergence Checking = SecondaryPartitionDivergenceCheckingElapsedTime, Flush Changes = SecondaryPartitionFlushChangesElapsedTime)

Fields #

Name	Description
`DatabaseName`
`DatabaseGuid`
`MachineName`
`PrimaryPartitionOverallElapsedTime`
`SecondaryPartitionOverallElapsedTime`
`PrimaryPartitionStreamFileElapsedTime`
`SecondaryPartitionStreamFileElapsedTime`
`PrimaryPartitionDeployFileAtEndOfSeedElapsedTime`
`SecondaryPartitionDeployFileAtEndOfSeedElapsedTime`
`PrimaryPartitionDeleteLogFilesElapsedTime`
`SecondaryPartitionDeleteLogFilesElapsedTime`
`PrimaryPartitionUpdateDBHeaderFromTrailerElapsedTime`
`SecondaryPartitionUpdateDBHeaderFromTrailerElapsedTime`
`PrimaryPartitionDivergenceCheckingElapsedTime`
`SecondaryPartitionDivergenceCheckingElapsedTime`
`PrimaryPartitionFlushChangesElapsedTime`
`SecondaryPartitionFlushChangesElapsedTime`

Event ID 3015: Disk monitor component [Message] started.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk monitor component [Message] started.

Fields #

Name	Description
`Message`

Event ID 3016: Disk monitor component [Message] Succeed.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk monitor component [Message] Succeed.

Fields #

Name	Description
`Message`

Event ID 3017: Disk monitor component [Message] Failed: StackTrace.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk monitor component [Message] Failed: StackTrace.

Fields #

Name	Description
`Message`
`StackTrace`

Event ID 3018: Disk [Message1]: partition access paths: Message2, the expected protected status should be: Message3.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Disk [Message1]: partition access paths: Message2, the expected protected status should be: Message3

Fields #

Name	Description
`Message1`
`Message2`
`Message3`

Event ID 3019: FQDN resolution failed for server ServerName with error : Message.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

FQDN resolution failed for server ServerName with error : Message. The following stacktrace provides the call chain: StackTrace

Fields #

Name	Description
`ServerName`
`Message`
`StackTrace`

Event ID 3020: CallSite encountered SerializationException with a message of : ExceptionMessage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Debug

Description

CallSite encountered SerializationException with a message of : ExceptionMessage

Fields #

Name	Description
`CallSite`
`ExceptionMessage`

Event ID 9000: The Disk Reclaimer used-only encrypted volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer used-only encrypted volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Fields #

Name	Description
`VolumeName`
`MountedFolder`

Event ID 9001: The Disk Reclaimer failed to used-only encrypt volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer failed to used-only encrypt volume 'VolumeName' mounted at 'MountedFolder' as a spare. Exception: Exception ReturnValue: ReturnValue ErrorMessage: ErrorMessage

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`Exception`
`ReturnValue`
`ErrorMessage`

Event ID 9002: The Disk Reclaimer couldn't find any empty spare volumes to encrypt.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer couldn't find any empty spare volumes to encrypt.

Event ID 9003: The Disk Reclaimer found 'VolumeCount' candidates for Encryption.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer found 'VolumeCount' candidates for Encryption.

Fields #

Name	Description
`VolumeCount`

Event ID 9004: The Disk Reclaimer successfully used-only encrypted 'SuccessCount' Empty volumes and failed encrypting 'FailureCount' Empty volumes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer successfully used-only encrypted 'SuccessCount' Empty volumes and failed encrypting 'FailureCount' Empty volumes.

Fields #

Name	Description
`SuccessCount`
`FailureCount`

Event ID 9005: Unable to get Win32_EncryptableVolume object for volume : 'SuccessCount' due to error : 'FailureCount'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Unable to get Win32_EncryptableVolume object for volume : 'SuccessCount' due to error : 'FailureCount'.

Fields #

Name	Description
`SuccessCount`
`FailureCount`

Event ID 9006: The Disk Reclaimer skipped encrypting empty Win8 volumes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer skipped encrypting empty Win8 volumes. Disabled config is set to true.

Event ID 9007: Volume 'VolumeName' is mounted on a virtual disk.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Volume 'VolumeName' is mounted on a virtual disk. So not getting bitlocker status.

Fields #

Name	Description
`VolumeName`

Event ID 9008: The Disk Reclaimer skipped calling Bitlocker Maintenance as the config is disabled.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer skipped calling Bitlocker Maintenance as the config is disabled..

Event ID 9009: he Disk Reclaimer failed to start full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

he Disk Reclaimer failed to start full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare. Exception: Exception ReturnValue: ReturnValue ErrorMessage: ErrorMessage

Fields #

Name	Description
`VolumeName`
`MountedFolder`
`Exception`
`ReturnValue`
`ErrorMessage`

Event ID 9010: The Disk Reclaimer started full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer started full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare.

Fields #

Name	Description
`VolumeName`
`MountedFolder`

Event ID 9012: The Disk Reclaimer successfully started full volume encryption on volume 'SuccessCount' Empty volumes and failed to start enncrypting 'FailureCount' Empty volumes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer successfully started full volume encryption on volume 'SuccessCount' Empty volumes and failed to start enncrypting 'FailureCount' Empty volumes.

Fields #

Name	Description
`SuccessCount`
`FailureCount`

Event ID 9014: The Disk Reclaimer skipped encrypting empty Win7 volumes.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer skipped encrypting empty Win7 volumes. Disabled config is set to true.

Event ID 9016: Bitlocker Encryption Percentage for volume 'VolumeName' is at 'EncryptionPercentage' percentage.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Bitlocker Encryption Percentage for volume 'VolumeName' is at 'EncryptionPercentage' percentage.

Fields #

Name	Description
`VolumeName`
`EncryptionPercentage`

Event ID 9017: The Disk Reclaimer is calling Win7 encryption method in BitlockerHelper.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer is calling Win7 encryption method in BitlockerHelper.cs from an Win8 Operating System.

Event ID 9019: The Disk Reclaimer is calling Win8 encryption method in BitlockerHelper.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

The Disk Reclaimer is calling Win8 encryption method in BitlockerHelper.cs from an Win7 Operating System.

Event ID 9021: Bitlocker Encryption failed for mountpoint 'MountPoint' volume 'VolumeName' due to error 'Error'.

Provider: Microsoft-Exchange-HighAvailability
Channel: Operational

Description

Bitlocker Encryption failed for mountpoint 'MountPoint' volume 'VolumeName' due to error 'Error'. Corresponding Bitlocker event 'EventXML'.

Fields #

Name	Description
`VolumeName`
`Error`
`EventXML`
`MountPoint`

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)