Microsoft-Exchange-HighAvailability

EventTitleChannelSampleRule
100Initiating startup automount.OperationalNN
101Initiating automount due to store start on server 'ServerFqdn'.OperationalNN
103Active Manager started.OperationalNN
104Active Manager start postponed.OperationalNN
105Active Manager stopped.OperationalNN
106ACLL failed while performing switchover on shutdown for database 'DatabaseName'.OperationalNN
107Lossy mount enabled for database 'DatabaseName'.OperationalNN
108Mount rejected for database 'DatabaseName' since data loss exceeds configured …OperationalNN
109Role monitor started with role 'Role'.OperationalNN
110Cluster node state change detected for node 'NodeNameFqdn' (Node …OperationalNN
111Active manager role changed from 'PreviousRole' to 'CurrentRole'.OperationalNN
112Database 'DatabaseName' is attempting to mount on server 'ServerFqdn'.OperationalNN
113Database 'DatabaseName' failed to mount on server 'ServerFqdn' with error: …OperationalNN
114Database 'DatabaseName' mounted successfully on server 'ServerFqdn'.OperationalNN
118Database 'DatabaseName' is attempting to move to 'ToServer'.OperationalNN
119Database 'DatabaseName' failed to move to 'ToServer' with error: ErrorMessage.OperationalNN
120Database 'DatabaseName' moved successfully to 'ToServer'.OperationalNN
121Direct mount operation failed for database (Guid=DatabaseGuid, …OperationalNN
122Direct dismount operation failed for database (Guid=DatabaseGuid, …OperationalNN
123Switchover on shutdown initated for server 'SourceServer'.OperationalNN
124Switchover on shutdown failed for server 'SourceServer' with error: …OperationalNN
125Switchover on shutdown successfully completed for server 'SourceServer'.OperationalNN
126Server operation generated unhandled exception (Exception=ExceptionString).OperationalNN
127Forcefully dismounting all the locally mounted databases on server 'ServerFqdn' …OperationalNN
128Service monitor detected that 'Service' service is now running.OperationalNN
129Service monitor detected that 'Service' service is now stopped.OperationalNN
130Store service start detected but configuration is currently invalid.OperationalNN
131The FacilityDescription has been successfully initialized.OperationalNN
132Failure item notification registration for database 'DatabaseName' failed.OperationalNN
133Finished startup automount (AttemptedMounts=MountedCount, …OperationalNN
134Finished automounting due to store start (Node=NodeName, …OperationalNN
135Finished failover (Node=NodeName, Databases=DatabaseCount).OperationalNN
136Finished switchover (Node=NodeName, Databases=DatabaseCount).OperationalNN
137Initiating server failover (Node=NodeName).OperationalNN
138Initiating server switchover (Node=NodeName).OperationalNN
139Message.OperationalNN
140Mount rejected for database 'DatabaseName' since attempts to copy the last logs …OperationalNN
141Database 'DatabaseName' failed to mount (error: ErrorMessage).OperationalNN
142Database 'DatabaseName' failed to dismount (error: ErrorMessage).OperationalNN
143Database 'DatabaseName' failed to move (error: ErrorMessage).OperationalNN
144Active Manager skipped automounting database 'DatabaseName' since MountAtStartup …OperationalNN
145Active Manager skipped automounting database 'DatabaseName' since it was admin …OperationalNN
146ReplayState 'StateName' for database 'DatabaseName(DatabaseGuid)' on node …DebugNN
147Database 'DatabaseName' cannot be activated on possible target server …OperationalNN
148Database 'DatabaseName' cannot be activated on any server because none of their …OperationalNN
149An error occurred while trying to select database copy 'DatabaseName' on server …OperationalNN
150Database copy 'DatabaseName' on server 'PossibleServer' has been selected for …OperationalNN
151An error occurred while trying to validate the specified database copy …OperationalNN
152Database copy 'DatabaseName' on specified server 'TargetServer' has passed …OperationalNN
153ACLL completed without loss while performing switchover on shutdown for database …OperationalNN
154ACLL completed without loss for database 'DatabaseName'.OperationalNN
155Database 'DatabaseName' successfully copied the last logs to server 'ToServer' …OperationalNN
156Database property update failed on local site (db='DatabaseName', …OperationalNN
157Database property remote replication request failed (db='DatabaseName', …OperationalNN
158Database property remote replication request succeeded (db='DatabaseName', …OperationalNN
159Store service is stopped on node 'NodeName' and all the database which were …OperationalNN
160There seems to be a database operation which is already in progress.OperationalNN
161There seems to be a database operation which is already in progress.OperationalNN
162Database 'DatabaseName' copied the last logs to server 'ToServer' from server …OperationalNN
163The attempt to copy remaining uncopied logs failed for database Database.OperationalNN
164Databases are being marked as dismounted because the store was stopped on server …OperationalNN
165Database DatabaseName on server ServerFqdn is being dismounted because it's not …OperationalNN
166The batch mounter operation failed with error ErrorMessage.OperationalNN
167Best copy selection for database 'DatabaseName' failed to get the database …OperationalNN
168Active manager did not perform an action for server 'ServerName' since debug …OperationalNN
169Debug options settings are enabled on this Database availability group.OperationalNN
170Log TruncationState 'StateName' for database 'DatabaseName(DatabaseGuid)' on …TruncationDebugNN
171Active manager received system event EventCode from server ServerReporting.OperationalNN
172Persistent state of database DatabaseName is synchronized.OperationalNN
173Active directory properties of database DatabaseName is synchronized.OperationalNN
174The cluster group is hosted on this server but the current role is Unknown.OperationalNN
175The cluster group was already moved.OperationalNN
176This server is now running as 'Role'.OperationalNN
177The cluster group is being moved to server 'NodeName'.OperationalNN
178The cluster group was successfully moved to server 'NodeName'.OperationalNN
179The cluster group failed to move to server 'NodeName'.OperationalNN
180An error was encounted accessing the cluster'.OperationalNN
181No new cluster owner could be found.OperationalNN
182Active Directory access has failed.OperationalNN
183Active Directory access is now functioning properly.DebugNN
184Node status could not be recorded.OperationalNN
185Mapi access to this node may be broken.OperationalNN
186Mapi access to this node is expected to be operational because windows …OperationalNN
187Mapi access to this node is expected to be operational because Active Directory …OperationalNN
188Initiating move of all active databases (Node=NodeName).OperationalNN
189Finished moving all active databases (Node=NodeName, Databases=DatabaseCount, …OperationalNN
190Moving all active databases failed for server 'SourceServer' (MoveComment: …OperationalNN
191Database 'DatabaseName' cannot be activated on server 'ServerName' because the …OperationalNN
192Suspend requested for database guid=DatabaseGuid, comment='SuspendComment', …OperationalNN
193Suspend database guid=DatabaseGuid succeeded.OperationalNN
194Suspend database guid=DatabaseGuid failed: Message.OperationalNN
195Resume requested for database guid=DatabaseGuid, flags='ResumeFlags'.OperationalNN
196Resume database guid=DatabaseGuid succeeded.OperationalNN
197Resume database guid=DatabaseGuid failed: Message.OperationalNN
198BeginSeed requested for database guid=DatabaseGuid, args='SeedArgs'.OperationalNN
199BeginSeed database guid=DatabaseGuid succeeded.OperationalNN
200BeginSeed database guid=DatabaseGuid failed: Message.OperationalNN
201CancelSeed requested for database guid=DatabaseGuid.OperationalNN
202CancelSeed database guid=DatabaseGuid succeeded.OperationalNN
203CancelSeed database guid=DatabaseGuid failed: Message.OperationalNN

Event ID 100: Initiating startup automount.

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
ServerFqdn

Event ID 103: Active Manager started.

#
Channel
Operational

Event ID 104: Active Manager start postponed.

#
Channel
Operational

Event ID 105: Active Manager stopped.

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

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

#
Channel
Operational

Fields #

NameDescription
Role

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

#
Channel
Operational

Fields #

NameDescription
NodeNameFqdn
NodeState

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

#
Channel
Operational

Fields #

NameDescription
CurrentRole
PreviousRole

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerFqdn
MountFlags
MountDialOverride
TryOtherServers
ActionCode

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerFqdn
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerFqdn

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ToServer
FromServer
MountFlags
DismountFlags
MountDialOverride
TryOtherServers
ActionCode

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ToServer
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ToServer

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
SourceServer

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

#
Channel
Operational

Fields #

NameDescription
SourceServer
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
SourceServer

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

#
Channel
Operational

Fields #

NameDescription
ExceptionString

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

#
Channel
Operational

Fields #

NameDescription
ServerFqdn
Reason

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

#
Channel
Operational

Fields #

NameDescription
Service

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

#
Channel
Operational

Fields #

NameDescription
Service

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

#
Channel
Operational

Event ID 131: The FacilityDescription has been successfully initialized.

#
Channel
Operational

Fields #

NameDescription
FacilityDescription

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
MountedCount
DismountedCount
DbSyncedCount
MoveCount

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

#
Channel
Operational

Fields #

NameDescription
NodeName
MountedCount
DismountedCount
DbSyncedCount
MoveCount

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

#
Channel
Operational

Fields #

NameDescription
NodeName
DatabaseCount

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

#
Channel
Operational

Fields #

NameDescription
NodeName
DatabaseCount

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

#
Channel
Operational

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Fields #

NameDescription
NodeName

Event ID 139: Message.

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid

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

#
Channel
Debug

Fields #

NameDescription
DatabaseName
DatabaseGuid
NodeName
StateName
OldValue
NewValue

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid

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

#
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 #

NameDescription
DatabaseName
DatabaseGuid
PossibleServer
ChecksRun
ErrorMessage
OperationId
CheckThatFailed

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
DatabaseGuid
TargetServer
ChecksRun
ErrorMessage
OperationId

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
TargetServer
ChecksRun
OperationId

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ToServer
SourceServer

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer
LocalSiteDN
Error

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer
SiteDNList
DcsContactedList
Error

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
NodeName
Count

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

#
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 #

NameDescription
DatabaseGuid
Error

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

#
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 #

NameDescription
DatabaseGuid
Error

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ToServer
SourceServer

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

#
Channel
Operational

Description

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

Fields #

NameDescription
Database
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerFqdn

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

#
Channel
Operational

Fields #

NameDescription
ErrorMessage

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
ServerName
DebugOption
Hint

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

#
Channel
Operational

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

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseName
DatabaseGuid
NodeName
StateName
OldValue
NewValue

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

#
Channel
Operational

Fields #

NameDescription
EventCode
ServerReporting

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
PreviousMountStatus
NewMountStatus
ActiveServer

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
InitialOwningServer
NewActiveServer

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

#
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Fields #

NameDescription
Role

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

#
Channel
Operational

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Description

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

Fields #

NameDescription
NodeName
Message

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

#
Channel
Operational

Description

An error was encounted accessing the cluster'. Message

Fields #

NameDescription
Message

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

#
Channel
Operational

Event ID 182: Active Directory access has failed.

#
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.

#
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
Message1
Message2

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

#
Channel
Operational

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

#
Channel
Operational

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

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
NodeName

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

#
Channel
Operational

Fields #

NameDescription
NodeName
DatabaseCount
MoveComment

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

#
Channel
Operational

Fields #

NameDescription
SourceServer
ErrorMessage
MoveComment

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerName
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
SuspendComment
SuspendFlags
Initiator

Event ID 193: Suspend database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
ResumeFlags

Event ID 196: Resume database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
SeedArgs

Event ID 199: BeginSeed database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

Event ID 202: CancelSeed database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Operation
Server

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Operation
Server

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Operation
Server
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
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 #

NameDescription
DatabaseName
Message

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName

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

#
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 #

NameDescription
DatabaseName
ServerName

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

#
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 #

NameDescription
DatabaseName
ServerName
Message1
Message2
Message3

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

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
TruncationDebug

Description

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

Fields #

NameDescription
DatabaseGuid
PassiveServerName
GenToPreserve
LocalGenRequired

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

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
TruncationDebug

Fields #

NameDescription
Message1
Message2
Message3

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

#
Channel
TruncationDebug

Fields #

NameDescription
Message

Event ID 227: Active manager configuration change detected.

#
Channel
Operational

Description

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

Fields #

NameDescription
CurrentRole
PreviousRole
ChangeFlags
LastError

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Debug

Fields #

NameDescription
DatabaseName
ServerName

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Debug

Fields #

NameDescription
DatabaseName
ServerName
LowGeneration
HighGeneration

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

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

#
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 #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
FailedGeneration
ErrorMessage

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
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'.

#
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 #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
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'.

#
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 #

NameDescription
DatabaseName
SourceServerName
TargetServerName
TotalBytesSent
SendTimeSpan
Thruput
EdbFilePath

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ErrorMessage
LastBootTime
BugcheckReason

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

#
Channel
Operational

Fields #

NameDescription
BugcheckReason
BugcheckSkippedReason

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ShutdownInitiatedTime

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

#
Channel
Operational

Fields #

NameDescription
ServerName
DatabaseGuid
Flags
RetryOnConflict

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ServerName
DatabaseGuid
ErrorMessage
DurableDismount
Duration

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

#
Channel
Operational

Description

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

Fields #

NameDescription
IsSuccess

Event ID 263: Initiating graceful crash of store process.

#
Channel
Operational

Event ID 264: Finished graceful crash of store process.

#
Channel
Operational

Fields #

NameDescription
ErrorMessage

Event ID 265: The FacilityDescription has been stopped.

#
Channel
Operational

Fields #

NameDescription
FacilityDescription

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

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseName
PassiveServerName

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

#
Channel
BlockReplication

Fields #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DisableReason

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ApiName
StartTime
Elapsed
HintStr
MaxAllowedLatency

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

#
Channel
Operational

Fields #

NameDescription
ApiName
StartTime
Elapsed
HintStr
IsUnhandledException
ReturnCode
MaxAllowedLatency

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ServiceName
Reason
ErrorMessage

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

#
Channel
Operational

Description

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

Fields #

NameDescription
Delay

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

#
Channel
Operational

Fields #

NameDescription
Role

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

#
Channel
Operational

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

#
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 #

NameDescription
ServerName
ReasonCode
ReportedTime
Delay

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ServerName
DueTime

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

#
Channel
Operational

Fields #

NameDescription
ServerName
Reason

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

#
Channel
Operational

Fields #

NameDescription
ServerName

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

#
Channel
Operational

Description

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

Fields #

NameDescription
Operation
ServerName
ErrorMessage

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ApiName
ErrorCode
Hint

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

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Monitoring

Fields #

NameDescription
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.

#
Channel
Monitoring

Fields #

NameDescription
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...

#
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 #

NameDescription
DatabaseGuid
PassiveServerName
StartGenTruncated
GenToPreserve
GenToPreserveWithoutCheckpoint

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
ErrorMessage
FailoverSequenceNumber

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
FailoverSequenceNumber

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
ErrorMessage
FailoverSequenceNumber

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
FailoverSequenceNumber
DurableDismount

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

#
Channel
Operational

Fields #

NameDescription
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...

#
Channel
Operational

Description

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

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
ErrorMessage
FailoverSequenceNumber

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
ActiveServer
ElapsedTime
FailoverSequenceNumber

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
SourceServer

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
MountFlags
IsLossyMountEnabled
AMMountFlags

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
ElapsedTime
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
ElapsedTime

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
DismountFlags
BestEffortTimeout

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
RunningOnServer
DismountMode
ElapsedTime
DurableDismount

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
PreviousActiveServer
CurrentActiveServer

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
SkippedOnServer
ErrorMessage

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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...

#
Channel
Operational

Description

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

Fields #

NameDescription
Role
AuthoritativeServer
ElapsedTimeInCurrentRole
ChangeFlags
LastError
ServersInMaintenance

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

#
Channel
Debug

Fields #

NameDescription
SystemEvent

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

#
Channel
Debug

Fields #

NameDescription
SystemEvent

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

#
Channel
Debug

Fields #

NameDescription
SystemEvent
Duration

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

#
Channel
Debug

Fields #

NameDescription
SystemEvent
Duration
Exception

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

#
Channel
Debug

Fields #

NameDescription
SystemEvent
Duration

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

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
BcsType
IsStatusFetcherConstructed

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

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
AttemptNumber
ElapsedTime
HasDatabaseBeenMountedElapsedTime
GetDatabaseCopiesElapsedTime
DetermineServersToContactElapsedTime
GetCopyStatusRpcElapsedTime

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
SourceDir
TargetDir
Exception

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

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
Message

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

#
Channel
Operational

Description

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

Fields #

NameDescription
ApiName
StartTime
Elapsed
HintStr
MaxAllowedLatency

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

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Monitoring

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage
ExceptionFullString

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

#
Channel
Monitoring

Fields #

NameDescription
DatabaseName
DatabaseGuid
TotalSpaceInMB
RemainingSpaceInMB
RemainingSpacePercent
CopyQueueLen
ReplayQueueLen
MinLogGen
MaxLogGen
HealthyCopyCount
MinRequiredHealthy

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage
StackTrace
Exception
HResult

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

#
Channel
Operational

Fields #

NameDescription
MachineName
FailureCategory
Threshold
FailureSuppressionDurationMinute

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

#
Channel
Operational

Fields #

NameDescription
MachineName

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

#
Channel
Operational

Fields #

NameDescription
MachineName

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

#
Channel
Operational

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

#
Channel
Operational

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

#
Channel
Operational

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage
StackTrace
LastCopiedGen
LastNotifiedGen

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

#
Channel
Operational

Fields #

NameDescription
MachineName
FailureCategory
Threshold
FailureSuppressionDurationMinute

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

#
Channel
Operational

Fields #

NameDescription
MachineName
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
MachineName

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

#
Channel
Operational

Fields #

NameDescription
MachineName
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
MachineName

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

#
Channel
Operational

Description

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

Fields #

NameDescription
MachineName
ErrorCode
ErrorMessage
FailureSuppressionDurationMinutes

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

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
Message

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

#
Channel
Operational

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

#
Channel
Operational

Description

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

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Operational

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

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
CurrentActiveFQDN
MountDesired

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

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
Message

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

#
Channel
Operational

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

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Operational

Fields #

NameDescription
Message

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message
StackTrace

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
NewActiveServerName
Message
StackTrace

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

#
Channel
Operational

Fields #

NameDescription
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'.

#
Channel
Operational

Fields #

NameDescription
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'.

#
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 #

NameDescription
DatabaseGuid
CurrentActiveFQDN
MountDesired
Error

Event ID 700: Disk heartbeat started.

#
Channel
Operational

Event ID 701: Disk heartbeat stopped.

#
Channel
Operational

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

#
Channel
Monitoring

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid
DisableReason
DisableSuppression

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
DatabaseGuid
LogGeneration
LogFileAge
LowestGenerationRequired
HighestGenerationRequired

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
LogGeneration
LogFileAge
Reason
ReasonCode

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
LogGeneration
LogFileAge
PrevHighestGenToReplay
HighestGenerationToReplay

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

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

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

#
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 #

NameDescription
DatabaseName
DatabaseGuid
PreviousActiveServer
LastLogGenBeforeActivation
NumberOfLogsLost
FailoverTimeUtc
StartTimeUtc
EndTimeUtc
IsRequestInOldDumpsterSchema
IsRequestFromSafetyNet
RequestOrigin
RequestGuid

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
IsRequestInOldDumpsterSchema
ErrorMessage
ExceptionFullString

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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...

#
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 #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
TotalServersCount
SuccessfulReplyCount

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

#
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 #

NameDescription
TotalServersCount
SuccessfulReplyCount

Event ID 719: Majority node check completed.

#
Channel
Operational

Description

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

Fields #

NameDescription
Elapsed
IsMajority
TotalServersContacted
SuccessfulRepliesReceived

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

#
Channel
Operational

Event ID 721: LastKnownGoodConfig serialization failed.

#
Channel
Operational

Description

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

Fields #

NameDescription
Mode
Error

Event ID 722: LastKnownGoodConfig initialized from registry.

#
Channel
Operational

Description

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

Fields #

NameDescription
Role
AuthoritativeServer
Members

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer
IsMountAtStartup
IsAdminDismounted
IsMountAttemptedAtleastOnce
IsStoreGracefullyStoppedOnActive

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Timeout

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

#
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 #

NameDescription
DatabaseName
DatabaseGuid
ExceptionMessage

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

#
Channel
Operational

Fields #

NameDescription
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.

#
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 #

NameDescription
TotalServersCount
SuccessfulReplyCount

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

#
Channel
Operational

Description

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

Fields #

NameDescription
BugcheckReason

Event ID 729: Attempting to cause BugCheck.

#
Channel
Operational

Description

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

Fields #

NameDescription
LastBootTime
BugcheckReason

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

#
Channel
Operational

Description

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

Fields #

NameDescription
BugcheckReason
DisabledRegKey
DisabledTimeUtc

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Flags

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

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
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...

#
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 #

NameDescription
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).

#
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 #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid
DisableReason
DisableSuppression

Event ID 739: The store service is being killed.

#
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
Reason
Detail
WatsonDuration
StackTrace

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

#
Channel
Operational

Fields #

NameDescription
MachineName
FlagsString
FlagsInt

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

#
Channel
Operational

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
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'.

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid
EnableSuppression
UndelayReason

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
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...

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid
EnableSuppression
UndelayReason

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

#
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 #

NameDescription
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').

#
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 #

NameDescription
Path
ThresholdDuration
IOHangDuration

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

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

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

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseName
TimeoutInterval
StackTrace

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName
Constraint

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

#
Channel
Monitoring

Fields #

NameDescription
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...

#
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 #

NameDescription
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.

#
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 #

NameDescription
DatabaseName
PassiveLogCopyGeneration
ServerName
TimeRecieved

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName
Details

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

#
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 #

NameDescription
DatabaseName
ServerName
PassiveLogCopyGeneration
TimeRecieved
PassiveLogInspectionGeneration
PassiveLogReplayGeneration

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

#
Channel
Monitoring

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Monitoring

Description

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

Fields #

NameDescription
DatabaseName

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

#
Channel
Monitoring

Fields #

NameDescription
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...

#
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 #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
ServerName
Role
Exception
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
ErrorMessage
Phase

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

#
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 #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
PamServerName

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

#
Channel
Operational

Fields #

NameDescription
FromServer
ToServer

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

#
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.

#
Channel
Operational

Description

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

Fields #

NameDescription
Duration
Result
Operation

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

#
Channel
Operational

Fields #

NameDescription
FromServer
ToServer

Event ID 820: AD lookup failed: Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage

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

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
SeedReason

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

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
SeedReason

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
TargetServer
ErrorMessage

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

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2
Message3

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

#
Channel
Debug

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
LocalNodeName
CopyRole
Stack

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

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

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

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

#
Channel
Operational

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
StartingGen
ActiveServer

Event ID 838: The copy 'DatabaseName\ServerName' failed to get start gen from global coordinator.

#
Channel
Operational

Description

The copy 'DatabaseName\ServerName' failed to get start gen from global coordinator. Error: Message1

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 840: Database 'DatabaseName' failed to mount on server 'ServerFqdn' due to timeout: ErrorMessage.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ServerFqdn
ErrorMessage

Event ID 841: ListMdbStatus failed to server 'NodeName': Message.

#
Channel
Operational

Fields #

NameDescription
NodeName
Message

Event ID 842: ListMdbStatus = MdbStatusFlags for database 'DatabaseName' (DatabaseGuid) on MailboxServer.

#
Channel
Debug

Fields #

NameDescription
DatabaseName
DatabaseGuid
MailboxServer
MdbStatusFlags

Event ID 843: Recovery from ListMdbStatus failure is being attempted.

#
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.

#
Channel
Operational

Description

Recovery from ListMdbStatus failure is being attempted. All databases on NodeName will be dismounted.

Fields #

NameDescription
NodeName

Event ID 845: Failed to close the backup reader handle for database 'DatabaseName' ('DatabaseGuid').

#
Channel
Seeding

Description

Failed to close the backup reader handle for database 'DatabaseName' ('DatabaseGuid'). Error: ErrorMessage

Fields #

NameDescription
DatabaseGuid
DatabaseName
ErrorMessage

Event ID 846: Database 'DatabaseName' has no copies and is being ignored.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 847: GetDiskFreeSpaceEx failed with error ErrorCode using path 'DatabasePath' for database DatabaseGuid.

#
Channel
TruncationDebug

Description

GetDiskFreeSpaceEx failed with error ErrorCode using path 'DatabasePath' for database DatabaseGuid. Loose truncation is not possible.

Fields #

NameDescription
DatabaseGuid
ErrorCode
DatabasePath

Event ID 848: Low disk space exists on the active (local) copy of database DatabaseGuid.

#
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 #

NameDescription
DatabaseGuid
PassiveServerName
GenIgnored

Event ID 849: The IoBufferPool used by block mode replication was initialized with BufferCount buffers.

#
Channel
Operational

Description

The IoBufferPool used by block mode replication was initialized with BufferCount buffers. Details: Explanation

Fields #

NameDescription
BufferCount
Explanation

Event ID 850: Mount status validation failed after database 'DatabaseName' could not be moved from 'ActiveServer'.

#
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 #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer
ActiveManagerMountStatus
StoreMountStatus

Event ID 851: Full server reseed is being started.

#
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.

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid

Event ID 853: Full server reseed failed to resume database copy 'DatabaseName\ServerName'.

#
Channel
Seeding

Description

Full server reseed failed to resume database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 854: Full server reseed encountered an error.

#
Channel
Seeding

Description

Full server reseed encountered an error. Error: Message

Fields #

NameDescription
Message

Event ID 855: Full server reseed has completed kicking off reseeds.

#
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 #

NameDescription
Message1
Message2

Event ID 856: Full server reseed is now attempting to reseed database copy 'DatabaseName\ServerName'.

#
Channel
Seeding

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid

Event ID 857: Full server reseed failed to reseed database copy 'DatabaseName\ServerName'.

#
Channel
Seeding

Description

Full server reseed failed to reseed database copy 'DatabaseName\ServerName'. Error: Message1

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 858: Full server reseed is being skipped because the Microsoft Exchange Replication service is being stopped.

#
Channel
Seeding

Event ID 859: Another instance of a full server reseed is already running.

#
Channel
Seeding

Event ID 860: Database 'DatabaseName' is active on a disfavored server but cannot be moved because all servers are marked with DatabaseCopyActivationDisabledAndMoveNow.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 861: Loose truncation is being used on database 'DatabaseName'.

#
Channel
TruncationDebug

Description

Loose truncation is being used on database 'DatabaseName'. Generation LooseTruncGen is used in place of StandardTruncGen.

Fields #

NameDescription
DatabaseGuid
DatabaseName
StandardTruncGen
LooseTruncGen

Event ID 862: Truncation for database 'DatabaseGuid' was unable to find file 'MissingFileName'.

#
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 #

NameDescription
DatabaseGuid
MissingFileName

Event ID 863: The support api failed to start: Message.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 864: The TCP listener has started listening on port Port.

#
Channel
Operational

Fields #

NameDescription
Port

Event ID 865: Serialization failed: Message.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 866: Truncation for database 'DatabaseGuid' is paused because a backup is in progress.

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseGuid

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

#
Channel
Seeding

Description

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

Fields #

NameDescription
DatabaseGuid
DatabaseName
SeedReason
Status
ErrorMessage

Event ID 868: The TCP listener failed to start listening on port Port.

#
Channel
Operational

Description

The TCP listener failed to start listening on port Port. Error: Error

Fields #

NameDescription
Port
Error

Event ID 869: Windows is configured for scavenge replication on port Port.

#
Channel
Operational

Fields #

NameDescription
Port

Event ID 870: Windows is not configured for scavenge replication.

#
Channel
Operational

Event ID 871: Windows is failed to configure for scavenge replication on port Port.

#
Channel
Operational

Description

Windows is failed to configure for scavenge replication on port Port. Error:Error

Fields #

NameDescription
Port
Error

Event ID 872: Replication for passive copy of DatabaseName is switching to scavenge.

#
Channel
Operational

Description

Replication for passive copy of DatabaseName is switching to scavenge. Reason: Reason.

Fields #

NameDescription
DatabaseGuid
DatabaseName
Reason

Event ID 873: Replication for passive copy of DatabaseName is switching to normal.

#
Channel
Operational

Description

Replication for passive copy of DatabaseName is switching to normal. Reason: Reason.

Fields #

NameDescription
DatabaseGuid
DatabaseName
Reason

Event ID 874: Active Directory is in a failed state.

#
Channel
Operational

Description

Active Directory is in a failed state. ComponentTag: ComponentTag. Error: Error

Fields #

NameDescription
ComponentTag
Error

Event ID 875: The replication TCP port stored in the registry failed.

#
Channel
Operational

Description

The replication TCP port stored in the registry failed. Operation: Operation. Error Error

Fields #

NameDescription
Operation
Error

Event ID 876: FileMode for database 'DatabaseName' is connected at gen StartingGen with the active on ActiveServer.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
StartingGen
ActiveServer
LocalEndPoint
SendingEndPoint

Event ID 877: Log file 'LogFileName' has unexpected signature 'LogFileSig' instead of 'ExpectedSig'.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
LogFileName
LogFileSig
ExpectedSig
ActualHex
ExpectedHex
Stack

Event ID 878: Thread priority was not downgraded: Message.

#
Channel
Operational

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
Channel
Operational

Description

FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is not attached. [CheckpointGeneration: CheckpointGen, LastConsistentGen: LastConsistentGen, LowestGenerationPresent: LowestGenerationPresent]

Fields #

NameDescription
DatabaseName
DatabaseGuid
PartitionID
DbState
LastConsistentGen
CheckpointGen
EdbFilePath
CheckpointFilePath
LowestGenerationPresent

Event ID 881: FileChecker determined that database file 'EdbFilePath' for database 'DatabaseName' (DatabaseGuid) is missing.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
PartitionID
EdbFilePath

Event ID 882: File-mode replication for database 'DatabaseName' is starting with passive PassiveServer at generation LogGen.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
LogGen
PassiveServer
LocalEndPoint
ReceivingEndPoint

Event ID 883: File-mode replication for database 'DatabaseName' is terminating with passive PassiveServer at generation LogGen.

#
Channel
Debug

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
ServerName
Message1
Message2

Event ID 900: The passive copy of 'DatabaseName' is starting its components.

#
Channel
Debug

Description

The passive copy of 'DatabaseName' is starting its components. ActiveServer=ActiveServer

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer

Event ID 901: The copy of 'DatabaseName' encountered an unusual situation: Details.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
Details

Event ID 902: ACLL starting for 'DatabaseName'.

#
Channel
Debug

Description

ACLL starting for 'DatabaseName'. Active is ActiveServer.

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
PAMOperationId

Event ID 903: ACLL for 'DatabaseName' finished after Duration.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
Duration
PAMOperationId

Event ID 904: ACLL for 'DatabaseName' failed after Duration.

#
Channel
Debug

Description

ACLL for 'DatabaseName' failed after Duration. Error:PAMOperationId

Fields #

NameDescription
DatabaseGuid
DatabaseName
Duration
PAMOperationId
Error

Event ID 905: Mount for local copy of 'DatabaseName' is starting.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 906: IncrementalReseed for 'DatabaseName' is replacing OldLog with NewLog.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
OldLog
NewLog
LogGen

Event ID 907: Acll for 'DatabaseName' failed due to an active incompatible operation: Error.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
PAMOperationId
Error

Event ID 908: Mount for 'DatabaseName' failed due to an active incompatible operation: Error.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 909: Database 'DatabaseName' was seeded to TargetServer.

#
Channel
Seeding

Description

Database 'DatabaseName' was seeded to TargetServer. Success=Success.

Fields #

NameDescription
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'.

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName
EdbFilePath
ErrorMessage

Event ID 911: DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'.

#
Channel
Seeding

Description

DB Seeding has completed for the local copy of database 'DatabaseName' (DatabaseGuid) on file 'EdbFilePath'. Error: ErrorMessage

Fields #

NameDescription
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...

#
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 #

NameDescription
DatabaseGuid
DatabaseName
EdbFilePath
ErrorMessage

Event ID 913: Failed to close the backup reader file handle for 'EdbFilePath' of database 'DatabaseName' ('DatabaseGuid').

#
Channel
Seeding

Description

Failed to close the backup reader file handle for 'EdbFilePath' of database 'DatabaseName' ('DatabaseGuid'). Error: ErrorMessage

Fields #

NameDescription
DatabaseGuid
DatabaseName
EdbFilePath
ErrorMessage

Event ID 1000: BlockMode replication could not obtain the lock on the timer.

#
Channel
BlockReplication

Description

BlockMode replication could not obtain the lock on the timer. Recovery should be automatic.

Fields #

NameDescription
DatabaseName
LockTimeoutLimit

Event ID 1001: A client-side network connection to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' succeeded.

#
Channel
Network

Fields #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint

Event ID 1002: A client-side attempt to connect to RemoteNodeName using 'RemoteEndpoint' from 'LocalEndpoint' failed: Error.

#
Channel
Network

Fields #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint
Error

Event ID 1003: Database redundancy health check failed.

#
Channel
Monitoring

Description

Database redundancy health check failed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1004: Database redundancy health check passed.

#
Channel
Monitoring

Description

Database redundancy health check passed. Database: DatabaseName Redundancy count: HealthyCopiesCount IsSuppressed: IsSuppressed Error: ErrorMessage

Fields #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid
IsSuppressed

Event ID 1005: Database site-level redundancy health check failed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1006: Database site-level redundancy health check passed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1007: Database availability health check failed.

#
Channel
Monitoring

Description

Database availability health check failed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1008: Database availability health check passed.

#
Channel
Monitoring

Description

Database availability health check passed. Database: DatabaseName Redundancy count: HealthyCopiesCount Error: ErrorMessage

Fields #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1009: Database site-level availability health check failed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1010: Database site-level availability health check passed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1011: Health validation check 'CheckName' for database copy 'DatabaseCopyName' produced a Warning.

#
Channel
Monitoring

Description

Health validation check 'CheckName' for database copy 'DatabaseCopyName' produced a Warning. Error: ErrorMessage

Fields #

NameDescription
DatabaseCopyName
CheckName
ErrorMessage

Event ID 1012: Database Health Monitor component encountered an error: Message.

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

Event ID 1013: A server-side connection is open with client RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

#
Channel
Network

Fields #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint

Event ID 1014: A server-side connection was closed.

#
Channel
Network

Description

A server-side connection was closed. Client RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint

Event ID 1015: A client-side connection was closed.

#
Channel
Network

Description

A client-side connection was closed. Server RemoteNodeName using remote 'RemoteEndpoint' and local 'LocalEndpoint'.

Fields #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint

Event ID 1016: A server-side idle connection is being closed.

#
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 #

NameDescription
RemoteNodeName
RemoteEndpoint
LocalEndpoint
IdleSinceUtc
IdleTimespan

Event ID 1017: Database redundancy two-copy health check passed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1018: Database redundancy two-copy health check failed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
ErrorMessage
DatabaseGuid

Event ID 1019: An inconsistency was detected by network discovery: 'Message' Normally this is due to transient network configuration.

#
Channel
Network

Fields #

NameDescription
Message

Event ID 1020: This server rejected a connection attempt from remote 'RemoteEndpoint' to 'LocalEndpoint'.

#
Channel
Network

Description

This server rejected a connection attempt from remote 'RemoteEndpoint' to 'LocalEndpoint'. Error: Error

Fields #

NameDescription
RemoteEndpoint
LocalEndpoint
Error

Event ID 1021: Database 'DatabaseName' appears to have a copy status cached entry that has not been updated recently.

#
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 #

NameDescription
DatabaseGuid
DatabaseName

Event ID 1022: Some databases on server 'Message1' have copy status cached entries that have not been updated recently.

#
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 #

NameDescription
Message1
Message2

Event ID 1023: Database remote connectivity health check failed.

#
Channel
Monitoring

Description

Database remote connectivity health check failed. Database: DatabaseName Error: ErrorMessage

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

Event ID 1024: Database remote connectivity health check passed.

#
Channel
Monitoring

Description

Database remote connectivity health check passed. Database: DatabaseName

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 1025: Health validation check 'CheckName' for database copy 'DatabaseCopyName' is being suppressed.

#
Channel
Monitoring

Description

Health validation check 'CheckName' for database copy 'DatabaseCopyName' is being suppressed. Error: ErrorMessage

Fields #

NameDescription
DatabaseCopyName
CheckName
ErrorMessage

Event ID 1026: All databases on server 'Message' have copy status cached entries that have been updated recently.

#
Channel
Monitoring

Fields #

NameDescription
Message

Event ID 1027: PAM monitor failure to restart ClusSvc on Server.

#
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 #

NameDescription
Server
IsSkippedDueToRegistryOverride
IsSkippedDueToTimeCheck
IsThrottled
ErrorMessage

Event ID 1028: PAM monitor successfully restarted ClusSvc on Server.

#
Channel
Operational

Fields #

NameDescription
Server

Event ID 1029: Database RPC Authentication health check failed.

#
Channel
Monitoring

Description

Database RPC Authentication health check failed. Database: DatabaseName Error: ErrorMessage

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage

Event ID 1030: Database RPC Authentication health check passed.

#
Channel
Monitoring

Description

Database RPC Authentication health check passed. Database: DatabaseName

Fields #

NameDescription
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...

#
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 #

NameDescription
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.

#
Channel
Operational

Description

Managed Availability health tracker encountered an error. Hint:Message, Error:'StackTrace'.

Fields #

NameDescription
Message
StackTrace

Event ID 1101: Initiating move of all active databases requested by a managed availability component (Node=NodeName, Component=ComponentName).

#
Channel
Operational

Fields #

NameDescription
NodeName
ComponentName

Event ID 1102: Finished moving all active databases requested by a managed availability component (Node=NodeName, Databases=DatabaseCount, MoveComment=MoveComment, Component=ComponentName).

#
Channel
Operational

Fields #

NameDescription
NodeName
DatabaseCount
MoveComment
ComponentName

Event ID 1103: Server: ServerName HealthStates: HealthStates.

#
Channel
Operational

Description

Server: ServerName HealthStates: HealthStates

Fields #

NameDescription
ServerName
HealthStates

Event ID 1104: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

#
Channel
AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

NameDescription
AppLogEventID
AppLogEventMessage
AppLogEventArgs

Event ID 1105: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

#
Channel
AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

NameDescription
AppLogEventID
AppLogEventMessage
AppLogEventArgs

Event ID 1106: AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage.

#
Channel
AppLogMirror

Description

AppLogEventID: AppLogEventID AppLogEventMessage: AppLogEventMessage

Fields #

NameDescription
AppLogEventID
AppLogEventMessage
AppLogEventArgs

Event ID 1107: Automatic Reseed Manager component encountered an error: Message.

#
Channel
Seeding

Fields #

NameDescription
Message
StackTrace

Event ID 1108: Automatic Reseed Manager component encountered an error when processing database 'DatabaseName': ErrorMessage.

#
Channel
Seeding

Fields #

NameDescription
DatabaseName
DatabaseGuid
ErrorMessage
ExceptionFullString

Event ID 1109: Automatic Reseed Manager is starting repair workflow 'WorkflowName' for database 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager is starting repair workflow 'WorkflowName' for database 'DatabaseName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason

Event ID 1110: Automatic Reseed Manager successfully completed repair workflow 'WorkflowName' for database 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager successfully completed repair workflow 'WorkflowName' for database 'DatabaseName'. WorkflowLaunchReason: WorkflowLaunchReason

Fields #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason

Event ID 1111: Automatic Reseed Manager failed to execute repair workflow 'WorkflowName' for database 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager failed to execute repair workflow 'WorkflowName' for database 'DatabaseName'. Error: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason
ErrorMessage

Event ID 1112: Automatic Reseed Manager has detected a content indexing error for database 'DatabaseName'.

#
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 #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason

Event ID 1115: Unable to read database 'DatabaseName' throttling configuration.

#
Channel
Monitoring

Description

Unable to read database 'DatabaseName' throttling configuration. Error: ErrorMessage

Fields #

NameDescription
DatabaseName
ErrorMessage

Event ID 1116: Server-level health validation check failed to update the LastRunTime in the local registry.

#
Channel
Monitoring

Description

Server-level health validation check failed to update the LastRunTime in the local registry. Error: Message

Fields #

NameDescription
Message
StackTrace

Event ID 1117: Automatic Reseed Manager throttled repair workflow 'WorkflowName' for database 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager throttled repair workflow 'WorkflowName' for database 'DatabaseName'. Details: ErrorMessage WorkflowLaunchReason: WorkflowLaunchReason

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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'.

#
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 #

NameDescription
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...

#
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 #

NameDescription
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'.

#
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 #

NameDescription
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'.

#
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 #

NameDescription
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'.

#
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 #

NameDescription
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'.

#
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 #

NameDescription
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.

#
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 #

NameDescription
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...

#
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 #

NameDescription
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...

#
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 #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason
ErrorMessage

Event ID 1131: The Disk Reclaimer is searching for quarantined disks that can potentially be formatted and reclaimed.

#
Channel
Seeding

Event ID 1132: The Disk Reclaimer failed to pass the database redundancy health check for one or more databases on this server.

#
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 #

NameDescription
Reason

Event ID 1133: The Disk Reclaimer failed to reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
Channel
Seeding

Description

The Disk Reclaimer failed to reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare. [FormatSucceeded=FormatSucceeded] Error: ErrorMessage

Fields #

NameDescription
VolumeName
MountedFolder
FormatSucceeded
ErrorMessage
Exception

Event ID 1134: The Disk Reclaimer succeeded to format and reclaim volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
Channel
Seeding

Fields #

NameDescription
VolumeName
MountedFolder

Event ID 1135: The Disk Reclaimer encountered an error: ErrorMessage.

#
Channel
Seeding

Fields #

NameDescription
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.

#
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 #

NameDescription
VolumeName
MountedFolder
ErrorMessage

Event ID 1137: The Disk Reclaimer started configuring volume mountpoints after Reinstall on this server.

#
Channel
Seeding

Description

The Disk Reclaimer started configuring volume mountpoints after Reinstall on this server. Regkey 'Reason' is set.

Fields #

NameDescription
Reason

Event ID 1138: The Disk Reclaimer PostInstall configuration is attempting to resume all copies on server 'Server'.

#
Channel
Seeding

Fields #

NameDescription
Server

Event ID 1139: The Disk Reclaimer found one or more unknown databases while configuring mountpoints for volume 'VolumeName'.

#
Channel
Seeding

Description

The Disk Reclaimer found one or more unknown databases while configuring mountpoints for volume 'VolumeName'. Error: ErrorMessage.

Fields #

NameDescription
VolumeName
ErrorMessage

Event ID 1140: The Disk Reclaimer PostInstall configuration encountered an error while configuring mountpoints for volume 'VolumeName'.

#
Channel
Seeding

Description

The Disk Reclaimer PostInstall configuration encountered an error while configuring mountpoints for volume 'VolumeName'. Error: ErrorMessage

Fields #

NameDescription
VolumeName
ErrorMessage

Event ID 1141: The Disk Reclaimer finished configuring volume mountpoints after Reinstall on this server.

#
Channel
Seeding

Description

The Disk Reclaimer finished configuring volume mountpoints after Reinstall on this server. Attempting to disable regkey 'Reason'.

Fields #

NameDescription
Reason

Event ID 1142: The Disk Reclaimer is about to quarantine corrupted disk or volume 'VolumeName' mounted at 'MountedFolder' for format.

#
Channel
Seeding

Description

The Disk Reclaimer is about to quarantine corrupted disk or volume 'VolumeName' mounted at 'MountedFolder' for format. Error: ErrorMessage.

Fields #

NameDescription
VolumeName
MountedFolder
ErrorMessage

Event ID 1143: The Disk Reclaimer skipped reclaiming volume 'VolumeName' mounted at 'MountedFolder'.

#
Channel
Seeding

Description

The Disk Reclaimer skipped reclaiming volume 'VolumeName' mounted at 'MountedFolder'. Error ErrorMessage.

Fields #

NameDescription
VolumeName
MountedFolder
ErrorMessage

Event ID 1144: The Disk Reclaimer found 'Count' never mounted active databases on the server.

#
Channel
Seeding

Description

The Disk Reclaimer found 'Count' never mounted active databases on the server. Databases: 'Databases'.

Fields #

NameDescription
Count
Databases

Event ID 1145: The Disk Reclaimer found never mounted active database: 'Database' missing volume mountpoint.

#
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 #

NameDescription
Database

Event ID 1146: The Disk Reclaimer was unable to fixup mountpoint for active database: 'DatabaseName'.

#
Channel
Seeding

Description

The Disk Reclaimer was unable to fixup mountpoint for active database: 'DatabaseName'. Error ErrorMessage.

Fields #

NameDescription
DatabaseName
ErrorMessage

Event ID 1147: The Disk Reclaimer was unable to mount active database: 'DatabaseName'.

#
Channel
Seeding

Description

The Disk Reclaimer was unable to mount active database: 'DatabaseName'. Error ErrorMessage.

Fields #

NameDescription
DatabaseName
ErrorMessage

Event ID 1148: The Disk Reclaimer completed its attempt to fix volume mountpoints for active databases on server: Server.

#
Channel
Seeding

Fields #

NameDescription
Server

Event ID 1149: The Volume Manager found the following volumes: UnknownVolumeCount=UnknownVolumeCount UnEncryptedEmptySpareVolumeCount=UnEncryptedEmptySpareVolumeCount EncryptingEmptySpareVolumeCount=EncryptingEmp...

#
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 #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 1151: The Disk Reclaimer PostInstall configuration found a misconfigured volume 'VolumeName'.

#
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 #

NameDescription
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.

#
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 #

NameDescription
Count
VolumesStr

Event ID 1153: Automatic Reseed Manager is being skipped because: Message.

#
Channel
Seeding

Fields #

NameDescription
Message

Event ID 1154: The Disk Reclaimer is being skipped because: Message.

#
Channel
Seeding

Fields #

NameDescription
Message

Event ID 1155: The Disk Reclaimer encountered an Active Directory error: ErrorMessage.

#
Channel
Seeding

Fields #

NameDescription
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.

#
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 #

NameDescription
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'.

#
Channel
Operational

Fields #

NameDescription
FormattedVolumeCount
FormattedVolumePathList

Event ID 1158: The Disk Reclaimer didn't found any formatted volumes.

#
Channel
Operational

Event ID 1160: Cluster API operation seems to be hung.

#
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 #

NameDescription
ApiName
StartTime
Context

Event ID 1161: Hung node detection completed (GUM ID: GumId LockOwner: LockOwner Context: Context).

#
Channel
Operational

Fields #

NameDescription
GumId
LockOwner
Context

Event ID 1162: Hung node detection failed (Error: ErrorMessage).

#
Channel
Operational

Fields #

NameDescription
ErrorMessage
Exception

Event ID 1163: Attempt to open the cluster on server ServerName timed out while trying to find the hung nodes.

#
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 #

NameDescription
ServerName
ErrorMessage
Context

Event ID 1164: Attempt to kill cluster service was skipped since the registry override IsKillClusterServiceOnClusApiHang is set to false.

#
Channel
Operational

Event ID 1165: Sending a request to kill ServiceName service on server ServerName.

#
Channel
Operational

Fields #

NameDescription
ServiceName
ServerName

Event ID 1166: ServiceName service successfully killed on server ServerName.

#
Channel
Operational

Fields #

NameDescription
ServiceName
ServerName
ReplyContext

Event ID 1167: An attempt to kill ServiceName service on server ServerName failed.

#
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 #

NameDescription
ServiceName
ServerName
IsThrottled
Reason
IsUnhandledException
ReplyContext

Event ID 1168: Request received to kill ServiceName service from server ServerName.

#
Channel
Operational

Fields #

NameDescription
ServiceName
ServerName
Context

Event ID 1169: Killing process ProcessName.

#
Channel
Operational

Description

Killing process ProcessName. (Service: ServiceName, ProcessId: ProcessId)

Fields #

NameDescription
ServiceName
ProcessName
ProcessId
Context

Event ID 1170: Hung node action skipped since gum id change was observed in the detection.

#
Channel
Operational

Description

Hung node action skipped since gum id change was observed in the detection. (LocalGumId=LocalGumId, RemoteGumId=RemoteGumId)

Fields #

NameDescription
LocalGumId
RemoteGumId
LockOwnerName
HungNodesMask

Event ID 1171: Incremental Reseed (DatabaseName\ServerName) failed to copy log generation Message2 from the source server after Message1 retries.

#
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 #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1
Message2
Message3
Message4

Event ID 1172: Bandwidth Monitor is now running.

#
Channel
Operational

Event ID 1173: Bandwidth Monitor stopped.

#
Channel
Operational

Event ID 1174: Bandwidth Monitor raised exception: Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 1180: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual resume operation.

#
Channel
Seeding

Fields #

NameDescription
DatabaseName
DatabaseGuid
AttemptNumber

Event ID 1181: Automatic Reseed Manager determined that database 'DatabaseName' recovered from a FailedAndSuspended state due to a manual reseed operation.

#
Channel
Seeding

Fields #

NameDescription
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 ...

#
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 #

NameDescription
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...

#
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 #

NameDescription
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...

#
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 #

NameDescription
DatabaseName
DatabaseGuid
AttemptNumber

Event ID 1185: An in-place reseed has been requested for the local copy of database 'DatabaseGuid'.

#
Channel
Seeding

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 1186: The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'.

#
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 #

NameDescription
VolumeName
MountedFolder
ExpectedCount
ActualCount

Event ID 1187: The Volume Manager found misconfigured volume 'VolumeName' mounted at 'MountedFolder'.

#
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 #

NameDescription
VolumeName
MountedFolder
ExpectedCount
ActualCount

Event ID 1188: Automatic Reseed Manager found never mounted active database 'Database' missing volume mountpoint.

#
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 #

NameDescription
Database

Event ID 1189: Automatic Reseed Manager allocated volume 'VolumeName' for never mounted active database 'Database'.

#
Channel
Seeding

Fields #

NameDescription
Database
VolumeName

Event ID 1190: Automatic Reseed Manager was unable to fixup mountpoint for active database: 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager was unable to fixup mountpoint for active database: 'DatabaseName'. Error: ErrorMessage

Fields #

NameDescription
DatabaseName
ErrorMessage

Event ID 1191: Automatic Reseed Manager was unable to mount active database: 'DatabaseName'.

#
Channel
Seeding

Description

Automatic Reseed Manager was unable to mount active database: 'DatabaseName'. Error: ErrorMessage

Fields #

NameDescription
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.

#
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 #

NameDescription
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 ...

#
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 #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason

Event ID 1194: A reseed to spare volume has been requested for the local copy of database 'DatabaseGuid'.

#
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 #

NameDescription
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...

#
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 #

NameDescription
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...

#
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 #

NameDescription
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...

#
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 #

NameDescription
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...

#
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 #

NameDescription
DatabaseName
DatabaseGuid
WorkflowName
WorkflowLaunchReason
MaxRetries
WorkflowNextRunAfter

Event ID 1210: Attempt to initiate system failover for replay service down failed for server ServerName.

#
Channel
Operational

Description

Attempt to initiate system failover for replay service down failed for server ServerName. (Error: Error)

Fields #

NameDescription
ServerName
Error

Event ID 1211: System failover skipped for server ServerName.

#
Channel
Operational

Description

System failover skipped for server ServerName. (Reason: Reason, Phase: Phase)

Fields #

NameDescription
ServerName
Reason
Phase

Event ID 1212: Throttling check did not allow system failover to proceed for server ServerName.

#
Channel
Operational

Description

Throttling check did not allow system failover to proceed for server ServerName. (TooSoonPerNode:IsActionCalledTooSoonPerNode, TooSoonAcrossDag:IsActionCalledTooSoonAcrossDag, MaxPerNodeExceeded:IsMaxActionsPerNodeExceeded, MaxAcrossDagExceeded:IsMaxActionsAcrossDagExceeded)

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
ServerName
MostRecentActionDataForNode
MostRecentActionDataAcrossDag
ActionsCountPerNode
ActionsCountAcrossDag
MinDurationBetweenActionsPerNode
MaxCheckDurationPerNode
MaxAllowedActionsPerNode
MinDurationBetweenActionsAcrossDag
MaxCheckDurationAcrossDag
MaxAllowedActionsAcrossDag

Event ID 1214: Failed to initialize throttled action traker state from cluster database.

#
Channel
Operational

Description

Failed to initialize throttled action traker state from cluster database. (Action: ActionName, MaxHistory=MaxHistorySize, Error: Error)

Fields #

NameDescription
ActionName
MaxHistorySize
Error

Event ID 1215: Failover on replay down feature is disabled with registry override.

#
Channel
Operational

Event ID 1216: Failover on replay down tracker is not initialized.

#
Channel
Operational

Event ID 1217: Starting action Action for cluster node NodeName.

#
Channel
Operational

Fields #

NameDescription
NodeName
Action
DurationJoiningCheck
DurationInProgressCheck
InProgressState
NodeState

Event ID 1218: Completed action Action for cluster node NodeName.

#
Channel
Operational

Fields #

NameDescription
NodeName
Action
InProgressState
NodeState
Error

Event ID 1219: Cluster node action Action is blocked for NodeName since there are operations still pending.

#
Channel
Operational

Fields #

NameDescription
NodeName
Action
InProgressState

Event ID 1220: Cluster node action Action is blocked for NodeName since there are nodes that are in Joining state.

#
Channel
Operational

Fields #

NameDescription
NodeName
Action
JoiningNodes

Event ID 1230: Cached last log updater failed to update last log generation info.

#
Channel
Operational

Description

Cached last log updater failed to update last log generation info. (Count: EntriesCount)

Fields #

NameDescription
EntriesCount
ErrorMessage

Event ID 1231: An rpc request to PAM to update last log generation info failed.

#
Channel
Operational

Description

An rpc request to PAM to update last log generation info failed. (Role: Role)

Fields #

NameDescription
Role
LastUpdatedTimeBasedOnPAM
ErrorMessage

Event ID 1232: Initiating cluster database updates from local nodes in stead of Primary Active Manager (LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

#
Channel
Operational

Fields #

NameDescription
FirstLocalUpdateTime
LastServerUpdateTimeAsPerClusdb
LastServerUpdateTimeAsPerPam
BatcherWriterStartTime
RpcError

Event ID 1233: Continuing cluster database updates locally (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

#
Channel
Operational

Fields #

NameDescription
FirstLocalUpdateTime
LastServerUpdateTimeAsPerClusdb
LastServerUpdateTimeAsPerPam
BatcherWriterStartTime
RpcError

Event ID 1234: Switching back to PAM based to cluster database updates (FirstLocalUpdateTime:FirstLocalUpdateTime, LastServerUpdateTimeAsPerClusdb: LastServerUpdateTimeAsPerClusdb).

#
Channel
Operational

Fields #

NameDescription
FirstLocalUpdateTime
LastServerUpdateTimeAsPerClusdb
LastServerUpdateTimeAsPerPam
BatcherWriterStartTime
RpcError

Event ID 1235: Database 'DatabaseName' copy on server 'ServerName' is too far behind.

#
Channel
Monitoring

Description

Database 'DatabaseName' copy on server 'ServerName' is too far behind. Copy queue is: CopyQueue and replay queue is ReplayQueue.

Fields #

NameDescription
DatabaseName
ServerName
CopyQueue
ReplayQueue

Event ID 1236: After TimeoutInSeconds seconds the SocketStream leaked resources to allow its termination processing to continue.

#
Channel
Operational

Fields #

NameDescription
TimeoutInSeconds

Event ID 1237: SocketStream could not obtain buffer space.

#
Channel
Operational

Description

SocketStream could not obtain buffer space. Memory fragmentation may result.

Event ID 1238: Database file 'EdbFilePath' for database 'DatabaseName' finished seeding.

#
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 #

NameDescription
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.

#
Channel
Operational

Description

Negotiation of compression with server 'RemoteNodeName' failed. Further negotiation will not be attempted until service restart.

Fields #

NameDescription
RemoteNodeName
RequestedConfiguration
Exception

Event ID 1240: Remote server 'RemoteNodeName' passed an unrecognized compression configuration.

#
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 #

NameDescription
RemoteNodeName
RequestedConfiguration
Exception

Event ID 1241: PAM Monitor is attempting to perform the recovery.

#
Channel
Operational

Description

PAM Monitor is attempting to perform the recovery. Server roles view: ServerView

Fields #

NameDescription
ServerView

Event ID 1242: PAM move cancelled since majority are not running as SAM (Total: TotalServersInDag, SAM: TotalServersInSamRole, MinimumRequired: MinimumRequired).

#
Channel
Operational

Fields #

NameDescription
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).

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
QueueLength
RequestedOperationClass
RequestedOperationUniqueId
RequestedOperationDetails
InProgressOperationClass
InProgressOperationUniqueId
InProgressOperationDetails
NextOperationClass
NextOperationUniqueId
NextOperationDetails

Event ID 1244: MonitoredDatabase for database 'DatabaseName' failed to start: ExceptionMessage HRESULT=HRESULT.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ExceptionMessage
HRESULT
FullException
DatabasePath

Event ID 1245: Attempt to query bitlocked failed: Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 1246: Seeding starts for local copy of database 'DatabaseName'.

#
Channel
Seeding

Description

Seeding starts for local copy of database 'DatabaseName'. Global truncation reports InitialGlobalMin initially yielding FinalGlobalMin.

Fields #

NameDescription
DatabaseGuid
DatabaseName
InitialGlobalMin
FinalGlobalMin

Event ID 1247: Seeding for local copy of database 'DatabaseName' failed to establish divergence check file 'DivergenceCheckFile' : Error.

#
Channel
Seeding

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
NumPages
Error

Event ID 1249: Seeding for local copy of database 'DatabaseName' was cancelled.

#
Channel
Seeding

Description

Seeding for local copy of database 'DatabaseName' was cancelled. AdminRequested=AdminRequested.

Fields #

NameDescription
DatabaseGuid
DatabaseName
AdminRequested

Event ID 1250: Cluster batch writer failed while attempting operation 'Operation' (error: ErrorMessage).

#
Channel
Operational

Fields #

NameDescription
Operation
ErrorMessage

Event ID 1251: The MonitoredDatabase for database 'DatabaseName' was requested to stop at StartOfCleanupUtc which took StopDuration.

#
Channel
Operational

Description

The MonitoredDatabase for database 'DatabaseName' was requested to stop at StartOfCleanupUtc which took StopDuration. EOL at EndOfLogGeneration EndOfLogUtc

Fields #

NameDescription
DatabaseGuid
DatabaseName
StopDuration
StartOfCleanupUtc
EndOfLogGeneration
EndOfLogUtc

Event ID 1252: The Disk Reclaimer has removed the mountpoint 'MountPoint'.

#
Channel
Seeding

Fields #

NameDescription
MountPoint

Event ID 1253: The Disk Reclaimer has added the mountpoint 'MountPoint' => 'Volume'.

#
Channel
Seeding

Fields #

NameDescription
MountPoint
Volume

Event ID 1254: The Disk Reclaimer has created the folder for database 'Database' at 'Folder'.

#
Channel
Seeding

Fields #

NameDescription
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'.

#
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 . Since this failure was due to throttling, attempt number AttemptNumber will be reexecuted WorkflowLaunchReason: WorkflowLaunchReason

Fields #

NameDescription
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'.

#
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 #

NameDescription
VolumeName
MountedFolder
ErrorMessage

Event ID 1270: The secondary partition status for the local copy of database 'DatabaseName' could not be overridden: Error: Error.

#
Channel
Operational

Description

The secondary partition status for the local copy of database 'DatabaseName' could not be overridden: Error: Error

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 1300: Start gathering hung node information via RPC calls (List of servers: ListOfServers).

#
Channel
Operational

Fields #

NameDescription
ListOfServers

Event ID 1301: Start gathering cluster node status (ClusterOpen node: ClusterOpenTarget).

#
Channel
Operational

Fields #

NameDescription
ClusterOpenTarget

Event ID 1302: Hung Node information gathering completed (HungNodeInfo: HungNodeInfo).

#
Channel
Operational

Fields #

NameDescription
HungNodeInfo

Event ID 1303: Hung Node information analysis completed (HungNodeAction: HungNodeAction).

#
Channel
Operational

Fields #

NameDescription
HungNodeAction

Event ID 1310: Start recovery action for cluster node hung (Target servers: TargetServers).

#
Channel
Operational

Fields #

NameDescription
TargetServers

Event ID 1311: Requesting remote reboot (target servers: RebootServers) and restart of clussvc service (target servers: RestartServers) of hung nodes.

#
Channel
Operational

Fields #

NameDescription
RebootServers
RestartServers

Event ID 1320: Attempt to remote reboot of target node succeeded (Target: Targets, DebugMessage: ActionMessage).

#
Channel
Operational

Fields #

NameDescription
Targets
ActionMessage

Event ID 1321: Attempt to remote reboot of target node failed or throttled.

#
Channel
Operational

Description

Attempt to remote reboot of target node failed or throttled. (Target: Targets, DebugMessage: ActionMessage)

Fields #

NameDescription
Targets
ActionMessage

Event ID 1322: Attempt to evict target node succeeded (Target: Targets).

#
Channel
Operational

Fields #

NameDescription
Targets

Event ID 1323: Total up node check failed for evict target node action.

#
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 #

NameDescription
Targets
Threshold
UpNodes
TotalNodes
DefaultNumberOfNodesInDAG

Event ID 1324: Total up node check succeeded for evict target node action.

#
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 #

NameDescription
Targets
Threshold
UpNodes
TotalNodes
DefaultNumberOfNodesInDAG

Event ID 1325: Attempt to evict target node failed or throttled.

#
Channel
Operational

Description

Attempt to evict target node failed or throttled. (Target: Targets, DebugMessage: DebugMessage)

Fields #

NameDescription
Targets
DebugMessage

Event ID 1326: Recovering ClusDB hang by attempting to restart ClusSvc on the following (individually identified as potential culprits) servers: Targets.

#
Channel
Operational

Fields #

NameDescription
Targets

Event ID 1327: Recovering ClusDB hang by attempting to restart clussvc on all nodes (Up, Joining and Paused) in the DAG: Targets.

#
Channel
Operational

Fields #

NameDescription
Targets

Event ID 1328: Restarting an individual node was throttled (ClusDB hang recovery).

#
Channel
Operational

Description

Restarting an individual node was throttled (ClusDB hang recovery). Server: Target

Fields #

NameDescription
Target

Event ID 1329: Restarting clussvc on a node as part of restarting all nodes in the DAG was throttled (ClusDB hang recovery).

#
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 #

NameDescription
Target

Event ID 1330: Cluster database periodic cleanup failed.

#
Channel
Operational

Description

Cluster database periodic cleanup failed. (Category: Category, Error: Error)

Fields #

NameDescription
Category
Error

Event ID 1331: Cluster database periodic cleanup skipped.

#
Channel
Operational

Description

Cluster database periodic cleanup skipped. (Category: Category, Reason: Reason)

Fields #

NameDescription
Category
Reason

Event ID 1332: Cluster database periodic cleanup batch operation failed.

#
Channel
Operational

Description

Cluster database periodic cleanup batch operation failed. (Category: Category, Error: Error)

Fields #

NameDescription
Category
Error
KeyName
IsDeleteKey
BatchNumber
ItemsInBatch
TotalItemsToDelete
FilteredItemsToDelete

Event ID 1333: Cluster database periodic cleanup did not detect any stale databases or servers.

#
Channel
Operational

Event ID 1334: Cluster database periodic cleanup for key ParentKeyName completed (TotalItemsDeleted: TotalItemsDeleted, ItemType: ItemType, DurationMs: DurationMilliseconds).

#
Channel
Operational

Fields #

NameDescription
Category
ParentKeyName
TotalItemsDeleted
ItemType
TotalBatchRequests
TotalFailedBatchRequests
DurationMilliseconds

Event ID 1335: Cluster database periodic cleanup detected DatabaseCountWaitingForConfirmation stale database entries and ServerCountWaitingForConfirmation stale server entries.

#
Channel
Operational

Fields #

NameDescription
DatabaseCountWaitingForConfirmation
ServerCountWaitingForConfirmation

Event ID 1336: Cluster database periodic cleanup analyze failed.

#
Channel
Operational

Description

Cluster database periodic cleanup analyze failed. (Category: Category, Error: Error)

Fields #

NameDescription
Category
Error

Event ID 1340: Recovering ClusDB hang by attempting to restart clussvc on all nodes is blocked: GumIdState.

#
Channel
Operational

Fields #

NameDescription
GumIdState

Event ID 1381: Prereqs for offline defragmentation process of database Database completed successfully.

#
Channel
Operational

Description

Prereqs for offline defragmentation process of database Database completed successfully. It took Duration minutes to complete.

Fields #

NameDescription
Database
Duration

Event ID 1382: Prereqs for offline defragmentation process of database Database failed (it took Duration minutes to fail).

#
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 #

NameDescription
Database
Duration
PrereqsFailed
ErrorMessage

Event ID 1383: Dismount of database Database and suspending its copies (for offline defragmentation) completed successfully.

#
Channel
Operational

Description

Dismount of database Database and suspending its copies (for offline defragmentation) completed successfully. It took Duration minutes to complete.

Fields #

NameDescription
Database
Duration

Event ID 1384: Dismount of database Database or suspending its copies (for offline defragmentation) failed (it took Duration minutes to fail).

#
Channel
Operational

Description

Dismount of database Database or suspending its copies (for offline defragmentation) failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

NameDescription
Database
Duration
ErrorMessage

Event ID 1385: EDB file defragmentation stage and integrity check of database Database completed successfully.

#
Channel
Operational

Description

EDB file defragmentation stage and integrity check of database Database completed successfully. It took Duration minutes to complete.

Fields #

NameDescription
Database
Duration

Event ID 1386: EDB file defragmentation stage and integrity check of database Database failed (it took Duration minutes to fail).

#
Channel
Operational

Description

EDB file defragmentation stage and integrity check of database Database failed (it took Duration minutes to fail). Error: ErrorMessage

Fields #

NameDescription
Database
Duration
ErrorMessage

Event ID 1387: Final stage (mount database and reseeding copies) of offline defragmentation of database Database completed successfully.

#
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 #

NameDescription
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).

#
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 #

NameDescription
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.

#
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 #

NameDescription
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).

#
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 #

NameDescription
Database
Duration
ErrorMessage

Event ID 1400: AD configuration is not available : Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 1401: AD configuration refresh took excessive time : TotalDuration.

#
Channel
Operational

Fields #

NameDescription
TotalDuration

Event ID 1402: AD configuration refresh failed : Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 1403: Process ProcessName is using MeasuredConsumption MB of memory.

#
Channel
Operational

Description

Process ProcessName is using MeasuredConsumption MB of memory. Warning threshold is WarningLimit. Error limit is ErrorLimit. Memory type is ResourceClass.

Fields #

NameDescription
ProcessName
MeasuredConsumption
WarningLimit
ErrorLimit
ResourceClass

Event ID 1404: Process ProcessName is using MeasuredConsumption handles.

#
Channel
Operational

Description

Process ProcessName is using MeasuredConsumption handles. Warning threshold is WarningLimit. Error limit is ErrorLimit. Handle type is ResourceClass.

Fields #

NameDescription
ProcessName
MeasuredConsumption
WarningLimit
ErrorLimit
ResourceClass

Event ID 1405: Process ProcessName is using MeasuredConsumption threads.

#
Channel
Operational

Description

Process ProcessName is using MeasuredConsumption threads. Warning threshold is WarningLimit. Error limit is ErrorLimit.

Fields #

NameDescription
ProcessName
MeasuredConsumption
WarningLimit
ErrorLimit
ResourceClass

Event ID 1406: SetServerComponentState was run: Server=Server Requester=Requester Component=Component State=State CmdType=CmdType.

#
Channel
Operational

Fields #

NameDescription
Server
Requester
Component
State
CmdType

Event ID 1500: Database Health Tracker component encountered an error: Message.

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

Event ID 1501: Database Health Tracker is now running as the Primary role.

#
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.

#
Channel
Monitoring

Fields #

NameDescription
Role

Event ID 1503: Database Health Tracker, running as the Primary role, failed to persist the health information.

#
Channel
Monitoring

Description

Database Health Tracker, running as the Primary role, failed to persist the health information. Error: Message

Fields #

NameDescription
Message
StackTrace

Event ID 1504: Database Health Tracker, running as a Secondary role, failed to persist the health information.

#
Channel
Monitoring

Description

Database Health Tracker, running as a Secondary role, failed to persist the health information. Error: Message

Fields #

NameDescription
Message
StackTrace

Event ID 1505: Database Health Tracker failed to initialize the health information from the persisted file.

#
Channel
Monitoring

Description

Database Health Tracker failed to initialize the health information from the persisted file. Error: Message

Fields #

NameDescription
Message
StackTrace

Event ID 1506: Remote operation 'OperationName' timed out to one or more servers after 'Timeout'.

#
Channel
Monitoring

Fields #

NameDescription
OperationName
Timeout

Event ID 1507: Remote operation 'OperationName' failed to one or more servers.

#
Channel
Monitoring

Description

Remote operation 'OperationName' failed to one or more servers. Error: Message

Fields #

NameDescription
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.

#
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 #

NameDescription
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...

#
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...

#
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 #

NameDescription
OtherUpdateTimeUtc
LocalUpdateTimeUtc

Event ID 1511: Secondary role received an older health information table of update time 'OtherUpdateTimeUtc' from the Primary server.

#
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 #

NameDescription
OtherUpdateTimeUtc
LocalUpdateTimeUtc

Event ID 1512: The Monitoring WCF service failed to register its endpoint.

#
Channel
Monitoring

Description

The Monitoring WCF service failed to register its endpoint. Error: Message

Fields #

NameDescription
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'.

#
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 #

NameDescription
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.

#
Channel
Monitoring

Fields #

NameDescription
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.

#
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 #

NameDescription
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.

#
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 #

NameDescription
LastUpdateTimeUtc
LastUpdateTimeDiff
UpdateThreshold

Event ID 1517: Failover sequence number for database guid DatabaseGuid is not based on time due to time skew.

#
Channel
Operational

Description

Failover sequence number for database guid DatabaseGuid is not based on time due to time skew. It is now FailoverSequenceNumber.

Fields #

NameDescription
DatabaseGuid
FailoverSequenceNumber

Event ID 1518: The Monitoring WCF service started.

#
Channel
Monitoring

Description

The Monitoring WCF service started. Endpoint(s): Endpoints

Fields #

NameDescription
Endpoints

Event ID 1600: Database potential redundancy health check passed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
HealthyPassiveCopiesCount
TotalPassiveCopiesCount
TotalPassiveCopiesRequired
ErrorMessage
DatabaseGuid
IsSuppressed

Event ID 1601: Database potential redundancy health check failed.

#
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 #

NameDescription
DatabaseName
HealthyCopiesCount
HealthyPassiveCopiesCount
TotalPassiveCopiesCount
TotalPassiveCopiesRequired
ErrorMessage
DatabaseGuid

Event ID 1602: Databases on server Message have passed the check for potential database redundancy issue.

#
Channel
Monitoring

Fields #

NameDescription
Message

Event ID 1603: Some databases on server LocalMachineName will potentially have insufficient data redundancy, which has been caused by server RemoteMachineName.

#
Channel
Monitoring

Description

Some databases on server LocalMachineName will potentially have insufficient data redundancy, which has been caused by server RemoteMachineName. Databases: ErrorMessage

Fields #

NameDescription
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.

#
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 #

NameDescription
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...

#
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 #

NameDescription
Message1
Message2

Event ID 1606: FailedCopies Database Copies out of NumberOfCopies have a growing Log Copy queue on ServerName.

#
Channel
Monitoring

Fields #

NameDescription
FailedCopies
NumberOfCopies
ServerName

Event ID 2000: AvailabilitySensorError component encountered an error: Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 2001: Database scanning during passive replay is disabled on 'DatabaseName'.

#
Channel
Operational

Description

Database scanning during passive replay is disabled on 'DatabaseName'. Explanation: Message1.

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 2002: Database scanning during passive replay is enabled on 'DatabaseName'.

#
Channel
Operational

Description

Database scanning during passive replay is enabled on 'DatabaseName'. Explanation: Message1.

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 2003: The log copier for database 'DatabaseName' found divergence at generation DivergedGeneration.

#
Channel
Operational

Description

The log copier for database 'DatabaseName' found divergence at generation DivergedGeneration. The active server was ActiveServer.

Fields #

NameDescription
DatabaseName
DatabaseGuid
DivergedGeneration
ActiveServer

Event ID 2004: The log copier for database 'DatabaseName' could not verify divergence at generation DivergedGeneration.

#
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 #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer

Event ID 2006: The ESE LogConsumer for database 'DatabaseName' failed during termination: Message1.

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseName
ServerName
DatabaseGuid
Message1

Event ID 2007: BlockMode terminated for database 'DatabaseName'.

#
Channel
BlockReplication

Description

BlockMode terminated for database 'DatabaseName'. CurrentGen=CurrentGen HeldGen=HeldGen

Fields #

NameDescription
DatabaseName
DatabaseGuid
CurrentGen
HeldGen

Event ID 2008: ACLL completed with minor loss due to LazyCommit while performing switchover on shutdown for database 'DatabaseName'.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 2009: Prior to mounting database 'DatabaseName' possible loss due LazyCommit was recorded.

#
Channel
Operational

Description

Prior to mounting database 'DatabaseName' possible loss due LazyCommit was recorded. Loss window: Start=LossStart End=LossEnd

Fields #

NameDescription
DatabaseGuid
DatabaseName
LossStart
LossEnd
ResultingStart
ResultingEnd

Event ID 2010: Prior to mounting database 'DatabaseName' possible loss due LazyCommit could not be determined.

#
Channel
Operational

Description

Prior to mounting database 'DatabaseName' possible loss due LazyCommit could not be determined. Error=Message

Fields #

NameDescription
DatabaseGuid
DatabaseName
Message

Event ID 2011: After mounting database 'DatabaseName' redelivery was performed for possible loss due LazyCommit.

#
Channel
Operational

Description

After mounting database 'DatabaseName' redelivery was performed for possible loss due LazyCommit. Loss window: Start=LossStart End=LossEnd

Fields #

NameDescription
DatabaseGuid
DatabaseName
LossStart
LossEnd
LossString

Event ID 2012: After mounting database 'DatabaseName' possible loss due LazyCommit could not be processed.

#
Channel
Operational

Description

After mounting database 'DatabaseName' possible loss due LazyCommit could not be processed. Error=Message

Fields #

NameDescription
DatabaseGuid
DatabaseName
Message

Event ID 2013: ACLL failed for database 'DatabaseName'.

#
Channel
Operational

Description

ACLL failed for database 'DatabaseName'. PAM active server = ExpectedActiveServer but local copy has active = ActiveServerBeingUsed.

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseName
DatabaseGuid
ActiveServer

Event ID 2015: Sent CAFE notification to endpoint Endpoint (json: 'JsonPayload').

#
Channel
Operational

Description

Sent CAFE notification to endpoint Endpoint (json: 'JsonPayload'). FEServer: FEServer. Result: Result.

Fields #

NameDescription
Endpoint
JsonPayload
FEServer
Result

Event ID 2016: Failed CAFE notification to endpoint Endpoint (json: 'JsonPayload').

#
Channel
Operational

Description

Failed CAFE notification to endpoint Endpoint (json: 'JsonPayload'). FEServer: FEServer. Result: Result. FailureMessage: FailureMessage.

Fields #

NameDescription
Endpoint
JsonPayload
FEServer
Result
FailureMessage

Event ID 2017: InvokeWithTimeout perf: MaxDelay MaxDelayInUsec uSec.

#
Channel
Operational

Description

InvokeWithTimeout perf: MaxDelay MaxDelayInUsec uSec. MaxConcurrentWorkers = MaxConcurrentWorkers. CountInWorstBucket = CountInWorstBucket. WorstBucket = DelayForWorstBucket uSec. Measured over MeasurementWindow.

Fields #

NameDescription
MaxDelayInUsec
MaxConcurrentWorkers
MeasurementWindow
CountInWorstBucket
DelayForWorstBucket
OtherBuckets

Event ID 2018: ThreadPool: CurrentWorkers CurrentWorkerThreads.

#
Channel
Operational

Description

ThreadPool: CurrentWorkers CurrentWorkerThreads. MinWorkers MinWorkerThreads. MaxWorkers MaxWorkerThreads. CurrentIOThreads CurrentIOThreads. MinIO MinIOThreads. MaxIO MaxIOThreads.

Fields #

NameDescription
CurrentWorkerThreads
MinWorkerThreads
MaxWorkerThreads
CurrentIOThreads
MinIOThreads
MaxIOThreads
ProcessThreadCount

Event ID 2019: SafetyNet request 'StoreValueName' for database 'DatabaseName' failed to deserialize: Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
StoreValueName
Error

Event ID 2020: SafetyNet request 'StoreValueName' for database 'DatabaseName' has expired.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
StoreValueName

Event ID 2021: SafetyNet for database 'DatabaseName' failed due to a serialization error: Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 2022: The local copy of database 'DatabaseName' was marked Disconnected but BlockMode is active.

#
Channel
Operational

Description

The local copy of database 'DatabaseName' was marked Disconnected but BlockMode is active. Resetting to Healthy.

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 2023: The local copy of database 'DatabaseName' has entered BlockMode Replication.

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseGuid
DatabaseName

Event ID 2024: Passive BlockMode for database 'DatabaseName' failed to receive a response from ActiveServer after TimeoutInterval.

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
TimeoutInterval

Event ID 2025: Passive BlockMode for database 'DatabaseName' failed to ping active ActiveServer : Error.

#
Channel
BlockReplication

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Error

Event ID 2026: Passive BlockMode for database 'DatabaseName' failed to initialize.

#
Channel
BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to initialize. Active was ActiveServer. Error: Error.

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Error

Event ID 2027: Passive BlockMode for database 'DatabaseName' failed to read data.

#
Channel
BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed to read data. Active was ActiveServer. Error: Error.

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Error

Event ID 2028: Passive BlockMode for database 'DatabaseName' failed due to a local consumer problem.

#
Channel
BlockReplication

Description

Passive BlockMode for database 'DatabaseName' failed due to a local consumer problem. Active was ActiveServer. Error: Error.

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Error

Event ID 2029: FileIOErrorOnSource for database 'DatabaseName': Corrupt: TreatedAsCorrupt.

#
Channel
Operational

Description

FileIOErrorOnSource for database 'DatabaseName': Corrupt: TreatedAsCorrupt. Err: Exception

Fields #

NameDescription
DatabaseGuid
DatabaseName
TreatedAsCorrupt
Exception
PartnerNodeName

Event ID 2030: The copy of 'DatabaseName' has a loss window from LossStart to LossEnd.

#
Channel
Operational

Description

The copy of 'DatabaseName' has a loss window from LossStart to LossEnd. No redelivery request was found.

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
LossStart
LossEnd
RedeliveryKey
RedeliveryRecord

Event ID 2032: LossVerification during IncrementalReseed failed: Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 2033: SetBlockFlags failed during failure item processing for database 'DatabaseName' : Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 2034: Incremental Reseed failed for database 'DatabaseName' because DivergenceInLogs logs of divergence exist but the limit is MaxDivergenceAllowed logs.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
LogsToCopy
MaxLogsAllowed

Event ID 2036: MonitoredDatabase for database 'DatabaseName' is starting.

#
Channel
Operational

Description

MonitoredDatabase for database 'DatabaseName' is starting. IsActive=IsActive.

Fields #

NameDescription
DatabaseGuid
DatabaseName
IsActive

Event ID 2037: MonitoredDatabase for database 'DatabaseName' has started.

#
Channel
Operational

Description

MonitoredDatabase for database 'DatabaseName' has started. IsActive=IsActive. Duration=Duration. EOL=EndOfLogGeneration EndOfLogUtc

Fields #

NameDescription
DatabaseGuid
DatabaseName
IsActive
Duration
EndOfLogGeneration
EndOfLogUtc

Event ID 2038: The active copy for database 'DatabaseGuid' could not be determined: Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Error
Stack

Event ID 2039: The configuration for the local copy of database 'DatabaseName' could not be determined: Error.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error

Event ID 2040: The active copy for database 'DatabaseName' is ActiveCopy.

#
Channel
Debug

Description

The active copy for database 'DatabaseName' is ActiveCopy. It was determined by Authority at DeterminationUTC UTC

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveCopy
Authority
DeterminationUTC

Event ID 2041: A network error happened at LocationTag: Error.

#
Channel
Debug

Fields #

NameDescription
Error
LocationTag
ObjectName
ConnectionWasInScavenge

Event ID 2042: A network timeout happened at LocationTag: Error.

#
Channel
Debug

Fields #

NameDescription
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.

#
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 #

NameDescription
DatabaseGuid
DatabaseName
SecondaryEdbFilePath
SeedError
PreviousStartupMessage

Event ID 2050: Suspend log replay requested for database guid=DatabaseGuid, reason='SuspendReason'.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
SuspendReason
SuspendReasonCode

Event ID 2051: Suspend log replay for database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

Event ID 2052: Suspend log replay for database guid=DatabaseGuid failed: Message.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

Event ID 2053: Resume log replay requested for database guid=DatabaseGuid.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

Event ID 2054: Resume log replay for database guid=DatabaseGuid succeeded.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid

Event ID 2055: Resume log replay for database guid=DatabaseGuid failed: Message.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
Message

Event ID 2056: RedundancySensorError component encountered an error: Message.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 2057: Loss redelivery after incremental reseed for database 'DatabaseName' failed: Error.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
LossStart
LossEnd

Event ID 2059: The DAG is configured with ActivityState 'DagActivityState' so the MaxPreferredDatabases check in BCS is treated like MaxActiveDatabases.

#
Channel
Operational

Fields #

NameDescription
DagActivityState

Event ID 2060: The passive copy of 'DatabaseName' has stopped with last log copied at LastLogCopied and inspected at LastLogInspected.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
LastLogCopied
LastLogInspected

Event ID 2061: The LogCopier for 'DatabaseName' halted communication after ACLL.

#
Channel
Debug

Description

The LogCopier for 'DatabaseName' halted communication after ACLL. FileMode duration: FileModeDuration BlockMode duration: BlockModeDuration.

Fields #

NameDescription
DatabaseGuid
DatabaseName
FileModeDuration
BlockModeDuration

Event ID 2062: The active copy for database DatabaseGuid ignored CircularLogging because there are CurrentCopyCount copies but ExpectedCopyCount are expected.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
CurrentCopyCount
ExpectedCopyCount

Event ID 2063: Move back to server 'TargetServerName' completed.

#
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 #

NameDescription
TargetServerName
NumberOfDatabasesProcessed
NumberOfBatches
ElapsedTime
NumberOfDatabasesSkipped

Event ID 2064: Move back to server 'TargetServerName' timed out after ElapsedTime.

#
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 #

NameDescription
TargetServerName
NumberOfDatabasesProcessed
NumberOfBatches
ElapsedTime
NumberOfDatabasesSkipped

Event ID 2065: Microsoft Exchange Server Locator Service failed to find active server for database 'Database'.

#
Channel
Debug

Description

Microsoft Exchange Server Locator Service failed to find active server for database 'Database'. Error: Error

Fields #

NameDescription
Database
Error

Event ID 2066: Microsoft Exchange Server Locator Service failed to find active servers for the database availability group.

#
Channel
Operational

Description

Microsoft Exchange Server Locator Service failed to find active servers for the database availability group. Error: Error

Fields #

NameDescription
Error

Event ID 2070: Active Manager configuration refresh failed.

#
Channel
Operational

Description

Active Manager configuration refresh failed. Error: ErrorMessage

Fields #

NameDescription
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.

#
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 #

NameDescription
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...

#
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 #

NameDescription
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.

#
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 #

NameDescription
Provider
TriggerEvent

Event ID 2074: Loose truncation on database DatabaseGuid was performed due to low space.

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseGuid
FreeSpaceInMB
MinDiskFreeSpaceThresholdInMB
NormalTruncationGen
ProtectedCopiesTruncationGen
LooseTruncationGenUsed
MinGenRequiredByActive
CircularLogging

Event ID 2075: Truncation on database DatabaseGuid is being performed.

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseGuid
MinGenFromAllPassives
MinGenFromProtectedPassives
TruncationGenUsed
MinGenRequiredByActive
CircularLogging

Event ID 2076: Loose truncation on database DatabaseGuid was performed due to excess log buildup.

#
Channel
TruncationDebug

Fields #

NameDescription
DatabaseGuid
NormalTruncationGen
ProtectedCopiesTruncationGen
LooseTruncationGenUsed
MinGenRequiredByActive
CircularLogging

Event ID 2077: Microsoft Exchange Server Locator Service Logger failed to commit log information.

#
Channel
Monitoring

Description

Microsoft Exchange Server Locator Service Logger failed to commit log information. Error: Error

Fields #

NameDescription
Error

Event ID 2078: Rebalance for CPU found work.

#
Channel
Debug

Fields #

NameDescription
SourceServers
TargetServers
IgnoredServers

Event ID 2079: Rebalance for CPU ignored database 'DatabaseName' because: Reason.

#
Channel
Debug

Fields #

NameDescription
DatabaseName
Reason

Event ID 2080: Rebalance for CPU moved database 'DatabaseName' from OldActive to NewActive.

#
Channel
Debug

Fields #

NameDescription
DatabaseName
OldActive
NewActive

Event ID 2081: Rebalance for CPU timed out after Timeout.

#
Channel
Debug

Fields #

NameDescription
Timeout

Event ID 2082: Forced mount for database 'DatabaseName' failed.

#
Channel
Operational

Description

Forced mount for database 'DatabaseName' failed. Error: Error

Fields #

NameDescription
DatabaseGuid
DatabaseName
Error
AmFlags
StoreFlags

Event ID 2083: Forced mount for database 'DatabaseName' is being attempted.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
AmFlags
StoreFlags

Event ID 2084: Forced mount for database 'DatabaseName' checked server ServerChecked to determine EDB existence = EDBFound.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ServerChecked
EDBFound

Event ID 2090: Database move supporting operations performance details.

#
Channel
Operational

Fields #

NameDescription
UniqueId
DatabaseName
DatabaseGuid
MoveAllOrNoneWaitElapsedTime
DismountElapsedTime
UpdateAdPropertiesElapsedTime
CheckIfMoveApplicableElapsedTime
MoveSuppressionCheckElapsedTime

Event ID 2091: Global truncation for 'DatabaseName' on active ActiveServer took Duration.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Duration
GenerationSent

Event ID 2092: LogCopier for database 'DatabaseName' connected to active ActiveServer detected poor performance of Thruput bytes/sec.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
ActiveServer
Thruput
MinThruput
DetectionWindow

Event ID 2093: TcpStats report from Context=Context.

#
Channel
Operational

Description

TcpStats report from Context=Context. Client=Client. Server=Server.

Fields #

NameDescription
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.

#
Channel
Operational

Description

TcpStats internal failure. Context=Context. Error=Error

Fields #

NameDescription
Context
Error

Event ID 2095: LogCopyServer for database 'DatabaseName' sending data to passive PassiveServer detected poor performance of Thruput bytes/sec.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
PassiveServer
Thruput
MinThruput
DetectionWindow

Event ID 2096: ListMDBStatus for server Server failed while hosting actives=HostingActives with exception=Exception.

#
Channel
Operational

Fields #

NameDescription
Server
HostingActives
Exception

Event ID 2097: Local copy of database 'DatabaseName' was hung for restartInterval='RestartInterval' prepareToStopInterval='PrepareToStopInterval'.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
RestartInterval
PrepareToStopInterval
HangLimit
WasDisconnected
RecoveryWillBeAttempted
RequestRestartStack

Event ID 2098: Log 'FileName' failed to open after 'DurationOfOpen' with error Exception.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
FileName
DurationOfOpen
Exception

Event ID 2099: Dismount database 'DatabaseName' attempted from CallerContext.

#
Channel
Operational

Description

Dismount database 'DatabaseName' attempted from CallerContext. Success=Success.

Fields #

NameDescription
DatabaseGuid
DatabaseName
CallerContext
Success
ServerFqdn
Flags
Duration
Error

Event ID 2100: The Message1 has been Message2.

#
Channel
Operational

Fields #

NameDescription
Message1
Message2

Event ID 2101: The callback to update Network Throttling configuration failed with: Message1.

#
Channel
Operational

Description

The callback to update Network Throttling configuration failed with: Message1. Stack Trace: Message2

Fields #

NameDescription
Message1
Message2

Event ID 2102: The IsPrimaryTable operation from Azure storage table (IsPrimary:IsPrimaryTable) failed with: Message.

#
Channel
Operational

Description

The IsPrimaryTable operation from Azure storage table (IsPrimary:IsPrimaryTable) failed with: Message. Stack Trace: StackTrace

Fields #

NameDescription
IsPrimaryTable
Operation
Message
StackTrace

Event ID 2103: The operation to retrieve the storage configuration from Torus Secret failed with: Message1.

#
Channel
Operational

Description

The operation to retrieve the storage configuration from Torus Secret failed with: Message1. Stack Trace: Message2

Fields #

NameDescription
Message1
Message2

Event ID 2104: Operation:Operation; SourceLocation:SourceLocation; DestinationLocation:DestinationLocation; OperationMessage:Message.

#
Channel
Monitoring

Fields #

NameDescription
Operation
SourceLocation
DestinationLocation
Message

Event ID 2130: Restart RI for database 'DatabaseName' requested.

#
Channel
Debug

Description

Restart RI for database 'DatabaseName' requested. Requestor=Requestor. Reason=Reason.

Fields #

NameDescription
DatabaseGuid
DatabaseName
Requestor
Reason
AdminVisible
PrepareToStop
Context
Exception
ChangeHintsReason
IsFirstRequest
ConfigType
StackTrace

Event ID 2131: RI for database 'DatabaseName' has been selected for restart.

#
Channel
Debug

Description

RI for database 'DatabaseName' has been selected for restart. Reason=Reason, ReasonMessage: ReasonMessage

Fields #

NameDescription
DatabaseGuid
DatabaseName
Reason
ConfigType
ConfigChanged
ConfigChangeFlags
ForceRestart
ReasonMessage

Event ID 2132: Component 'ComponentName' instance 'InstanceName' stopped after 'StopDuration'.

#
Channel
Debug

Fields #

NameDescription
ComponentName
InstanceName
StopDuration
PrepareToStopTime
StartOfStopTime
EndOfStopTime

Event ID 2133: Registry value EnableCounterForIoctl could not be set.

#
Channel
Monitoring

Description

Registry value EnableCounterForIoctl could not be set. This is required for DiskLatencySensor.

Fields #

NameDescription
Message
StackTrace

Event ID 2134: There was an error reading disk performance data.

#
Channel
Monitoring

Fields #

NameDescription
Message
StackTrace

Event ID 2135: Restart RI for database 'DatabaseName' has been deferred.

#
Channel
Debug

Description

Restart RI for database 'DatabaseName' has been deferred. Reason=Reason.

Fields #

NameDescription
DatabaseGuid
DatabaseName
Reason

Event ID 2136: ReplayDiagnosticsHandler failed to start: Message.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 2137: Lossy ACLL for database 'DatabaseName' contacted SourceNode to check for additional log data.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Description

Lossy ACLL for database 'DatabaseName' used BlockMode generation Generation. For remote ACLL=IsRemote.

Fields #

NameDescription
DatabaseGuid
DatabaseName
Generation
LastPos
LastUtc
IsRemote
Error

Event ID 2140: The attempt to truncate local logs for database 'DatabaseName' failed: Exception.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Exception
HRESULT
FailureTag

Event ID 2141: The ServiceName service is starting.

#
Channel
Operational

Description

The ServiceName service is starting. Extra time requested: AdditionalTime. BackgroundStart=BackgroundStartup

Fields #

NameDescription
ServiceName
AdditionalTime
BackgroundStartup

Event ID 2142: The Message service is stopping without waiting for an incomplete startup to finish.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 2143: An override was used to configure the copy of 'DatabaseName' as Role.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Role
StartUtc
Duration
FqdnOfActiveCopy

Event ID 2144: Probing file 'FileName' failed.

#
Channel
Operational

Description

Probing file 'FileName' failed. Win32=Win32Err. Err=Error

Fields #

NameDescription
DatabaseGuid
DatabaseName
FileName
Win32Err
Error

Event ID 2145: ACLL driven dismount database 'DatabaseName' succeeded after Duration.

#
Channel
Operational

Description

ACLL driven dismount database 'DatabaseName' succeeded after Duration. DurableDismount=DurableDismountObtained.

Fields #

NameDescription
DatabaseGuid
DatabaseName
DurableDismountObtained
Duration

Event ID 2146: ACLL driven dismount database 'DatabaseName' failed after Duration.

#
Channel
Operational

Description

ACLL driven dismount database 'DatabaseName' failed after Duration. Error=Error

Fields #

NameDescription
DatabaseGuid
DatabaseName
Duration
Error

Event ID 2147: ACLL driven dismount database 'DatabaseName' failed due to timeout after Duration.

#
Channel
Operational

Fields #

NameDescription
DatabaseGuid
DatabaseName
Duration

Event ID 2148: ACLL probe of the EDB for 'DatabaseName' took DurationInMicrosec microseconds.

#
Channel
Debug

Description

ACLL probe of the EDB for 'DatabaseName' took DurationInMicrosec microseconds. DismountNeeded=DismountNeeded

Fields #

NameDescription
DatabaseGuid
DatabaseName
DurationInMicrosec
DismountNeeded

Event ID 2149: ProcessAffinity for ServiceName was set successfully=SuccessfullySet.

#
Channel
Operational

Fields #

NameDescription
ServiceName
SuccessfullySet
NumProcessors
AffinityMask
PriorityClass
MaxCpu
Error

Event ID 2500: Attempted to upgrade FPGA image from version RpdVersionOnFlash to RpdVersionOnDisk.

#
Channel
Operational

Description

Attempted to upgrade FPGA image from version RpdVersionOnFlash to RpdVersionOnDisk. The upgrade Status. Timing Sequence: TimingSequence.

Fields #

NameDescription
TimingSequence
RpdVersionOnFlash
RpdVersionOnDisk
Status

Event ID 2501: An attempt to initialize the FPGA was abandoned because the service is stopping.

#
Channel
Operational

Description

An attempt to initialize the FPGA was abandoned because the service is stopping. Timing Sequence: TimingSequence.

Fields #

NameDescription
TimingSequence

Event ID 2502: An exception was thrown while trying to perform an operation on the FPGA.

#
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 #

NameDescription
ErrorCode
Message

Event ID 2503: Operation failed with error: ErrorCode.

#
Channel
Operational

Fields #

NameDescription
Operation
ErrorCode

Event ID 2504: FpgaCoreLib.

#
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'.

#
Channel
Operational

Description

Microsoft Exchange Server 'RequestingMachineName' initiated bug check for server 'TargetMachineName'. (Source: Source, Identity: Identity)

Fields #

NameDescription
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'.

#
Channel
Operational

Description

Triggered Active manager configuration refresh since PAM change notification received from server 'ReportingServer' (ReportingServerPrevRole: 'ReportingServerPreviousAmRole', LocalServerPamView: 'LocalServerViewOfPam', LocalServerAmRole: 'LocalServerAmRole').

Fields #

NameDescription
ReportingServer
ReportingServerPreviousAmRole
LocalServerViewOfPam
LocalServerAmRole

Event ID 3002: Received PAM change notification received from server 'ReportingServer' but skipped config refresh.

#
Channel
Operational

Description

Received PAM change notification received from server 'ReportingServer' but skipped config refresh (ReportingServerPrevRole: 'ReportingServerPreviousAmRole', LocalServerPamView: 'LocalServerViewOfPam', LocalServerAmRole: 'LocalServerAmRole', IsConfigManagerValid: 'IsConfigManagerValid').

Fields #

NameDescription
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.

#
Channel
Seeding

Fields #

NameDescription
VolumeId
DBNames

Event ID 3004: The volume 'VolumeId' was forcefully formatted.

#
Channel
Seeding

Fields #

NameDescription
VolumeId

Event ID 3005: Message.

#
Channel
Seeding

Fields #

NameDescription
Message

Event ID 3006: Found an empty encrypted NTFS spare : VolumeId.

#
Channel
Seeding

Fields #

NameDescription
VolumeId

Event ID 3007: Message.

#
Channel
Seeding

Fields #

NameDescription
Message

Event ID 3008: Found a potential ReFS volume for force dismount : VolumeId.

#
Channel
Seeding

Description

Found a potential ReFS volume for force dismount : VolumeId. Now checking to see if databases on volume have enough redundancy.

Fields #

NameDescription
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 '%...

#
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 #

NameDescription
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...

#
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 #

NameDescription
ServerName
Threshold

Event ID 3013: Avg FFB on DatabaseName was AvgLatencyInMsec mSec.

#
Channel
Debug

Fields #

NameDescription
DatabaseGuid
DatabaseName
MaxLatencyInMsec
MinLatencyInMsec
AvgLatencyInMsec
TotalFlushes
MeasurementWindow
Buckets

Event ID 3014: Full reseed for database 'DatabaseName\MachineName' finished.

#
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 #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 3016: Disk monitor component [Message] Succeed.

#
Channel
Operational

Fields #

NameDescription
Message

Event ID 3017: Disk monitor component [Message] Failed: StackTrace.

#
Channel
Operational

Fields #

NameDescription
Message
StackTrace

Event ID 3018: Disk [Message1]: partition access paths: Message2, the expected protected status should be: Message3.

#
Channel
Operational

Fields #

NameDescription
Message1
Message2
Message3

Event ID 3019: FQDN resolution failed for server ServerName with error : Message.

#
Channel
Operational

Description

FQDN resolution failed for server ServerName with error : Message. The following stacktrace provides the call chain: StackTrace

Fields #

NameDescription
ServerName
Message
StackTrace

Event ID 3020: CallSite encountered SerializationException with a message of : ExceptionMessage.

#
Channel
Debug

Fields #

NameDescription
CallSite
ExceptionMessage

Event ID 9000: The Disk Reclaimer used-only encrypted volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
Channel
Operational

Fields #

NameDescription
VolumeName
MountedFolder

Event ID 9001: The Disk Reclaimer failed to used-only encrypt volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
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 #

NameDescription
VolumeName
MountedFolder
Exception
ReturnValue
ErrorMessage

Event ID 9002: The Disk Reclaimer couldn't find any empty spare volumes to encrypt.

#
Channel
Operational

Event ID 9003: The Disk Reclaimer found 'VolumeCount' candidates for Encryption.

#
Channel
Operational

Fields #

NameDescription
VolumeCount

Event ID 9004: The Disk Reclaimer successfully used-only encrypted 'SuccessCount' Empty volumes and failed encrypting 'FailureCount' Empty volumes.

#
Channel
Operational

Fields #

NameDescription
SuccessCount
FailureCount

Event ID 9005: Unable to get Win32_EncryptableVolume object for volume : 'SuccessCount' due to error : 'FailureCount'.

#
Channel
Operational

Fields #

NameDescription
SuccessCount
FailureCount

Event ID 9006: The Disk Reclaimer skipped encrypting empty Win8 volumes.

#
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.

#
Channel
Operational

Description

Volume 'VolumeName' is mounted on a virtual disk. So not getting bitlocker status.

Fields #

NameDescription
VolumeName

Event ID 9008: The Disk Reclaimer skipped calling Bitlocker Maintenance as the config is disabled.

#
Channel
Operational

Event ID 9009: he Disk Reclaimer failed to start full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
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 #

NameDescription
VolumeName
MountedFolder
Exception
ReturnValue
ErrorMessage

Event ID 9010: The Disk Reclaimer started full volume encryption for volume 'VolumeName' mounted at 'MountedFolder' as a spare.

#
Channel
Operational

Fields #

NameDescription
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.

#
Channel
Operational

Fields #

NameDescription
SuccessCount
FailureCount

Event ID 9014: The Disk Reclaimer skipped encrypting empty Win7 volumes.

#
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.

#
Channel
Operational

Fields #

NameDescription
VolumeName
EncryptionPercentage

Event ID 9017: The Disk Reclaimer is calling Win7 encryption method in BitlockerHelper.

#
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.

#
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'.

#
Channel
Operational

Description

Bitlocker Encryption failed for mountpoint 'MountPoint' volume 'VolumeName' due to error 'Error'. Corresponding Bitlocker event 'EventXML'.

Fields #

NameDescription
VolumeName
Error
EventXML
MountPoint