Microsoft-Windows-Application Server-Applications

481 events across 3 channels

Event ID	Title	Channel
100	TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
101	TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, …	Analytic
102	TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
103	TrackRecord = ActivityStateRecord, InstanceID = %1, RecordNumber=%2, …	Analytic
104	TrackRecord = ActivityScheduledRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
105	TrackRecord = FaultPropagationRecord, InstanceID=.	Analytic
106	TrackRecord = CancelRequestedRecord, InstanceID=.	Analytic
107	TrackRecord = BookmarkResumptionRecord, InstanceID=.	Analytic
108	TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, …	Analytic
110	TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, …	Analytic
111	TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, …	Analytic
112	TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = …	Analytic
113	TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = …	Analytic
114	TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
115	TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
116	TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = …	Analytic
117	TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = …	Analytic
118	TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, …	Analytic
119	TrackRecord= WorkflowInstanceUpdatedRecord, InstanceID = %1, RecordNumber = %2, …	Analytic
131	Pool allocating %1 Bytes.	Debug
132	BufferPool of size %1, changing quota by %2.	Debug
133	IO Thread scheduler callback invoked.	Debug
134	IO Thread scheduler callback invoked.	Debug
201	The Dispatcher invoked 'AfterReceiveReply' on a ClientMessageInspector of type …	Debug
202	The Dispatcher invoked 'BeforeSendRequest' on a ClientMessageInspector of type …	Analytic
203	The Dispatcher invoked 'AfterCall' on a ClientParameterInspector of type '.	Analytic
204	The Dispatcher invoked 'BeforeCall' on a ClientParameterInspector of type '.	Analytic
205	An OperationInvoker invoked the '.	Analytic
206	The Dispatcher invoked an ErrorHandler of type '.	Analytic
207	The Dispatcher invoked a FaultProvider of type '.	Analytic
208	The Dispatcher invoked 'AfterReceiveReply' on a MessageInspector of type '.	Analytic
209	The Dispatcher invoked 'BeforeSendRequest' on a MessageInspector of type '.	Analytic
210	The '.	Analytic
211	The Dispatcher invoked 'AfterCall' on a ParameterInspector of type '.	Analytic
212	The Dispatcher invoked 'BeforeCall' on a ParameterInspector of type '.	Analytic
213	ServiceHost started: '.	Analytic
214	An OperationInvoker completed the call to the '.	Analytic
215	The transport received a message from '.	Analytic
216	The transport sent a message to '.	Analytic
217	The Client is executing Action '.	Debug
218	The Client completed executing Action '.	Analytic
219	There was an unhandled exception of type '.	Analytic
220	The Dispatcher sent a message to the transport.	Analytic
221	The Dispatcher received a message from the transport.	Analytic
222	The '.	Analytic
223	The '.	Analytic
224	The '.	Analytic
225	Calculated correlation key '.	Analytic
226	%1 idle services out of total %2 activated services closed.	Analytic
301	Name:'.	Analytic
302	Name:'.	Analytic
303	Name:'.	Analytic
401	Activity boundary.	Analytic
402	Activity boundary.	Analytic
403	Activity boundary.	Analytic
404	Activity boundary.	Analytic
440	Activity boundary.	Analytic
441	Activity boundary.	Analytic
451		Analytic
452		Analytic
499	Transfer event emitted.	Analytic
501	Begin compilation	Debug
502	End compilation	Debug
503	ServiceHostFactory begin creation	Debug
504	ServiceHostFactory end creation	Debug
505	Begin CreateServiceHost	Debug
506	End CreateServiceHost	Debug
507	HostedTransportConfigurationManager begin configuration initialization	Debug
508	HostedTransportConfigurationManager end configuration initialization	Debug
509	ServiceHost Open started.	Analytic
510	ServiceHost Open completed.	Analytic
513	Received request with virtual path '.	Debug
514	WebHostRequest stop.	Debug
601	Processed ServiceActivation Element Relative Address:'.	Debug
602	Incoming request matches a ServiceActivation element with address '.	Debug
603	Incoming request matches a WCF Service defined in Asp.	Debug
604	A new Asp.	Debug
605	IncrementBusyCount called.	Debug
606	DecrementBusyCount called.	Debug
701	ServiceChannelOpen started.	Analytic
702	ServiceChannelOpen completed.	Analytic
703	ServiceChannelCall started.	Analytic
704	ServiceChannel asynchronous calls started.	Analytic
706	Http Send Request Start.	Debug
707	Http Send Request Stop.	Debug
708	Message received from http transport.	Analytic
709	Message dispatching started.	Analytic
710	Start authentication for message dispatching	Analytic
711	Start authorization for message dispatching	Analytic
712	Message dispatching completed	Analytic
715	ServiceChannel Open Start.	Analytic
716	ServiceChannel Open Stop.	Analytic
717	Http Send streamed message started.	Analytic
1001	WorkflowInstance Id: '.	Debug
1002	WorkflowApplication Id: '.	Debug
1003	WorkflowInstance Id: '.	Debug
1004	WorkflowInstance Id: '.	Debug
1005	WorkflowApplication Id: '.	Debug
1006	WorkflowInstance Id: '.	Debug
1007	WorkflowApplication Id: '.	Debug
1008	WorkflowInstance Id: '.	Debug
1009	Parent Activity '.	Debug
1010	Activity '.	Debug
1011	An ExecuteActivityWorkItem has been scheduled for Activity '.	Debug
1012	Starting execution of an ExecuteActivityWorkItem for Activity '.	Debug
1013	An ExecuteActivityWorkItem has completed for Activity '.	Debug
1014	A CompletionWorkItem has been scheduled for parent Activity '.	Debug
1015	Starting execution of a CompletionWorkItem for parent Activity '.	Debug
1016	A CompletionWorkItem has completed for parent Activity '.	Debug
1017	A CancelActivityWorkItem has been scheduled for Activity '.	Debug
1018	Starting execution of a CancelActivityWorkItem for Activity '.	Debug
1019	A CancelActivityWorkItem has completed for Activity '.	Debug
1020	A Bookmark has been created for Activity '.	Debug
1021	A BookmarkWorkItem has been scheduled for Activity '.	Debug
1022	Starting execution of a BookmarkWorkItem for Activity '.	Debug
1023	A BookmarkWorkItem has completed for Activity '.	Debug
1024	A BookmarkScope has been created.	Debug
1025	The BookmarkScope that had TemporaryId: '.	Debug
1026	A TransactionContextWorkItem has been scheduled for Activity '.	Debug
1027	Starting execution of a TransactionContextWorkItem for Activity '.	Debug
1028	A TransactionContextWorkItem has completed for Activity '.	Debug
1029	A FaultWorkItem has been scheduled for Activity '.	Debug
1030	Starting execution of a FaultWorkItem for Activity '.	Debug
1031	A FaultWorkItem has completed for Activity '.	Debug
1032	A runtime work item has been scheduled for Activity '.	Debug
1033	Starting execution of a runtime work item for Activity '.	Debug
1034	A runtime work item has completed for Activity '.	Debug
1035	The runtime transaction has been set by Activity '.	Debug
1036	Activity '.	Debug
1037	The runtime transaction has completed with the state '.	Debug
1038	Entering a no persist block.	Debug
1039	Exiting a no persist block.	Debug
1040	In argument '.	Debug
1041	WorkflowApplication Id: '.	Debug
1101	WorkflowInstance Id: '.	Debug
1102	WorkflowInstance Id: '.	Debug
1103	WorkflowInstance Id: '.	Debug
1104	WorkflowInstance Id: '.	Debug
1124	InvokeMethod '.	Debug
1125	InvokeMethod '.	Debug
1126	An exception was thrown in the method called by the activity '.	Debug
1131	InvokeMethod '.	Debug
1132	InvokeMethod '.	Debug
1140	Flowchart '.	Debug
1141	Flowchart '.	Debug
1143	Flowchart '.	Debug
1146	Flowchart '.	Debug
1147	Flowchart '.	Debug
1148	Flowchart '.	Debug
1150	CompensableActivity '.	Debug
1223	The Switch activity '.	Debug
1400		Analytic
1401		Analytic
1402	%1 Connection pool key: %2.	Analytic
1403	%1 Connection pool key: %2.	Analytic
1405		Analytic
1406		Analytic
1407		Analytic
1409		Analytic
1416		Analytic
1417		Analytic
1418		Debug
1419		Debug
1420		Analytic
1422		Analytic
1423	Negotiate token authenticator state cache ratio: %1/%2.	Debug
1424	Security session ratio: %1/%2.	Debug
1430	Pending connections ratio: %1/%2.	Analytic
1431	Concurrent calls ratio: %1/%2.	Analytic
1432	Concurrent sessions ratio: %1/%2.	Analytic
1433	Outbound connections per endpoint ratio: %1/%2.	Analytic
1436	Pending messages per channel ratio: %1/%2.	Analytic
1438	Concurrent instances ratio: %1/%2.	Analytic
1439	Zero pending accepts left	Debug
1441		Analytic
1442	Receive retry count reached on MSMQ message with id '.	Analytic
1443	Max retry cycles exceeded on MSMQ message with id '.	Analytic
1445	Created new '.	Analytic
1446	Created new '.	Analytic
1449	Message received by workflow	Debug
1450	Message sent from workflow	Debug
1451		Analytic
2021	Execute work item start	Debug
2022	Execute work item stop	Debug
2023	SendMessageChannelCache miss	Debug
2024	InternalCacheMetadata started on activity '.	Debug
2025	InternalCacheMetadata stopped on activity '.	Debug
2026	Compiling VB expression '.	Debug
2027	CacheRootMetadata started on activity '.	Debug
2028	CacheRootMetadata stopped on activity %1.	Debug
2029	Finished compiling VB expression.	Debug
2576	The TryCatch activity '.	Debug
2577	A child activity of the TryCatch activity '.	Debug
2578	A Catch or Finally activity that is associated with the TryCatch activity '.	Debug
3300	Failed to Complete %1.	Analytic
3301	Failed to Abandon %1.	Debug
3302	Receive Context faulted.	Analytic
3303	%1 was Abandoned with exception %2.	Debug
3305	Number of cached channel factories is: '.	Debug
3306	A channel factory has been aged out of the cache because the cache has reached …	Debug
3307	Used matching channel factory found in cache.	Debug
3308	Not using channel factory from cache, i.	Debug
3309	Query composition using '.	Debug
3310	The '.	Analytic
3311	The '.	Analytic
3312	A message with size '.	Debug
3313	A message with size '.	Debug
3314	Session aborting for idle channel to uri:'.	Analytic
3319	Connection accept started.	Debug
3320	ListenerId:%1 accepted SocketId:%2.	Debug
3321	Pool for %1 has no available connection and %2 busy connections.	Debug
3322	Dispatcher started deserialization the request message.	Debug
3323	Dispatcher completed deserialization the request message.	Debug
3324	Dispatcher started serialization of the reply message.	Debug
3325	Dispatcher completed serialization of the reply message.	Debug
3326	Client request serialization started.	Debug
3327	Client completed serialization of the request message.	Debug
3328	Client started deserializing the reply message.	Debug
3329	Client completed deserializing the reply message.	Debug
3330	Security negotiation started.	Debug
3331	Security negotiation completed.	Debug
3332	SecurityTokenProvider opening completed.	Debug
3333	Outgoing message has been secured.	Debug
3334	Incoming message has been verified.	Debug
3335	Service instance retrieval started.	Debug
3336	Service instance retrieved.	Debug
3337	ChannelHandlerId:%1 - Message receive loop started.	Debug
3338	ChannelHandlerId:%1 - Message receive loop stopped.	Debug
3339	ChannelFactory created.	Debug
3340	Pipe connection accept started on %1 .	Debug
3341	Pipe connection accepted.	Debug
3342	Connection establishment started for %1.	Debug
3343	Connection established.	Debug
3345	Session preamble for '.	Debug
3346	Connection reader sending fault '.	Debug
3347	Socket accept closed.	Debug
3348	Service host faulted.	Analytic
3349	Listener opening for '.	Debug
3350	Listener open completed.	Debug
3351	Server max pooled connections quota reached.	Analytic
3352	SocketId:%1 to remote address %2 timed out.	Analytic
3353	SocketId:%1 to remote address %2 had a connection reset error.	Analytic
3354	Service security negotiation completed.	Debug
3355	Security negotiation processing failed.	Analytic
3356	Security verification succeeded.	Debug
3357	Security verification failed.	Analytic
3358	Socket duplicated for %1.	Debug
3359	Security impersonation succeeded.	Debug
3360	Security impersonation failed.	Analytic
3361	Http channel request aborted.	Analytic
3362	Http channel response aborted.	Analytic
3363	Http authentication failed.	Analytic
3364	SharedListenerProxy registration started for uri '.	Analytic
3365	SharedListenerProxy Register Stop.	Analytic
3366	SharedListenerProxy register failed with status '.	Analytic
3367	ConnectionPoolPreambleFailed.	Analytic
3368	SslOnAcceptUpgradeStart	Analytic
3369	SslOnAcceptUpgradeStop	Analytic
3370	BinaryMessageEncoder started encoding the message.	Debug
3371	MtomMessageEncoder started encoding the message.	Debug
3372	TextMessageEncoder started encoding the message.	Debug
3373	BinaryMessageEncoder started decoding the message.	Debug
3374	MtomMessageEncoder started decoding the message.	Debug
3375	TextMessageEncoder started decoding the message.	Debug
3376	Http transport started receiving a message.	Debug
3377	SocketId:%1 read '%2' bytes read from '%3'.	Debug
3378	SocketId:%1 read '%2' bytes read from '%3'.	Debug
3379	SocketId:%1 writing '%2' bytes to '%3'.	Debug
3380	SocketId:%1 writing '%2' bytes to '%3'.	Debug
3381	SessionId:%1 acknowledgement sent.	Debug
3382	SessionId:%1 reconnecting.	Debug
3383	SessionId:%1 faulted.	Debug
3384	WindowsStreamSecurity initiating security upgrade.	Analytic
3385	Windows streaming security on accepting upgrade.	Analytic
3386	SocketId:%1 is aborting.	Analytic
3388	HttpGetContext start.	Analytic
3389	Client sending preamble start.	Debug
3390	Client sending preamble stop.	Debug
3391	Http Message receive failed.	Analytic
3392	TransactionScope is being created with LocalIdentifier:'.	Debug
3393	A streamed message was read by the encoder.	Debug
3394	A streamed message was written by the encoder.	Debug
3395	A message was written asynchronously by the encoder.	Debug
3396	BufferId:%1 completed writing '%2' bytes to underlying stream.	Debug
3397	A message was written asynchronously by the encoder.	Debug
3398	Pipe shared memory created at '.	Debug
3399	NamedPipe '.	Debug
3401	Signature verification started.	Debug
3402	Signature verification succeeded	Debug
3403	Wrapped key decryption started.	Debug
3404	Wrapped key decryption succeeded.	Debug
3405	Encrypted data processing started.	Debug
3406	Encrypted data processing succeeded.	Debug
3407	Http message handler started processing the inbound request.	Debug
3408	Http message handler started processing the inbound request asynchronously.	Debug
3409	Http message handler completed processing an inbound request.	Debug
3410	Http message handler is faulted.	Analytic
3411	WebSocket connection timed out.	Analytic
3412	Http message handler started processing the response.	Debug
3413	Http message handler started processing the response asynchronously.	Debug
3414	Http message handler completed processing the response.	Debug
3415	WebSocket connection request to '.	Debug
3416	WebSocketId:%1 connection request sent.	Debug
3417	WebSocket connection accept start.	Debug
3418	WebSocketId:%1 connection accepted.	Debug
3419	WebSocket connection declined with status code '.	Analytic
3420	WebSocket connection request failed: '.	Analytic
3421	WebSocketId:%1 connection is aborted.	Analytic
3422	WebSocketId:%1 writing '%2' bytes to '%3'.	Debug
3423	WebSocketId:%1 asynchronous write stop.	Debug
3424	WebSocketId:%1 read start.	Debug
3425	WebSocketId:%1 read '%2' bytes from '%3'.	Debug
3426	WebSocketId:%1 sending close message to '%2' with close status '%3'.	Debug
3427	WebSocketId:%1 sending close output message to '%2' with close status '%3'.	Debug
3428	WebSocketId:%1 connection closed.	Debug
3429	WebSocketId:%1 connection close message received with status '%2'.	Debug
3430	Using the WebSocketVersion from a client WebSocket factory of type '.	Debug
3431	Creating the client WebSocket with a factory of type '.	Debug
3501	ContractDescription with Name='.	Analytic
3502	OperationDescription with Name='.	Analytic
3503	A duplicate CorrelationQuery was found with Where='.	Analytic
3507	A service endpoint has been added for address '.	Analytic
3508	TrackingProfile '.	Analytic
3550	Operation '.	Analytic
3551	Operation '.	Analytic
3552	The throttle 'MaxPendingMessagesPerChannel' limit of '.	Analytic
3553	XamlServicesLoad start	Debug
3554	XamlServicesLoad Stop	Debug
3555	CreateWorkflowServiceHost start	Debug
3556	CreateWorkflowServiceHost Stop	Debug
3557	The call to EndCommit on the CommittableTransaction with id = '.	Analytic
3558	Service activation start	Analytic
3559	Service activation Stop	Analytic
3560	Available memory (bytes).	Analytic
3561	The service could not be activated.	Operational
3800	The Routing Service is closing client '.	Debug
3801	Routing Service client '.	Debug
3802	A Routing Service one way message is completing.	Debug
3803	The Routing Service failed while processing a message on the endpoint with …	Debug
3804	The Routing Service is creating a client for endpoint: '.	Debug
3805	The Routing Service is configured with RouteOnHeadersOnly: %1, …	Debug
3807	A Routing Service request reply message is completing.	Debug
3809	The Routing Service routed message with ID: '.	Debug
3810	A new RoutingConfiguration has been applied to the Routing Service.	Debug
3815	The Routing Service is processing a message with ID: '.	Debug
3816	The Routing Service is transmitting the message with ID: '.	Debug
3817	The Routing Service is committing a transaction with id: '.	Debug
3818	Routing Service component %1 encountered a duplex callback exception.	Debug
3819	Routing Service message with ID: '.	Debug
3820	The Routing Service created a new Transaction with id '.	Debug
3821	The Routing Service failed while closing outbound client '.	Debug
3822	The Routing Service is sending back a response message with Action '.	Debug
3823	The Routing Service is sending back a Fault response message with Action '.	Debug
3824	The Routing Service is calling ReceiveContext.	Debug
3825	The Routing Service is calling ReceiveContext.	Debug
3826	The Routing Service will send messages using existing transaction '.	Debug
3827	The Routing Service failed while sending to '.	Debug
3828	Routing Service MessageFilterTable Match Start.	Analytic
3829	Routing Service MessageFilterTable Match Stop.	Analytic
3830	The Routing Service is calling abort on channel: '.	Debug
3831	The Routing Service has handled an exception.	Debug
3832	The Routing Service successfully transmitted Message with ID: '.	Debug
4001	Transport listener session received with via '.	Analytic
4002	FailFastException.	Analytic
4003	Service start pipe error.	Analytic
4008	Session dispatch started.	Analytic
4010	Session dispatch for '.	Analytic
4011	Message queue register start.	Analytic
4012	Message queue registration aborted with status:'.	Analytic
4013	Message queue unregister succeeded for uri:'.	Analytic
4014	Message queue registration for uri:'.	Analytic
4015	Message queue registration completed for uri '.	Analytic
4016	Message queue failed duplicating socket.	Analytic
4019	MessageQueueDuplicatedSocketComplete	Analytic
4020	Tcp transport listener starting to listen on uri:'.	Analytic
4021	Tcp transport listener listening.	Analytic
4022	Error Code.	Analytic
4023	Was closing all listener channel instances completed.	Analytic
4024	Error Code.	Analytic
4025	Error Code.	Analytic
4026	WAS Connected.	Analytic
4027	WAS Disconnected.	Analytic
4028	Pipe transport listener listening start on uri.	Analytic
4029	Pipe transport listener listening stop.	Analytic
4030	Session dispatch succeeded.	Analytic
4031	Session dispatch failed.	Analytic
4032	WAS connection timed out.	Analytic
4033	Routing table lookup started.	Debug
4034	Routing table lookup completed.	Debug
4035	Pending session queue ratio: %1/%2.	Debug
4201	End SQL command execution.	Debug
4202	Starting SQL command execution.	Debug
4203	Failed to extend lock expiration, lock expiration already passed or the lock …	Debug
4205	Command failed.	Debug
4206	Encountered exception %1 while attempting to unlock instance.	Debug
4207	Giving up retrying a SQL command as the maximum number of retries have been …	Debug
4208	Retrying a SQL command due to SQL error number %1.	Debug
4209	Timeout trying to open a SQL connection.	Debug
4210	Caught SQL Exception number %1 message %2.	Debug
4211	Queuing SQL retry with delay %1 milliseconds.	Debug
4212	Timeout trying to acquire the instance lock.	Debug
4213	Detection of runnable instances failed due to the following exception	Debug
4214	Recovering instance locks failed due to the following exception	Debug
4600	Message could not be logged as it exceeds the ETW event size	Debug
4801	The DiscoveryClient created inside DiscoveryClientChannel failed to close and …	Debug
4802	A ProtocolException was suppressed while closing the DiscoveryClient.	Debug
4803	The DiscoveryClient received a multicast suppression message from a …	Debug
4804	A %1 message with messageId='%2' was dropped by the DiscoveryClient because the …	Debug
4805	A %1 message with messageId='%2' was dropped because it had invalid content.	Debug
4806	A %1 message with messageId='%2' and relatesTo='%3' was dropped by the …	Debug
4807	A discovery request message with messageId='.	Debug
4808	A %1 message was dropped because it did not have any content.	Debug
4809	A %1 message was dropped because the message header did not contain the required …	Debug
4810	A %1 message with messageId='%2' was dropped by the DiscoveryClient because it …	Debug
4811	A %1 message with messageId='%2' was dropped by the DiscoveryClient because the …	Debug
4812	A discovery request message with messageId='.	Debug
4813	A %1 message with messageId='%2' was dropped because it was a duplicate.	Debug
4814	The discoverability of endpoint with EndpointAddress='.	Debug
4815	The discoverability of endpoint with EndpointAddress='.	Debug
4816	A Find operation was initiated in the DiscoveryClientChannel to discover …	Debug
4817	The DiscoveryClientChannel failed to create the channel with a discovered …	Debug
4818	The DiscoveryClientChannel failed to open the channel with a discovered endpoint …	Debug
4819	The DiscoveryClientChannel successfully discovered an endpoint and opened the …	Debug
4820	The SynchronizationContext has been reset to its original value of %1 by …	Debug
4821	The SynchronizationContext has been set to null by DiscoveryClientChannel before …	Debug
5001	DataContract serialize %1 with surrogates start.	Debug
5002	DataContract serialize with surrogates stop.	Debug
5003	DataContract deserialize %1 with surrogates start.	Debug
5004	DataContract deserialize with surrogates stop.	Debug
5005	ImportKnownTypes start.	Debug
5006	ImportKnownTypes stop.	Debug
5007	DataContract resolver resolving %1 start.	Debug
5008	DataContract generate %1 writer for %2 start.	Debug
5009	DataContract generate writer stop.	Debug
5010	DataContract generate %1 reader for %2 start.	Debug
5011	DataContract generation stop.	Debug
5012	Json generate %1 reader for %2 start.	Debug
5013	Json reader generation stop.	Debug
5014	Json generate %1 writer for %2 start.	Debug
5015	Json generate writer stop.	Debug
5016	Generate Xml serializable for '.	Debug
5017	Generate Xml serializable stop.	Debug
5203	JsonMessageEncoder started decoding the message.	Debug
5204	JsonMessageEncoder started encoding the message.	Debug
5402	SecurityToken (type '%1' and id '%2') validation started.	Debug
5403	SecurityToken (type '%1' and id '%2') validation succeeded.	Debug
5404	SecurityToken (type '%1' and id '%2') validation failed.	Debug
5405	Retrieval of issuer name:%1 from tokenId:%2 succeeded.	Debug
5406	Retrieval of issuer name from tokenId:%1 failed.	Debug
5600	Federation message processing started.	Debug
5601	Federation message processing succeeded.	Debug
5602	Creating federation message from form post started.	Debug
5603	Creating federation message from form post succeeded.	Debug
5604	Reading session token from session cookie started.	Debug
5605	Reading session token from session cookie succeeded.	Debug
5606	Principal setting from session token started.	Debug
5607	Principal setting from session token succeeded.	Debug
39456	Size of tracking record %1 exceeds maximum allowed by the ETW session for …	Debug
39457	Tracking Record %1 raised to %2.	Debug
39458	Truncated tracking record %1 written to ETW session with provider %2.	Debug
39459	Tracking data %1 extracted in activity %2.	Debug
39460	The extracted argument/variable '.	Debug
57393	AppDomain unloading.	Debug
57394	Handling an exception.	Analytic
57395	An unexpected failure occurred.	Analytic
57396	Throwing an exception.	Analytic
57397	Unhandled exception.	Operational
57398	The system hit the limit set for throttle 'MaxConcurrentInstances'.	Analytic
57399	Wrote to the EventLog.	Debug
57400	Wrote to the EventLog.	Debug
57401	Wrote to the EventLog.	Debug
57402	Wrote to the EventLog.	Debug
57403	Wrote to the EventLog.	Debug
57404	Handling an exception.	Analytic
57405	Handling an exception.	Operational
57406	Handling an exception Exception details.	Analytic
57407	Throwing an exception.	Analytic
57408	Unhandled exception.	Operational
57409	Throwing an exception.	Analytic
57410	Throwing an exception.	Analytic
62326	The url '.	Debug

Event ID 100 — TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, Annotations = %6, P...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, Annotations = %6, ProfileName = %7

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`State`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 101 — TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, SourceName =...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, SourceName = %5, SourceId = %6, SourceInstanceId = %7, SourceTypeName=%8, Exception=%9, Annotations= %10, ProfileName = %11

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`SourceName`	—
`SourceId`	—
`SourceInstanceId`	—
`SourceTypeName`	—
`Exception`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 102 — TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotation...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotations = %6, ProfileName = %7

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 103 — TrackRecord = ActivityStateRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, State = %4, Name=%5, ActivityId=%6, ActivityInstanceId=%7, Activ...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = ActivityStateRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, State = %4, Name=%5, ActivityId=%6, ActivityInstanceId=%7, ActivityTypeName=%8, Arguments=%9, Variables=%10, Annotations=%11, ProfileName = %12

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`State`	—
`Name`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`Arguments`	—
`Variables`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 104 — TrackRecord = ActivityScheduledRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, Name = %4, ActivityId = %5, ActivityInstanceId = %6, Act...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = ActivityScheduledRecord, InstanceID = %1,  RecordNumber = %2, EventTime = %3, Name = %4, ActivityId = %5, ActivityInstanceId = %6, ActivityTypeName = %7, ChildActivityName = %8, ChildActivityId = %9, ChildActivityInstanceId = %10, ChildActivityTypeName =%11, Annotations=%12, ProfileName = %13

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`ChildActivityName`	—
`ChildActivityId`	—
`ChildActivityInstanceId`	—
`ChildActivityTypeName`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 105 — TrackRecord = FaultPropagationRecord, InstanceID=.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = FaultPropagationRecord, InstanceID=%1, RecordNumber=%2, EventTime=%3, FaultSourceActivityName=%4, FaultSourceActivityId=%5, FaultSourceActivityInstanceId=%6, FaultSourceActivityTypeName=%7, FaultHandlerActivityName=%8,  FaultHandlerActivityId = %9, FaultHandlerActivityInstanceId =%10, FaultHandlerActivityTypeName=%11, Fault=%12, IsFaultSource=%13, Annotations=%14, ProfileName = %15

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`FaultSourceActivityName`	—
`FaultSourceActivityId`	—
`FaultSourceActivityInstanceId`	—
`FaultSourceActivityTypeName`	—
`FaultHandlerActivityName`	—
`FaultHandlerActivityId`	—
`FaultHandlerActivityInstanceId`	—
`FaultHandlerActivityTypeName`	—
`Fault`	—
`IsFaultSource`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 106 — TrackRecord = CancelRequestedRecord, InstanceID=.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = CancelRequestedRecord, InstanceID=%1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityId=%5, ActivityInstanceId=%6, ActivityTypeName = %7, ChildActivityName = %8, ChildActivityId = %9, ChildActivityInstanceId = %10, ChildActivityTypeName =%11, Annotations=%12, ProfileName = %13

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`ChildActivityName`	—
`ChildActivityId`	—
`ChildActivityInstanceId`	—
`ChildActivityTypeName`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 107 — TrackRecord = BookmarkResumptionRecord, InstanceID=.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = BookmarkResumptionRecord, InstanceID=%1, RecordNumber=%2,EventTime=%3, Name=%4, SubInstanceID=%5,  OwnerActivityName=%6, OwnerActivityId =%7, OwnerActivityInstanceId=%8, OwnerActivityTypeName=%9, Annotations=%10, ProfileName = %11

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`SubInstanceID`	—
`OwnerActivityName`	—
`OwnerActivityId`	—
`OwnerActivityInstanceId`	—
`OwnerActivityTypeName`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 108 — TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7,...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3,  Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7, ActivityTypeName=%8, Data=%9, Annotations=%10, ProfileName = %11

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`ActivityName`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`Data`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 110 — TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7,...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7, ActivityTypeName=%8, Data=%9, Annotations=%10, ProfileName = %11

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`ActivityName`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`Data`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 111 — TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7,...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = CustomTrackingRecord, InstanceID = %1, RecordNumber=%2, EventTime=%3, Name=%4, ActivityName=%5, ActivityId=%6, ActivityInstanceId=%7, ActivityTypeName=%8, Data=%9, Annotations=%10, ProfileName = %11

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`Name`	—
`ActivityName`	—
`ActivityId`	—
`ActivityInstanceId`	—
`ActivityTypeName`	—
`Data`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 112 — TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotati...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotations = %6, ProfileName = %7

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 113 — TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotat...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotations = %6, ProfileName = %7

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 114 — TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, Annotations = %6, P...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord= WorkflowInstanceRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, Annotations = %6, ProfileName = %7, WorkflowDefinitionIdentity = %8

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`State`	—
`Annotations`	—
`ProfileName`	—
`WorkflowDefinitionIdentity`	—
`HostReference`	—
`AppDomain`	—

Event ID 115 — TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotation...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceAbortedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5,  Annotations = %6, ProfileName = %7, WorkflowDefinitionIdentity = %8

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`WorkflowDefinitionIdentity`	—
`HostReference`	—
`AppDomain`	—

Event ID 116 — TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotati...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceSuspendedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotations = %6, ProfileName = %7, WorkflowDefinitionIdentity = %8

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`WorkflowDefinitionIdentity`	—
`HostReference`	—
`AppDomain`	—

Event ID 117 — TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5, Annotat...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceTerminatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, Reason = %5,  Annotations = %6, ProfileName = %7, WorkflowDefinitionIdentity = %8

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`Reason`	—
`Annotations`	—
`ProfileName`	—
`WorkflowDefinitionIdentity`	—
`HostReference`	—
`AppDomain`	—

Event ID 118 — TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, SourceName =...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord = WorkflowInstanceUnhandledExceptionRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, SourceName = %5, SourceId = %6, SourceInstanceId = %7, SourceTypeName=%8, Exception=%9,  Annotations= %10, ProfileName = %11, WorkflowDefinitionIdentity = %12

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`SourceName`	—
`SourceId`	—
`SourceInstanceId`	—
`SourceTypeName`	—
`Exception`	—
`Annotations`	—
`ProfileName`	—
`WorkflowDefinitionIdentity`	—
`HostReference`	—
`AppDomain`	—

Event ID 119 — TrackRecord= WorkflowInstanceUpdatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, OriginalDefi...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackRecord= WorkflowInstanceUpdatedRecord, InstanceID = %1, RecordNumber = %2, EventTime = %3, ActivityDefinitionId = %4, State = %5, OriginalDefinitionIdentity = %6, UpdatedDefinitionIdentity = %7, Annotations = %8, ProfileName = %9

Fields

Name	Description
`InstanceId`	—
`RecordNumber`	—
`EventTime`	—
`ActivityDefinitionId`	—
`State`	—
`OriginalDefinitionIdentity`	—
`UpdatedDefinitionIdentity`	—
`Annotations`	—
`ProfileName`	—
`HostReference`	—
`AppDomain`	—

Event ID 131 — Pool allocating %1 Bytes.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pool allocating %1 Bytes.

Fields

Name	Description
`Size`	—
`AppDomain`	—

Event ID 132 — BufferPool of size %1, changing quota by %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

BufferPool of size %1, changing quota by %2.

Fields

Name	Description
`PoolSize`	—
`Delta`	—
`AppDomain`	—

Event ID 133 — IO Thread scheduler callback invoked.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

IO Thread scheduler callback invoked.

Fields

Name	Description
`AppDomain`	—

Event ID 134 — IO Thread scheduler callback invoked.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

IO Thread scheduler callback invoked.

Fields

Name	Description
`AppDomain`	—

Event ID 201 — The Dispatcher invoked 'AfterReceiveReply' on a ClientMessageInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Dispatcher invoked 'AfterReceiveReply' on a ClientMessageInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 202 — The Dispatcher invoked 'BeforeSendRequest' on a ClientMessageInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'BeforeSendRequest' on a ClientMessageInspector of type  '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 203 — The Dispatcher invoked 'AfterCall' on a ClientParameterInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'AfterCall' on a ClientParameterInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 204 — The Dispatcher invoked 'BeforeCall' on a ClientParameterInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'BeforeCall' on a ClientParameterInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 205 — An OperationInvoker invoked the '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

An OperationInvoker invoked the '%1' method. Caller information: '%2'.

Fields

Name	Description
`MethodName`	—
`CallerInfo`	—
`HostReference`	—
`AppDomain`	—

Event ID 206 — The Dispatcher invoked an ErrorHandler of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked an ErrorHandler of type  '%1' with an exception of type '%3'.  ErrorHandled == '%2'.

Fields

Name	Description
`TypeName`	—
`Handled`	—
`ExceptionTypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 207 — The Dispatcher invoked a FaultProvider of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked a FaultProvider of type '%1' with an exception of type '%2'.

Fields

Name	Description
`TypeName`	—
`ExceptionTypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 208 — The Dispatcher invoked 'AfterReceiveReply' on a MessageInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'AfterReceiveReply' on a MessageInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 209 — The Dispatcher invoked 'BeforeSendRequest' on a MessageInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'BeforeSendRequest' on a MessageInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 210 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' throttle limit of '%2' was hit.

Fields

Name	Description
`ThrottleName`	—
`Limit`	—
`HostReference`	—
`AppDomain`	—

Event ID 211 — The Dispatcher invoked 'AfterCall' on a ParameterInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'AfterCall' on a ParameterInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 212 — The Dispatcher invoked 'BeforeCall' on a ParameterInspector of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher invoked 'BeforeCall' on a ParameterInspector of type '%1'.

Fields

Name	Description
`TypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 213 — ServiceHost started: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceHost started: '%1'.

Fields

Name	Description
`ServiceTypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 214 — An OperationInvoker completed the call to the '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

An OperationInvoker completed the call to the '%1' method.  The method call duration was '%2' ms.

Fields

Name	Description
`MethodName`	—
`Duration`	—
`HostReference`	—
`AppDomain`	—

Event ID 215 — The transport received a message from '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The transport received a message from '%1'.

Fields

Name	Description
`ListenAddress`	—
`HostReference`	—
`AppDomain`	—

Event ID 216 — The transport sent a message to '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The transport sent a message to '%1'.

Fields

Name	Description
`DestinationAddress`	—
`HostReference`	—
`AppDomain`	—

Event ID 217 — The Client is executing Action '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Client is executing Action '%1' associated with the '%2' contract. The message will be sent to '%3'.

Fields

Name	Description
`Action`	—
`ContractName`	—
`Destination`	—
`HostReference`	—
`AppDomain`	—

Event ID 218 — The Client completed executing Action '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Client completed executing Action '%1' associated with the '%2' contract. The message was sent to '%3'.

Fields

Name	Description
`Action`	—
`ContractName`	—
`Destination`	—
`HostReference`	—
`AppDomain`	—

Event ID 219 — There was an unhandled exception of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

There was an unhandled exception of type '%2' during message processing.  Full Exception Details: %1.

Fields

Name	Description
`ExceptionToString`	—
`ExceptionTypeName`	—
`HostReference`	—
`AppDomain`	—

Event ID 220 — The Dispatcher sent a message to the transport.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher sent a message to the transport. Correlation ID == '%1'.

Fields

Name	Description
`CorrelationId`	—
`HostReference`	—
`AppDomain`	—

Event ID 221 — The Dispatcher received a message from the transport.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The Dispatcher received a message from the transport. Correlation ID == '%1'.

Fields

Name	Description
`CorrelationId`	—
`HostReference`	—
`AppDomain`	—

Event ID 222 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' method threw an unhandled exception when invoked by the OperationInvoker. The method call duration was '%2' ms.

Fields

Name	Description
`MethodName`	—
`Duration`	—
`HostReference`	—
`AppDomain`	—

Event ID 223 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' method threw a FaultException when invoked by the OperationInvoker. The method call duration was '%2' ms.

Fields

Name	Description
`MethodName`	—
`Duration`	—
`HostReference`	—
`AppDomain`	—

Event ID 224 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' throttle limit of '%2' is at 70%%.

Fields

Name	Description
`ThrottleName`	—
`Limit`	—
`HostReference`	—
`AppDomain`	—

Event ID 225 — Calculated correlation key '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Calculated correlation key '%1' using values '%2' in parent scope '%3'.

Fields

Name	Description
`InstanceKey`	—
`Values`	—
`ParentScope`	—
`HostReference`	—
`AppDomain`	—

Event ID 226 — %1 idle services out of total %2 activated services closed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1 idle services out of total %2 activated services closed.

Fields

Name	Description
`ClosedCount`	—
`TotalCount`	—
`AppDomain`	—

Event ID 301 — Name:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Name:'%1', Reference:'%2', Payload:%3

Fields

Name	Description
`Name`	—
`HostReference`	—
`Payload`	—

Event ID 302 — Name:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Name:'%1', Reference:'%2', Payload:%3

Fields

Name	Description
`Name`	—
`HostReference`	—
`Payload`	—

Event ID 303 — Name:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Name:'%1', Reference:'%2', Payload:%3

Fields

Name	Description
`Name`	—
`HostReference`	—
`Payload`	—

Event ID 401 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 402 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 403 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 404 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 440 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 441 — Activity boundary.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Activity boundary.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 451 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 452 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 499 — Transfer event emitted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Transfer event emitted.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 501 — Begin compilation

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Begin compilation

Fields

Name	Description
`AppDomain`	—

Event ID 502 — End compilation

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

End compilation

Fields

Name	Description
`AppDomain`	—

Event ID 503 — ServiceHostFactory begin creation

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ServiceHostFactory begin creation

Fields

Name	Description
`AppDomain`	—

Event ID 504 — ServiceHostFactory end creation

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ServiceHostFactory end creation

Fields

Name	Description
`AppDomain`	—

Event ID 505 — Begin CreateServiceHost

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Begin CreateServiceHost

Fields

Name	Description
`AppDomain`	—

Event ID 506 — End CreateServiceHost

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

End CreateServiceHost

Fields

Name	Description
`AppDomain`	—

Event ID 507 — HostedTransportConfigurationManager begin configuration initialization

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

HostedTransportConfigurationManager begin configuration initialization

Fields

Name	Description
`AppDomain`	—

Event ID 508 — HostedTransportConfigurationManager end configuration initialization

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

HostedTransportConfigurationManager end configuration initialization

Fields

Name	Description
`AppDomain`	—

Event ID 509 — ServiceHost Open started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceHost Open started.

Fields

Name	Description
`AppDomain`	—

Event ID 510 — ServiceHost Open completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceHost Open completed.

Fields

Name	Description
`AppDomain`	—

Event ID 513 — Received request with virtual path '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Received request with virtual path '%2' from the AppDomain '%1'.

Fields

Name	Description
`AppDomainFriendlyName`	—
`VirtualPath`	—
`AppDomain`	—

Event ID 514 — WebHostRequest stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebHostRequest stop.

Fields

Name	Description
`AppDomain`	—

Event ID 601 — Processed ServiceActivation Element Relative Address:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Processed ServiceActivation Element Relative Address:'%1', Normalized Relative Address '%2' .

Fields

Name	Description
`RelativeAddress`	—
`NormalizedAddress`	—
`AppDomain`	—

Event ID 602 — Incoming request matches a ServiceActivation element with address '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Incoming request matches a ServiceActivation element with address '%1'.

Fields

Name	Description
`IncomingAddress`	—
`AppDomain`	—

Event ID 603 — Incoming request matches a WCF Service defined in Asp.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Incoming request matches a WCF Service defined in Asp.Net route with address %1.

Fields

Name	Description
`IncomingAddress`	—
`AppDomain`	—

Event ID 604 — A new Asp.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A new Asp.Net route '%1' with serviceType '%2' and serviceHostFactoryType '%3' is added.

Fields

Name	Description
`AspNetRoutePrefix`	—
`ServiceType`	—
`ServiceHostFactoryType`	—
`AppDomain`	—

Event ID 605 — IncrementBusyCount called.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

IncrementBusyCount called. Source : %1

Fields

Name	Description
`IncrementBusyCount_called_Source`	IncrementBusyCount called. Source.
`Data`	—
`AppDomain`	—

Event ID 606 — DecrementBusyCount called.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DecrementBusyCount called. Source : %1

Fields

Name	Description
`DecrementBusyCount_called_Source`	DecrementBusyCount called. Source.
`Data`	—
`AppDomain`	—

Event ID 701 — ServiceChannelOpen started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannelOpen started.

Fields

Name	Description
`AppDomain`	—

Event ID 702 — ServiceChannelOpen completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannelOpen completed.

Fields

Name	Description
`AppDomain`	—

Event ID 703 — ServiceChannelCall started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannelCall started.

Fields

Name	Description
`AppDomain`	—

Event ID 704 — ServiceChannel asynchronous calls started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannel asynchronous calls started.

Fields

Name	Description
`AppDomain`	—

Event ID 706 — Http Send Request Start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http Send Request Start.

Fields

Name	Description
`AppDomain`	—

Event ID 707 — Http Send Request Stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http Send Request Stop.

Fields

Name	Description
`AppDomain`	—

Event ID 708 — Message received from http transport.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message received from http transport.

Fields

Name	Description
`AppDomain`	—

Event ID 709 — Message dispatching started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message dispatching started.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 710 — Start authentication for message dispatching

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Start authentication for message dispatching

Fields

Name	Description
`AppDomain`	—

Event ID 711 — Start authorization for message dispatching

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Start authorization for message dispatching

Fields

Name	Description
`AppDomain`	—

Event ID 712 — Message dispatching completed

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message dispatching completed

Fields

Name	Description
`AppDomain`	—

Event ID 715 — ServiceChannel Open Start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannel Open Start.

Fields

Name	Description
`AppDomain`	—

Event ID 716 — ServiceChannel Open Stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ServiceChannel Open Stop.

Fields

Name	Description
`AppDomain`	—

Event ID 717 — Http Send streamed message started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http Send streamed message started.

Fields

Name	Description
`AppDomain`	—

Event ID 1001 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' has completed in the Closed state.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1002 — WorkflowApplication Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowApplication Id: '%1' was terminated. It has completed in the Faulted state with an exception.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1003 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' has completed in the Canceled state.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1004 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' was aborted with an exception.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1005 — WorkflowApplication Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowApplication Id: '%1' went idle.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1006 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' has encountered an unhandled exception.  The exception originated from Activity '%2', DisplayName: '%3'.  The following action will be taken: %4.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1007 — WorkflowApplication Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowApplication Id: '%1' was Persisted.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1008 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' was Unloaded.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1009 — Parent Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Parent Activity '%1', DisplayName: '%2', InstanceId: '%3' scheduled child Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`AppDomain`	—

Event ID 1010 — Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Activity '%1', DisplayName: '%2', InstanceId: '%3' has completed in the '%4' state.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`AppDomain`	—

Event ID 1011 — An ExecuteActivityWorkItem has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

An ExecuteActivityWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1012 — Starting execution of an ExecuteActivityWorkItem for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of an ExecuteActivityWorkItem for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1013 — An ExecuteActivityWorkItem has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

An ExecuteActivityWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1014 — A CompletionWorkItem has been scheduled for parent Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A CompletionWorkItem has been scheduled for parent Activity '%1', DisplayName: '%2', InstanceId: '%3'.  Completed Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`AppDomain`	—

Event ID 1015 — Starting execution of a CompletionWorkItem for parent Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a CompletionWorkItem for parent Activity '%1', DisplayName: '%2', InstanceId: '%3'. Completed Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`AppDomain`	—

Event ID 1016 — A CompletionWorkItem has completed for parent Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A CompletionWorkItem has completed for parent Activity '%1', DisplayName: '%2', InstanceId: '%3'. Completed Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`AppDomain`	—

Event ID 1017 — A CancelActivityWorkItem has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A CancelActivityWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1018 — Starting execution of a CancelActivityWorkItem for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a CancelActivityWorkItem for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1019 — A CancelActivityWorkItem has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A CancelActivityWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1020 — A Bookmark has been created for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A Bookmark has been created for Activity '%1', DisplayName: '%2', InstanceId: '%3'.  BookmarkName: %4, BookmarkScope: %5.

Fields

Name	Description
`BookmarkScope`	—
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`AppDomain`	—

Event ID 1021 — A BookmarkWorkItem has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A BookmarkWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.  BookmarkName: %4, BookmarkScope: %5.

Fields

Name	Description
`BookmarkScope`	—
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`AppDomain`	—

Event ID 1022 — Starting execution of a BookmarkWorkItem for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a BookmarkWorkItem for Activity '%1', DisplayName: '%2', InstanceId: '%3'.  BookmarkName: %4, BookmarkScope: %5.

Fields

Name	Description
`BookmarkScope`	—
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`AppDomain`	—

Event ID 1023 — A BookmarkWorkItem has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A BookmarkWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'. BookmarkName: %4, BookmarkScope: %5.

Fields

Name	Description
`BookmarkScope`	—
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`AppDomain`	—

Event ID 1024 — A BookmarkScope has been created.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A BookmarkScope has been created: %1.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1025 — The BookmarkScope that had TemporaryId: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The BookmarkScope that had TemporaryId: '%1' has been initialized with Id: '%2'.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 1026 — A TransactionContextWorkItem has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A TransactionContextWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1027 — Starting execution of a TransactionContextWorkItem for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a TransactionContextWorkItem for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1028 — A TransactionContextWorkItem has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A TransactionContextWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1029 — A FaultWorkItem has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A FaultWorkItem has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.  The exception was propagated from Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1030 — Starting execution of a FaultWorkItem for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a FaultWorkItem for Activity '%1', DisplayName: '%2', InstanceId: '%3'.  The exception was propagated from Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1031 — A FaultWorkItem has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A FaultWorkItem has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'. The exception was propagated from Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`SerializedException`	—
`AppDomain`	—

Event ID 1032 — A runtime work item has been scheduled for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A runtime work item has been scheduled for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1033 — Starting execution of a runtime work item for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting execution of a runtime work item for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1034 — A runtime work item has completed for Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A runtime work item has completed for Activity '%1', DisplayName: '%2', InstanceId: '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1035 — The runtime transaction has been set by Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The runtime transaction has been set by Activity '%1', DisplayName: '%2', InstanceId: '%3'.  Execution isolated to Activity '%4', DisplayName: '%5', InstanceId: '%6'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`data6`	—
`AppDomain`	—

Event ID 1036 — Activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Activity '%1', DisplayName: '%2', InstanceId: '%3' has scheduled completion of the runtime transaction.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1037 — The runtime transaction has completed with the state '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The runtime transaction has completed with the state '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1038 — Entering a no persist block.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Entering a no persist block.

Fields

Name	Description
`AppDomain`	—

Event ID 1039 — Exiting a no persist block.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Exiting a no persist block.

Fields

Name	Description
`AppDomain`	—

Event ID 1040 — In argument '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

In argument '%1' on Activity '%2', DisplayName: '%3', InstanceId: '%4' has been bound with value: %5.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`data5`	—
`AppDomain`	—

Event ID 1041 — WorkflowApplication Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowApplication Id: '%1' is idle and persistable.  The following action will be taken: %2.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 1101 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' E2E Activity

Fields

Name	Description
`Id`	—
`AppDomain`	—

Event ID 1102 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' E2E Activity

Fields

Name	Description
`Id`	—
`AppDomain`	—

Event ID 1103 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' E2E Activity

Fields

Name	Description
`Id`	—
`AppDomain`	—

Event ID 1104 — WorkflowInstance Id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WorkflowInstance Id: '%1' E2E Activity

Fields

Name	Description
`Id`	—
`AppDomain`	—

Event ID 1124 — InvokeMethod '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InvokeMethod '%1' - method is Static.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1125 — InvokeMethod '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InvokeMethod '%1' - method is not Static.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1126 — An exception was thrown in the method called by the activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

An exception was thrown in the method called by the activity '%1'. %2

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 1131 — InvokeMethod '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InvokeMethod '%1' - method uses asynchronous pattern of '%2' and '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 1132 — InvokeMethod '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InvokeMethod '%1' - method does not use asynchronous pattern.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1140 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1' - Start has been scheduled.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1141 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1' - was executed with no Nodes.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1143 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1'/FlowStep - Next node is null. Flowchart execution will end.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1146 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1'/FlowSwitch - Case '%2' was selected.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 1147 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1'/FlowSwitch - Default Case was selected.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1148 — Flowchart '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Flowchart '%1'/FlowSwitch - could find neither a Case activity nor a Default Case matching the Expression result. Flowchart execution will end.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1150 — CompensableActivity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

CompensableActivity '%1' is in the '%2' state.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 1223 — The Switch activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Switch activity '%1' could not find a Case activity matching the Expression result.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1400 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1401 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1402 — %1 Connection pool key: %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1 Connection pool key: %2

Fields

Name	Description
`msg`	—
`key`	—
`AppDomain`	—

Event ID 1403 — %1 Connection pool key: %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1 Connection pool key: %2

Fields

Name	Description
`msg`	—
`key`	—
`AppDomain`	—

Event ID 1405 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1406 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1407 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1409 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1416 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1417 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1418 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1419 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1420 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1422 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`msg`	—
`AppDomain`	—

Event ID 1423 — Negotiate token authenticator state cache ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Negotiate token authenticator state cache ratio: %1/%2

Fields

Name	Description
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1424 — Security session ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Security session ratio: %1/%2

Fields

Name	Description
`Security_session_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1430 — Pending connections ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Pending connections ratio: %1/%2

Fields

Name	Description
`Pending_connections_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1431 — Concurrent calls ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Concurrent calls ratio: %1/%2

Fields

Name	Description
`Concurrent_calls_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1432 — Concurrent sessions ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Concurrent sessions ratio: %1/%2

Fields

Name	Description
`Concurrent_sessions_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1433 — Outbound connections per endpoint ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Outbound connections per endpoint ratio: %1/%2

Fields

Name	Description
`Outbound_connections_per_endpoint_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1436 — Pending messages per channel ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Pending messages per channel ratio: %1/%2

Fields

Name	Description
`Pending_messages_per_channel_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1438 — Concurrent instances ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Concurrent instances ratio: %1/%2

Fields

Name	Description
`Concurrent_instances_ratio`	—
`cur`	—
`max`	—
`AppDomain`	—

Event ID 1439 — Zero pending accepts left

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Zero pending accepts left

Fields

Name	Description
`AppDomain`	—

Event ID 1441 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1442 — Receive retry count reached on MSMQ message with id '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Receive retry count reached on MSMQ message with id '%1'

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1443 — Max retry cycles exceeded on MSMQ message with id '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Max retry cycles exceeded on MSMQ message with id '%1'

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 1445 — Created new '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Created new '%1'

Fields

Name	Description
`itemTypeName`	—
`AppDomain`	—

Event ID 1446 — Created new '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Created new '%1'

Fields

Name	Description
`itemTypeName`	—
`AppDomain`	—

Event ID 1449 — Message received by workflow

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Message received by workflow

Fields

Name	Description
`AppDomain`	—

Event ID 1450 — Message sent from workflow

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Message sent from workflow

Fields

Name	Description
`AppDomain`	—

Event ID 1451 —

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

%1

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 2021 — Execute work item start

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Execute work item start

Fields

Name	Description
`AppDomain`	—

Event ID 2022 — Execute work item stop

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Execute work item stop

Fields

Name	Description
`AppDomain`	—

Event ID 2023 — SendMessageChannelCache miss

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SendMessageChannelCache miss

Fields

Name	Description
`AppDomain`	—

Event ID 2024 — InternalCacheMetadata started on activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InternalCacheMetadata started on activity '%1'.

Fields

Name	Description
`id`	—
`AppDomain`	—

Event ID 2025 — InternalCacheMetadata stopped on activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

InternalCacheMetadata stopped on activity '%1'.

Fields

Name	Description
`id`	—
`AppDomain`	—

Event ID 2026 — Compiling VB expression '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Compiling VB expression '%1'

Fields

Name	Description
`expr`	—
`AppDomain`	—

Event ID 2027 — CacheRootMetadata started on activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

CacheRootMetadata started on activity '%1'

Fields

Name	Description
`activityName`	—
`AppDomain`	—

Event ID 2028 — CacheRootMetadata stopped on activity %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

CacheRootMetadata stopped on activity %1.

Fields

Name	Description
`activityName`	—
`AppDomain`	—

Event ID 2029 — Finished compiling VB expression.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Finished compiling VB expression.

Fields

Name	Description
`AppDomain`	—

Event ID 2576 — The TryCatch activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The TryCatch activity '%1' has caught an exception of type '%2'.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 2577 — A child activity of the TryCatch activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A child activity of the TryCatch activity '%1' has thrown an exception during cancelation.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 2578 — A Catch or Finally activity that is associated with the TryCatch activity '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A Catch or Finally activity that is associated with the TryCatch activity '%1' has thrown an exception.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3300 — Failed to Complete %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Failed to Complete %1.

Fields

Name	Description
`TypeName`	—
`AppDomain`	—

Event ID 3301 — Failed to Abandon %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Failed to Abandon %1.

Fields

Name	Description
`TypeName`	—
`AppDomain`	—

Event ID 3302 — Receive Context faulted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Receive Context faulted.

Fields

Name	Description
`EventSource`	—
`AppDomain`	—

Event ID 3303 — %1 was Abandoned with exception %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

%1 was Abandoned with exception %2.

Fields

Name	Description
`TypeName`	—
`ExceptionToString`	—
`AppDomain`	—

Event ID 3305 — Number of cached channel factories is: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Number of cached channel factories is: '%1'.  At most '%2' channel factories can be cached.

Fields

Name	Description
`Count`	—
`MaxNum`	—
`EventSource`	—
`AppDomain`	—

Event ID 3306 — A channel factory has been aged out of the cache because the cache has reached its limit of '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A channel factory has been aged out of the cache because the cache has reached its limit of '%1'.

Fields

Name	Description
`Count`	—
`EventSource`	—
`AppDomain`	—

Event ID 3307 — Used matching channel factory found in cache.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Used matching channel factory found in cache.

Fields

Name	Description
`EventSource`	—
`AppDomain`	—

Event ID 3308 — Not using channel factory from cache, i.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Not using channel factory from cache, i.e. caching disabled for instance.

Fields

Name	Description
`EventSource`	—
`AppDomain`	—

Event ID 3309 — Query composition using '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Query composition using '%1' was executed on the Request Uri: '%2'.

Fields

Name	Description
`TypeName`	—
`Uri`	—
`EventSource`	—
`AppDomain`	—

Event ID 3310 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' operation was dispatched with errors.

Fields

Name	Description
`OperationName`	—
`HostReference`	—
`AppDomain`	—

Event ID 3311 — The '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The '%1' operation was dispatched successfully.

Fields

Name	Description
`OperationName`	—
`HostReference`	—
`AppDomain`	—

Event ID 3312 — A message with size '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A message with size '%1' bytes was read by the encoder.

Fields

Name	Description
`Size`	—
`EventSource`	—
`AppDomain`	—

Event ID 3313 — A message with size '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A message with size '%1' bytes was written by the encoder.

Fields

Name	Description
`Size`	—
`EventSource`	—
`AppDomain`	—

Event ID 3314 — Session aborting for idle channel to uri:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Session aborting for idle channel to uri:'%1'.

Fields

Name	Description
`RemoteAddress`	—
`AppDomain`	—

Event ID 3319 — Connection accept started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Connection accept started.

Fields

Name	Description
`AppDomain`	—

Event ID 3320 — ListenerId:%1 accepted SocketId:%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ListenerId:%1 accepted SocketId:%2.

Fields

Name	Description
`ListenerId`	—
`accepted_SocketId`	—
`ListenerHashCode`	—
`SocketHashCode`	—
`AppDomain`	—

Event ID 3321 — Pool for %1 has no available connection and %2 busy connections.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pool for %1 has no available connection and %2 busy connections.

Fields

Name	Description
`PoolKey`	—
`busy`	—
`AppDomain`	—

Event ID 3322 — Dispatcher started deserialization the request message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Dispatcher started deserialization the request message.

Fields

Name	Description
`AppDomain`	—

Event ID 3323 — Dispatcher completed deserialization the request message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Dispatcher completed deserialization the request message.

Fields

Name	Description
`AppDomain`	—

Event ID 3324 — Dispatcher started serialization of the reply message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Dispatcher started serialization of the reply message.

Fields

Name	Description
`AppDomain`	—

Event ID 3325 — Dispatcher completed serialization of the reply message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Dispatcher completed serialization of the reply message.

Fields

Name	Description
`AppDomain`	—

Event ID 3326 — Client request serialization started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client request serialization started.

Fields

Name	Description
`AppDomain`	—

Event ID 3327 — Client completed serialization of the request message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client completed serialization of the request message.

Fields

Name	Description
`AppDomain`	—

Event ID 3328 — Client started deserializing the reply message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client started deserializing the reply message.

Fields

Name	Description
`AppDomain`	—

Event ID 3329 — Client completed deserializing the reply message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client completed deserializing the reply message.

Fields

Name	Description
`AppDomain`	—

Event ID 3330 — Security negotiation started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Security negotiation started.

Fields

Name	Description
`AppDomain`	—

Event ID 3331 — Security negotiation completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Security negotiation completed.

Fields

Name	Description
`AppDomain`	—

Event ID 3332 — SecurityTokenProvider opening completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SecurityTokenProvider opening completed.

Fields

Name	Description
`AppDomain`	—

Event ID 3333 — Outgoing message has been secured.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Outgoing message has been secured.

Fields

Name	Description
`AppDomain`	—

Event ID 3334 — Incoming message has been verified.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Incoming message has been verified.

Fields

Name	Description
`AppDomain`	—

Event ID 3335 — Service instance retrieval started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Service instance retrieval started.

Fields

Name	Description
`AppDomain`	—

Event ID 3336 — Service instance retrieved.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Service instance retrieved.

Fields

Name	Description
`AppDomain`	—

Event ID 3337 — ChannelHandlerId:%1 - Message receive loop started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ChannelHandlerId:%1 - Message receive loop started.

Fields

Name	Description
`ChannelHandlerId`	—
`ChannelId`	—
`AppDomain`	—

Event ID 3338 — ChannelHandlerId:%1 - Message receive loop stopped.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ChannelHandlerId:%1 - Message receive loop stopped.

Fields

Name	Description
`ChannelHandlerId`	—
`ChannelId`	—
`AppDomain`	—

Event ID 3339 — ChannelFactory created.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ChannelFactory created .

Fields

Name	Description
`EventSource`	—
`AppDomain`	—

Event ID 3340 — Pipe connection accept started on %1 .

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pipe connection accept started on %1 .

Fields

Name	Description
`uri`	—
`AppDomain`	—

Event ID 3341 — Pipe connection accepted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pipe connection accepted.

Fields

Name	Description
`AppDomain`	—

Event ID 3342 — Connection establishment started for %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Connection establishment started for %1.

Fields

Name	Description
`Key`	—
`AppDomain`	—

Event ID 3343 — Connection established.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Connection established.

Fields

Name	Description
`AppDomain`	—

Event ID 3345 — Session preamble for '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Session preamble for '%1' understood.

Fields

Name	Description
`Via`	—
`AppDomain`	—

Event ID 3346 — Connection reader sending fault '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Connection reader sending fault '%1'.

Fields

Name	Description
`FaultString`	—
`AppDomain`	—

Event ID 3347 — Socket accept closed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Socket accept closed.

Fields

Name	Description
`AppDomain`	—

Event ID 3348 — Service host faulted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Service host faulted.

Fields

Name	Description
`EventSource`	—
`AppDomain`	—

Event ID 3349 — Listener opening for '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Listener opening for '%1'.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 3350 — Listener open completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Listener open completed.

Fields

Name	Description
`AppDomain`	—

Event ID 3351 — Server max pooled connections quota reached.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Server max pooled connections quota reached.

Fields

Name	Description
`AppDomain`	—

Event ID 3352 — SocketId:%1 to remote address %2 timed out.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SocketId:%1 to remote address %2 timed out.

Fields

Name	Description
`SocketId`	—
`Uri`	—
`AppDomain`	—

Event ID 3353 — SocketId:%1 to remote address %2 had a connection reset error.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SocketId:%1 to remote address %2 had a connection reset error.

Fields

Name	Description
`SocketId`	—
`Uri`	—
`AppDomain`	—

Event ID 3354 — Service security negotiation completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Service security negotiation completed.

Fields

Name	Description
`AppDomain`	—

Event ID 3355 — Security negotiation processing failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Security negotiation processing failed.

Fields

Name	Description
`AppDomain`	—

Event ID 3356 — Security verification succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Security verification succeeded.

Fields

Name	Description
`AppDomain`	—

Event ID 3357 — Security verification failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Security verification failed.

Fields

Name	Description
`AppDomain`	—

Event ID 3358 — Socket duplicated for %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Socket duplicated for %1.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 3359 — Security impersonation succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Security impersonation succeeded.

Fields

Name	Description
`AppDomain`	—

Event ID 3360 — Security impersonation failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Security impersonation failed.

Fields

Name	Description
`AppDomain`	—

Event ID 3361 — Http channel request aborted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http channel request aborted.

Fields

Name	Description
`AppDomain`	—

Event ID 3362 — Http channel response aborted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http channel response aborted.

Fields

Name	Description
`AppDomain`	—

Event ID 3363 — Http authentication failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http authentication failed.

Fields

Name	Description
`AppDomain`	—

Event ID 3364 — SharedListenerProxy registration started for uri '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SharedListenerProxy registration started for uri '%1'.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 3365 — SharedListenerProxy Register Stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SharedListenerProxy Register Stop.

Fields

Name	Description
`AppDomain`	—

Event ID 3366 — SharedListenerProxy register failed with status '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SharedListenerProxy register failed with status '%1'.

Fields

Name	Description
`Status`	—
`AppDomain`	—

Event ID 3367 — ConnectionPoolPreambleFailed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ConnectionPoolPreambleFailed.

Fields

Name	Description
`AppDomain`	—

Event ID 3368 — SslOnAcceptUpgradeStart

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SslOnAcceptUpgradeStart

Fields

Name	Description
`AppDomain`	—

Event ID 3369 — SslOnAcceptUpgradeStop

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SslOnAcceptUpgradeStop

Fields

Name	Description
`AppDomain`	—

Event ID 3370 — BinaryMessageEncoder started encoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

BinaryMessageEncoder started encoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3371 — MtomMessageEncoder started encoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

MtomMessageEncoder started encoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3372 — TextMessageEncoder started encoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

TextMessageEncoder started encoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3373 — BinaryMessageEncoder started decoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

BinaryMessageEncoder started decoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3374 — MtomMessageEncoder started decoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

MtomMessageEncoder started decoding  the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3375 — TextMessageEncoder started decoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

TextMessageEncoder started decoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 3376 — Http transport started receiving a message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http transport started receiving a message.

Fields

Name	Description
`AppDomain`	—

Event ID 3377 — SocketId:%1 read '%2' bytes read from '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SocketId:%1 read '%2' bytes read from '%3'.

Fields

Name	Description
`SocketId`	—
`Size`	—
`Endpoint`	—
`AppDomain`	—

Event ID 3378 — SocketId:%1 read '%2' bytes read from '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SocketId:%1 read '%2' bytes read from '%3'.

Fields

Name	Description
`SocketId`	—
`Size`	—
`Endpoint`	—
`AppDomain`	—

Event ID 3379 — SocketId:%1 writing '%2' bytes to '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SocketId:%1 writing '%2' bytes to '%3'.

Fields

Name	Description
`SocketId`	—
`Size`	—
`Endpoint`	—
`AppDomain`	—

Event ID 3380 — SocketId:%1 writing '%2' bytes to '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SocketId:%1 writing '%2' bytes to '%3'.

Fields

Name	Description
`SocketId`	—
`Size`	—
`Endpoint`	—
`AppDomain`	—

Event ID 3381 — SessionId:%1 acknowledgement sent.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SessionId:%1 acknowledgement sent.

Fields

Name	Description
`SessionId`	—
`AppDomain`	—

Event ID 3382 — SessionId:%1 reconnecting.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SessionId:%1 reconnecting.

Fields

Name	Description
`SessionId`	—
`AppDomain`	—

Event ID 3383 — SessionId:%1 faulted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SessionId:%1 faulted.

Fields

Name	Description
`SessionId`	—
`AppDomain`	—

Event ID 3384 — WindowsStreamSecurity initiating security upgrade.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WindowsStreamSecurity initiating security upgrade.

Fields

Name	Description
`AppDomain`	—

Event ID 3385 — Windows streaming security on accepting upgrade.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Windows streaming security on accepting upgrade.

Fields

Name	Description
`AppDomain`	—

Event ID 3386 — SocketId:%1 is aborting.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

SocketId:%1 is aborting.

Fields

Name	Description
`SocketId`	—
`AppDomain`	—

Event ID 3388 — HttpGetContext start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

HttpGetContext start.

Fields

Name	Description
`AppDomain`	—

Event ID 3389 — Client sending preamble start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client sending preamble start.

Fields

Name	Description
`AppDomain`	—

Event ID 3390 — Client sending preamble stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Client sending preamble stop.

Fields

Name	Description
`AppDomain`	—

Event ID 3391 — Http Message receive failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http Message receive failed.

Fields

Name	Description
`AppDomain`	—

Event ID 3392 — TransactionScope is being created with LocalIdentifier:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

TransactionScope is being created with LocalIdentifier:'%1' and DistributedIdentifier:'%2'.

Fields

Name	Description
`LocalId`	—
`Distributed`	—
`AppDomain`	—

Event ID 3393 — A streamed message was read by the encoder.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A streamed message was read by the encoder.

Fields

Name	Description
`AppDomain`	—

Event ID 3394 — A streamed message was written by the encoder.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A streamed message was written by the encoder.

Fields

Name	Description
`AppDomain`	—

Event ID 3395 — A message was written asynchronously by the encoder.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A message was written asynchronously by the encoder.

Fields

Name	Description
`AppDomain`	—

Event ID 3396 — BufferId:%1 completed writing '%2' bytes to underlying stream.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

BufferId:%1 completed writing '%2' bytes to underlying stream.

Fields

Name	Description
`BufferId`	—
`Size`	—
`AppDomain`	—

Event ID 3397 — A message was written asynchronously by the encoder.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A message was written asynchronously by the encoder.

Fields

Name	Description
`AppDomain`	—

Event ID 3398 — Pipe shared memory created at '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pipe shared memory created at '%1' .

Fields

Name	Description
`sharedMemoryName`	—
`AppDomain`	—

Event ID 3399 — NamedPipe '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

NamedPipe '%1' created.

Fields

Name	Description
`pipeName`	—
`AppDomain`	—

Event ID 3401 — Signature verification started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Signature verification started.

Fields

Name	Description
`AppDomain`	—

Event ID 3402 — Signature verification succeeded

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Signature verification succeeded

Fields

Name	Description
`AppDomain`	—

Event ID 3403 — Wrapped key decryption started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrapped key decryption started.

Fields

Name	Description
`AppDomain`	—

Event ID 3404 — Wrapped key decryption succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrapped key decryption succeeded.

Fields

Name	Description
`AppDomain`	—

Event ID 3405 — Encrypted data processing started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Encrypted data processing started.

Fields

Name	Description
`AppDomain`	—

Event ID 3406 — Encrypted data processing succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Encrypted data processing succeeded.

Fields

Name	Description
`AppDomain`	—

Event ID 3407 — Http message handler started processing the inbound request.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler started processing the inbound request.

Fields

Name	Description
`AppDomain`	—

Event ID 3408 — Http message handler started processing the inbound request asynchronously.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler started processing the inbound request asynchronously.

Fields

Name	Description
`AppDomain`	—

Event ID 3409 — Http message handler completed processing an inbound request.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler completed processing an inbound request.

Fields

Name	Description
`AppDomain`	—

Event ID 3410 — Http message handler is faulted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Http message handler is faulted.

Fields

Name	Description
`AppDomain`	—

Event ID 3411 — WebSocket connection timed out.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WebSocket connection timed out.

Fields

Name	Description
`AppDomain`	—

Event ID 3412 — Http message handler started processing the response.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler started processing the response.

Fields

Name	Description
`AppDomain`	—

Event ID 3413 — Http message handler started processing the response asynchronously.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler started processing the response asynchronously.

Fields

Name	Description
`AppDomain`	—

Event ID 3414 — Http message handler completed processing the response.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Http message handler completed processing the response.

Fields

Name	Description
`AppDomain`	—

Event ID 3415 — WebSocket connection request to '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocket connection request to '%1' send start.

Fields

Name	Description
`remoteAddress`	—
`AppDomain`	—

Event ID 3416 — WebSocketId:%1 connection request sent.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 connection request sent.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3417 — WebSocket connection accept start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocket connection accept start.

Fields

Name	Description
`AppDomain`	—

Event ID 3418 — WebSocketId:%1 connection accepted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 connection accepted.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3419 — WebSocket connection declined with status code '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WebSocket connection declined with status code '%1'

Fields

Name	Description
`errorMessage`	—
`AppDomain`	—

Event ID 3420 — WebSocket connection request failed: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WebSocket connection request failed: '%1'

Fields

Name	Description
`errorMessage`	—
`AppDomain`	—

Event ID 3421 — WebSocketId:%1 connection is aborted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WebSocketId:%1 connection is aborted.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3422 — WebSocketId:%1 writing '%2' bytes to '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 writing '%2' bytes to '%3'.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`byteCount`	—
`remoteAddress`	—
`AppDomain`	—

Event ID 3423 — WebSocketId:%1 asynchronous write stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 asynchronous write stop.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3424 — WebSocketId:%1 read start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 read start.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3425 — WebSocketId:%1 read '%2' bytes from '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 read '%2' bytes from '%3'.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`byteCount`	—
`remoteAddress`	—
`AppDomain`	—

Event ID 3426 — WebSocketId:%1 sending close message to '%2' with close status '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 sending close message to '%2' with close status '%3'.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`remoteAddress`	—
`closeStatus`	—
`AppDomain`	—

Event ID 3427 — WebSocketId:%1 sending close output message to '%2' with close status '%3'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 sending close output message to '%2' with close status '%3'.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`remoteAddress`	—
`closeStatus`	—
`AppDomain`	—

Event ID 3428 — WebSocketId:%1 connection closed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 connection closed.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`AppDomain`	—

Event ID 3429 — WebSocketId:%1 connection close message received with status '%2'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

WebSocketId:%1 connection close message received with status '%2'.

Fields

Name	Description
`WebSocketId`	—
`websocketId`	—
`closeStatus`	—
`AppDomain`	—

Event ID 3430 — Using the WebSocketVersion from a client WebSocket factory of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Using the WebSocketVersion from a client WebSocket factory of type '%1'.

Fields

Name	Description
`clientWebSocketFactoryType`	—
`AppDomain`	—

Event ID 3431 — Creating the client WebSocket with a factory of type '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Creating the client WebSocket with a factory of type '%1'.

Fields

Name	Description
`clientWebSocketFactoryType`	—
`AppDomain`	—

Event ID 3501 — ContractDescription with Name='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

ContractDescription with Name='%1' and Namespace='%2' has been inferred from WorkflowService.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 3502 — OperationDescription with Name='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

OperationDescription with Name='%1' in contract '%2' has been inferred from WorkflowService. IsOneWay=%3.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 3503 — A duplicate CorrelationQuery was found with Where='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

A duplicate CorrelationQuery was found with Where='%1'. This duplicate query will not be used when calculating correlation.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3507 — A service endpoint has been added for address '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

A service endpoint has been added for address '%1', binding '%2', and contract '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 3508 — TrackingProfile '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

TrackingProfile '%1' for the ActivityDefinitionId '%2' not found. Either the TrackingProfile is not found in the config file or the ActivityDefinitionId does not match.

Fields

Name	Description
`TrackingProfile`	—
`ActivityDefinitionId`	—
`AppDomain`	—

Event ID 3550 — Operation '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Operation '%1' cannot be performed at this time. Another attempt will be made when the service instance is ready to process this particular operation.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3551 — Operation '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Operation '%2' on service instance '%1' cannot be performed at this time. Another attempt will be made when the service instance is ready to process this particular operation.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 3552 — The throttle 'MaxPendingMessagesPerChannel' limit of '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The throttle 'MaxPendingMessagesPerChannel' limit of  '%1' was hit. To increase this limit, adjust the MaxPendingMessagesPerChannel property on BufferedReceiveServiceBehavior.

Fields

Name	Description
`limit`	—
`AppDomain`	—

Event ID 3553 — XamlServicesLoad start

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

XamlServicesLoad start

Fields

Name	Description
`AppDomain`	—

Event ID 3554 — XamlServicesLoad Stop

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

XamlServicesLoad Stop

Fields

Name	Description
`AppDomain`	—

Event ID 3555 — CreateWorkflowServiceHost start

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

CreateWorkflowServiceHost start

Fields

Name	Description
`AppDomain`	—

Event ID 3556 — CreateWorkflowServiceHost Stop

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

CreateWorkflowServiceHost Stop

Fields

Name	Description
`AppDomain`	—

Event ID 3557 — The call to EndCommit on the CommittableTransaction with id = '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The call to EndCommit on the CommittableTransaction with id = '%1' threw a TransactionException with the following message: '%2'.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 3558 — Service activation start

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Service activation start

Fields

Name	Description
`AppDomain`	—

Event ID 3559 — Service activation Stop

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Service activation Stop

Fields

Name	Description
`AppDomain`	—

Event ID 3560 — Available memory (bytes).

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Available memory (bytes): %1

Fields

Name	Description
`Available_memory_bytes`	Available memory (bytes).
`availableMemoryBytes`	—
`AppDomain`	—

Event ID 3561 — The service could not be activated.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Operational

Message

The service could not be activated. Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 3800 — The Routing Service is closing client '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is closing client '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3801 — Routing Service client '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Routing Service client '%1' has faulted.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3802 — A Routing Service one way message is completing.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A Routing Service one way message is completing.

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 3803 — The Routing Service failed while processing a message on the endpoint with address '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service failed while processing a message on the endpoint with address '%1'.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 3804 — The Routing Service is creating a client for endpoint: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is creating a client for endpoint: '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3805 — The Routing Service is configured with RouteOnHeadersOnly: %1, SoapProcessingEnabled: %2, EnsureOrderedDispatch: %3.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is configured with RouteOnHeadersOnly: %1, SoapProcessingEnabled: %2, EnsureOrderedDispatch: %3.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 3807 — A Routing Service request reply message is completing.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A Routing Service request reply message is completing.

Fields

Name	Description
`AppDomain`	—

Event ID 3809 — The Routing Service routed message with ID: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service routed message with ID: '%1' to %2 endpoint lists.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 3810 — A new RoutingConfiguration has been applied to the Routing Service.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A new RoutingConfiguration has been applied to the Routing Service.

Fields

Name	Description
`AppDomain`	—

Event ID 3815 — The Routing Service is processing a message with ID: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is processing a message with ID: '%1', Action: '%2', Inbound URL: '%3' Received in Transaction: %4.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`data4`	—
`AppDomain`	—

Event ID 3816 — The Routing Service is transmitting the message with ID: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is transmitting the message with ID: '%1' [operation %2] to '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 3817 — The Routing Service is committing a transaction with id: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is committing a transaction with id: '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3818 — Routing Service component %1 encountered a duplex callback exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Routing Service component %1 encountered a duplex callback exception.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 3819 — Routing Service message with ID: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Routing Service message with ID: '%1' [operation %2] moved to backup endpoint '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 3820 — The Routing Service created a new Transaction with id '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service created a new Transaction with id '%1' for processing message(s).

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3821 — The Routing Service failed while closing outbound client '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service failed while closing outbound client '%1'.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 3822 — The Routing Service is sending back a response message with Action '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is sending back a response message with Action '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3823 — The Routing Service is sending back a Fault response message with Action '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is sending back a Fault response message with Action '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3824 — The Routing Service is calling ReceiveContext.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is calling ReceiveContext.Complete for Message with ID: '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3825 — The Routing Service is calling ReceiveContext.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is calling ReceiveContext.Abandon for Message with ID: '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3826 — The Routing Service will send messages using existing transaction '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service will send messages using existing transaction '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3827 — The Routing Service failed while sending to '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service failed while sending to '%1'.

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 3828 — Routing Service MessageFilterTable Match Start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Routing Service MessageFilterTable Match Start.

Fields

Name	Description
`AppDomain`	—

Event ID 3829 — Routing Service MessageFilterTable Match Stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Routing Service MessageFilterTable Match Stop.

Fields

Name	Description
`AppDomain`	—

Event ID 3830 — The Routing Service is calling abort on channel: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service is calling abort on channel: '%1'.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 3831 — The Routing Service has handled an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service has handled an exception.

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 3832 — The Routing Service successfully transmitted Message with ID: '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The Routing Service successfully transmitted Message with ID: '%1 [operation %2] to '%3'.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—

Event ID 4001 — Transport listener session received with via '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Transport listener session received with via '%1'

Fields

Name	Description
`via`	—
`AppDomain`	—

Event ID 4002 — FailFastException.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

FailFastException.

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 4003 — Service start pipe error.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Service start pipe error.

Fields

Name	Description
`Endpoint`	—
`AppDomain`	—

Event ID 4008 — Session dispatch started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Session dispatch started.

Fields

Name	Description
`AppDomain`	—

Event ID 4010 — Session dispatch for '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Session dispatch for '%1' failed since pending session queue is full with '%2' pending items.

Fields

Name	Description
`Uri`	—
`count`	—
`AppDomain`	—

Event ID 4011 — Message queue register start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue register start.

Fields

Name	Description
`AppDomain`	—

Event ID 4012 — Message queue registration aborted with status:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue registration aborted with status:'%1' for uri:'%2'.

Fields

Name	Description
`Status`	—
`Uri`	—
`AppDomain`	—

Event ID 4013 — Message queue unregister succeeded for uri:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue unregister succeeded for uri:'%1'.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 4014 — Message queue registration for uri:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue registration for uri:'%1' failed with status:'%2'.

Fields

Name	Description
`Uri`	—
`Status`	—
`AppDomain`	—

Event ID 4015 — Message queue registration completed for uri '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue registration completed for uri '%1'.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 4016 — Message queue failed duplicating socket.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Message queue failed duplicating socket.

Fields

Name	Description
`AppDomain`	—

Event ID 4019 — MessageQueueDuplicatedSocketComplete

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

MessageQueueDuplicatedSocketComplete

Fields

Name	Description
`AppDomain`	—

Event ID 4020 — Tcp transport listener starting to listen on uri:'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Tcp transport listener starting to listen on uri:'%1'.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 4021 — Tcp transport listener listening.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Tcp transport listener listening.

Fields

Name	Description
`AppDomain`	—

Event ID 4022 — Error Code.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Error Code:%1

Fields

Name	Description
`Error_Code`	—
`hresult`	—
`AppDomain`	—

Event ID 4023 — Was closing all listener channel instances completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Was closing all listener channel instances completed.

Fields

Name	Description
`AppDomain`	—

Event ID 4024 — Error Code.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Error Code:%1

Fields

Name	Description
`Error_Code`	—
`hresult`	—
`AppDomain`	—

Event ID 4025 — Error Code.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Error Code:%1

Fields

Name	Description
`Error_Code`	—
`hresult`	—
`AppDomain`	—

Event ID 4026 — WAS Connected.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WAS Connected.

Fields

Name	Description
`AppDomain`	—

Event ID 4027 — WAS Disconnected.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WAS Disconnected.

Fields

Name	Description
`AppDomain`	—

Event ID 4028 — Pipe transport listener listening start on uri.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Pipe transport listener listening start on uri:%1.

Fields

Name	Description
`Uri`	—
`AppDomain`	—

Event ID 4029 — Pipe transport listener listening stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Pipe transport listener listening stop.

Fields

Name	Description
`AppDomain`	—

Event ID 4030 — Session dispatch succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Session dispatch succeeded.

Fields

Name	Description
`AppDomain`	—

Event ID 4031 — Session dispatch failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Session dispatch failed.

Fields

Name	Description
`AppDomain`	—

Event ID 4032 — WAS connection timed out.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

WAS connection timed out.

Fields

Name	Description
`AppDomain`	—

Event ID 4033 — Routing table lookup started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Routing table lookup started.

Fields

Name	Description
`AppDomain`	—

Event ID 4034 — Routing table lookup completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Routing table lookup completed.

Fields

Name	Description
`AppDomain`	—

Event ID 4035 — Pending session queue ratio: %1/%2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Pending session queue ratio: %1/%2

Fields

Name	Description
`Pending_session_queue_ratio`	—
`curr`	—
`max`	—
`AppDomain`	—

Event ID 4201 — End SQL command execution.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

End SQL command execution: %1

Fields

Name	Description
`End_SQL_command_execution`	—
`data1`	—
`AppDomain`	—

Event ID 4202 — Starting SQL command execution.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Starting SQL command execution: %1

Fields

Name	Description
`Starting_SQL_command_execution`	—
`data1`	—
`AppDomain`	—

Event ID 4203 — Failed to extend lock expiration, lock expiration already passed or the lock owner was deleted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Failed to extend lock expiration, lock expiration already passed or the lock owner was deleted. Aborting SqlWorkflowInstanceStore.

Fields

Name	Description
`AppDomain`	—

Event ID 4205 — Command failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Command failed: %1

Fields

Name	Description
`Command_failed`	—
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 4206 — Encountered exception %1 while attempting to unlock instance.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Encountered exception %1 while attempting to unlock instance.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 4207 — Giving up retrying a SQL command as the maximum number of retries have been performed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Giving up retrying a SQL command as the maximum number of retries have been performed.

Fields

Name	Description
`AppDomain`	—

Event ID 4208 — Retrying a SQL command due to SQL error number %1.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Retrying a SQL command due to SQL error number %1.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 4209 — Timeout trying to open a SQL connection.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Timeout trying to open a SQL connection. The operation did not complete within the allotted timeout of %1. The time allotted to this operation may have been a portion of a longer timeout.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 4210 — Caught SQL Exception number %1 message %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Caught SQL Exception number %1 message %2.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 4211 — Queuing SQL retry with delay %1 milliseconds.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Queuing SQL retry with delay %1 milliseconds.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 4212 — Timeout trying to acquire the instance lock.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Timeout trying to acquire the instance lock.  The operation did not complete within the allotted timeout of %1. The time allotted to this operation may have been a portion of a longer timeout.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 4213 — Detection of runnable instances failed due to the following exception

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Detection of runnable instances failed due to the following exception

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 4214 — Recovering instance locks failed due to the following exception

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Recovering instance locks failed due to the following exception

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 4600 — Message could not be logged as it exceeds the ETW event size

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Message could not be logged as it exceeds the ETW event size

Fields

Name	Description
`AppDomain`	—

Event ID 4801 — The DiscoveryClient created inside DiscoveryClientChannel failed to close and hence has been aborted.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The DiscoveryClient created inside DiscoveryClientChannel failed to close and hence has been aborted.

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 4802 — A ProtocolException was suppressed while closing the DiscoveryClient.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A ProtocolException was suppressed while closing the DiscoveryClient. This could be because a DiscoveryService is still trying to send response to the DiscoveryClient.

Fields

Name	Description
`SerializedException`	—
`AppDomain`	—

Event ID 4803 — The DiscoveryClient received a multicast suppression message from a DiscoveryProxy.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The DiscoveryClient received a multicast suppression message from a DiscoveryProxy.

Fields

Name	Description
`AppDomain`	—

Event ID 4804 — A %1 message with messageId='%2' was dropped by the DiscoveryClient because the corresponding %3 operation was completed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' was dropped by the DiscoveryClient because the corresponding %3 operation was completed.

Fields

Name	Description
`discoveryMessageName`	—
`messageId`	—
`discoveryOperationName`	—
`AppDomain`	—

Event ID 4805 — A %1 message with messageId='%2' was dropped because it had invalid content.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' was dropped because it had invalid content.

Fields

Name	Description
`messageType`	—
`messageId`	—
`AppDomain`	—

Event ID 4806 — A %1 message with messageId='%2' and relatesTo='%3' was dropped by the DiscoveryClient because either the corresponding %4 operation was completed ...

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' and relatesTo='%3' was dropped by the DiscoveryClient because either the corresponding %4 operation was completed or the relatesTo value is invalid.

Fields

Name	Description
`discoveryMessageName`	—
`messageId`	—
`relatesTo`	—
`discoveryOperationName`	—
`AppDomain`	—

Event ID 4807 — A discovery request message with messageId='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A discovery request message with messageId='%1' was dropped because it had an invalid ReplyTo address.

Fields

Name	Description
`messageId`	—
`AppDomain`	—

Event ID 4808 — A %1 message was dropped because it did not have any content.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message was dropped because it did not have any content.

Fields

Name	Description
`messageType`	—
`AppDomain`	—

Event ID 4809 — A %1 message was dropped because the message header did not contain the required MessageId property.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message was dropped because the message header did not contain the required MessageId property.

Fields

Name	Description
`messageType`	—
`AppDomain`	—

Event ID 4810 — A %1 message with messageId='%2' was dropped by the DiscoveryClient because it did not have the DiscoveryMessageSequence property.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' was dropped by the DiscoveryClient because it did not have the DiscoveryMessageSequence property.

Fields

Name	Description
`discoveryMessageName`	—
`messageId`	—
`AppDomain`	—

Event ID 4811 — A %1 message with messageId='%2' was dropped by the DiscoveryClient because the message header did not contain the required RelatesTo property.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' was dropped by the DiscoveryClient because the message header did not contain the required RelatesTo property.

Fields

Name	Description
`discoveryMessageName`	—
`messageId`	—
`AppDomain`	—

Event ID 4812 — A discovery request message with messageId='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A discovery request message with messageId='%1' was dropped because it did not have a ReplyTo address.

Fields

Name	Description
`messageId`	—
`AppDomain`	—

Event ID 4813 — A %1 message with messageId='%2' was dropped because it was a duplicate.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A %1 message with messageId='%2' was dropped because it was a duplicate.

Fields

Name	Description
`messageType`	—
`messageId`	—
`AppDomain`	—

Event ID 4814 — The discoverability of endpoint with EndpointAddress='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The discoverability of endpoint with EndpointAddress='%1' and ListenUri='%2' has been disabled.

Fields

Name	Description
`endpointAddress`	—
`listenUri`	—
`AppDomain`	—

Event ID 4815 — The discoverability of endpoint with EndpointAddress='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The discoverability of endpoint with EndpointAddress='%1' and ListenUri='%2' has been enabled.

Fields

Name	Description
`endpointAddress`	—
`listenUri`	—
`AppDomain`	—

Event ID 4816 — A Find operation was initiated in the DiscoveryClientChannel to discover endpoint(s).

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

A Find operation was initiated in the DiscoveryClientChannel to discover endpoint(s).

Fields

Name	Description
`AppDomain`	—

Event ID 4817 — The DiscoveryClientChannel failed to create the channel with a discovered endpoint with EndpointAddress='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The DiscoveryClientChannel failed to create the channel with a discovered endpoint with EndpointAddress='%1' and Via='%2'. The DiscoveryClientChannel will now attempt to use the next available discovered endpoint.

Fields

Name	Description
`endpointAddress`	—
`via`	—
`SerializedException`	—
`AppDomain`	—

Event ID 4818 — The DiscoveryClientChannel failed to open the channel with a discovered endpoint with EndpointAddress='.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The DiscoveryClientChannel failed to open the channel with a discovered endpoint with EndpointAddress='%1' and Via='%2'. The DiscoveryClientChannel will now attempt to use the next available discovered endpoint.

Fields

Name	Description
`endpointAddress`	—
`via`	—
`SerializedException`	—
`AppDomain`	—

Event ID 4819 — The DiscoveryClientChannel successfully discovered an endpoint and opened the channel using it.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The DiscoveryClientChannel successfully discovered an endpoint and opened the channel using it. The client is connected to a service using EndpointAddress='%1' and Via='%2'.

Fields

Name	Description
`endpointAddress`	—
`via`	—
`AppDomain`	—

Event ID 4820 — The SynchronizationContext has been reset to its original value of %1 by DiscoveryClientChannel.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The SynchronizationContext has been reset to its original value of %1 by DiscoveryClientChannel.

Fields

Name	Description
`synchronizationContextType`	—
`AppDomain`	—

Event ID 4821 — The SynchronizationContext has been set to null by DiscoveryClientChannel before initiating the Find operation.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The SynchronizationContext has been set to null by DiscoveryClientChannel before initiating the Find operation.

Fields

Name	Description
`AppDomain`	—

Event ID 5001 — DataContract serialize %1 with surrogates start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract serialize %1 with surrogates start.

Fields

Name	Description
`SurrogateType`	—
`AppDomain`	—

Event ID 5002 — DataContract serialize with surrogates stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract serialize with surrogates stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5003 — DataContract deserialize %1 with surrogates start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract deserialize %1 with surrogates start.

Fields

Name	Description
`SurrogateType`	—
`AppDomain`	—

Event ID 5004 — DataContract deserialize with surrogates stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract deserialize with surrogates stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5005 — ImportKnownTypes start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ImportKnownTypes start.

Fields

Name	Description
`AppDomain`	—

Event ID 5006 — ImportKnownTypes stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

ImportKnownTypes stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5007 — DataContract resolver resolving %1 start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract resolver resolving %1 start.

Fields

Name	Description
`TypeName`	—
`AppDomain`	—

Event ID 5008 — DataContract generate %1 writer for %2 start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract generate %1 writer for %2 start.

Fields

Name	Description
`Kind`	—
`TypeName`	—
`AppDomain`	—

Event ID 5009 — DataContract generate writer stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract generate writer stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5010 — DataContract generate %1 reader for %2 start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract generate %1 reader for %2 start.

Fields

Name	Description
`Kind`	—
`TypeName`	—
`AppDomain`	—

Event ID 5011 — DataContract generation stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

DataContract generation stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5012 — Json generate %1 reader for %2 start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Json generate %1 reader for %2 start.

Fields

Name	Description
`Kind`	—
`TypeName`	—
`AppDomain`	—

Event ID 5013 — Json reader generation stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Json reader generation stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5014 — Json generate %1 writer for %2 start.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Json generate %1 writer for %2 start.

Fields

Name	Description
`Kind`	—
`TypeName`	—
`AppDomain`	—

Event ID 5015 — Json generate writer stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Json generate writer stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5016 — Generate Xml serializable for '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Generate Xml serializable for '%1' start.

Fields

Name	Description
`DCType`	—
`AppDomain`	—

Event ID 5017 — Generate Xml serializable stop.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Generate Xml serializable stop.

Fields

Name	Description
`AppDomain`	—

Event ID 5203 — JsonMessageEncoder started decoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

JsonMessageEncoder started decoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 5204 — JsonMessageEncoder started encoding the message.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

JsonMessageEncoder started encoding the message.

Fields

Name	Description
`AppDomain`	—

Event ID 5402 — SecurityToken (type '%1' and id '%2') validation started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SecurityToken (type '%1' and id '%2') validation started.

Fields

Name	Description
`tokenType`	—
`tokenID`	—
`HostReference`	—
`AppDomain`	—

Event ID 5403 — SecurityToken (type '%1' and id '%2') validation succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SecurityToken (type '%1' and id '%2') validation succeeded.

Fields

Name	Description
`tokenType`	—
`tokenID`	—
`HostReference`	—
`AppDomain`	—

Event ID 5404 — SecurityToken (type '%1' and id '%2') validation failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

SecurityToken (type '%1' and id '%2') validation failed. %3

Fields

Name	Description
`tokenType`	—
`tokenID`	—
`errorMessage`	—
`HostReference`	—
`AppDomain`	—

Event ID 5405 — Retrieval of issuer name:%1 from tokenId:%2 succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Retrieval of issuer name:%1 from tokenId:%2 succeeded.

Fields

Name	Description
`issuerName`	—
`tokenID`	—
`HostReference`	—
`AppDomain`	—

Event ID 5406 — Retrieval of issuer name from tokenId:%1 failed.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Retrieval of issuer name from tokenId:%1 failed.

Fields

Name	Description
`tokenID`	—
`HostReference`	—
`AppDomain`	—

Event ID 5600 — Federation message processing started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Federation message processing started.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5601 — Federation message processing succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Federation message processing succeeded.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5602 — Creating federation message from form post started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Creating federation message from form post started.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5603 — Creating federation message from form post succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Creating federation message from form post succeeded.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5604 — Reading session token from session cookie started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Reading session token from session cookie started.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5605 — Reading session token from session cookie succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Reading session token from session cookie succeeded.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5606 — Principal setting from session token started.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Principal setting from session token started.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 5607 — Principal setting from session token succeeded.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Principal setting from session token succeeded.

Fields

Name	Description
`HostReference`	—
`AppDomain`	—

Event ID 39456 — Size of tracking record %1 exceeds maximum allowed by the ETW session for provider %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Size of tracking record %1 exceeds maximum allowed by the ETW session for provider %2

Fields

Name	Description
`RecordNumber`	—
`ProviderId`	—
`AppDomain`	—

Event ID 39457 — Tracking Record %1 raised to %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Tracking Record %1 raised to %2.

Fields

Name	Description
`data1`	—
`data2`	—
`AppDomain`	—

Event ID 39458 — Truncated tracking record %1 written to ETW session with provider %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Truncated tracking record %1 written to ETW session with provider %2. Variables/annotations/user data have been removed

Fields

Name	Description
`RecordNumber`	—
`ProviderId`	—
`AppDomain`	—

Event ID 39459 — Tracking data %1 extracted in activity %2.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Tracking data %1 extracted in activity %2.

Fields

Name	Description
`Data`	—
`Activity`	—
`AppDomain`	—

Event ID 39460 — The extracted argument/variable '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The extracted argument/variable '%1' is not serializable.

Fields

Name	Description
`name`	—
`AppDomain`	—

Event ID 57393 — AppDomain unloading.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

AppDomain unloading. AppDomain.FriendlyName %1, ProcessName %2, ProcessId %3.

Fields

Name	Description
`appdomainName`	—
`processName`	—
`processId`	—
`AppDomain`	—

Event ID 57394 — Handling an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Handling an exception.  Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57395 — An unexpected failure occurred.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

An unexpected failure occurred. Applications should not attempt to handle this error. For diagnostic purposes, this English message is associated with the failure: %1.

Fields

Name	Description
`data1`	—
`AppDomain`	—

Event ID 57396 — Throwing an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Throwing an exception. Source: %1. Exception details: %2

Fields

Name	Description
`data1`	—
`data2`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57397 — Unhandled exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Operational

Message

Unhandled exception.  Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57398 — The system hit the limit set for throttle 'MaxConcurrentInstances'.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

The system hit the limit set for throttle 'MaxConcurrentInstances'. Limit for this throttle was set to %1. Throttle value can be changed by modifying attribute 'maxConcurrentInstances' in serviceThrottle element or by modifying 'MaxConcurrentInstances' property on behavior ServiceThrottlingBehavior.

Fields

Name	Description
`limit`	—
`AppDomain`	—

Event ID 57399 — Wrote to the EventLog.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrote to the EventLog.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 57400 — Wrote to the EventLog.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrote to the EventLog.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 57401 — Wrote to the EventLog.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrote to the EventLog.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 57402 — Wrote to the EventLog.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrote to the EventLog.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 57403 — Wrote to the EventLog.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

Wrote to the EventLog.

Fields

Name	Description
`ExtendedData`	—
`AppDomain`	—

Event ID 57404 — Handling an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Handling an exception. Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57405 — Handling an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Operational

Message

Handling an exception. Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57406 — Handling an exception Exception details.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Handling an exception  Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57407 — Throwing an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Throwing an exception. Source: %1. Exception details: %2

Fields

Name	Description
`data1`	—
`data2`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57408 — Unhandled exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Operational

Message

Unhandled exception. Exception details: %1

Fields

Name	Description
`data1`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57409 — Throwing an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Throwing an exception. Source: %1. Exception details: %2

Fields

Name	Description
`data1`	—
`data2`	—
`SerializedException`	—
`AppDomain`	—

Event ID 57410 — Throwing an exception.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Analytic

Message

Throwing an exception. Source: %1. Exception details: %2

Fields

Name	Description
`data1`	—
`data2`	—
`SerializedException`	—
`AppDomain`	—

Event ID 62326 — The url '.

Provider: Microsoft-Windows-Application Server-Applications
Channel: Debug

Message

The url '%1' hosts XAML document with root element type '%2'. The HTTP handler type '%3' is picked to serve all the requests made to this url.

Fields

Name	Description
`data1`	—
`data2`	—
`data3`	—
`AppDomain`	—