Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2
Topic Last Modified: 2011-06-20
Microsoft Exchange Server 2010 Unified Messaging generates system events in Event Viewer so that you can troubleshoot and verify the performance of Unified Messaging system components, features, and services. Event Viewer tracks the following kinds of events in the following order based on importance:
- Error events
- Warning events
- Informational events
UM System Error and Events
The following table provides a list of Unified Messaging system events that you can use to troubleshoot and monitor Unified Messaging.
Unified Messaging system events
| Event ID | Category | Event type | Logging | Value or description | Class |
|---|---|---|---|---|---|
|
1000 |
UMWorkerProcess |
Information |
LogAlways |
The Unified Messaging Worker Process was started successfully on port "%1". |
System |
|
1001 |
UMWorkerProcess |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging Worker Process (UMWorkerProcess.exe) was unable to start. More information: %1. |
System |
|
1002 |
UMWorkerProcess |
Information |
LogAlways |
The Unified Messaging Worker Process has been stopped successfully. |
System |
|
1003 |
UMWorkerProcess |
Error |
LogAlways |
An unhandled exception occurred while the UM Worker Process (UMWorkerProcess.exe) was stopping. Exception details follow: %1 |
System |
|
1007 |
UMCore |
Information |
LogAlways |
The Unified Messaging server has ended a call with ID "%1" because the user at the far end disconnected. |
System |
|
1008 |
UMCore |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service failed to initialize because an exception occurred when it was loading the globcfg.xml configuration file or the finite state machine (FSM) files. To resolve this error, replace the globcfg.xml file or the FSM files with the default files located on the Exchange Server 2010 DVD. More information: "%1". |
System |
|
1009 |
UMCore |
Information |
LogAlways |
The telephone user interface is starting activity "%1" for the call with ID "%2". |
System |
|
1010 |
UMCore |
Information |
LogAlways |
The telephone user interface definitions were successfully loaded from the configuration file: "%1" |
System |
|
1011 |
UMCore |
Information |
LogAlways |
The telephone user interface activity "%1" will play the following prompts: "%2" |
System |
|
1014 |
UMCore |
Error |
LogAlways |
The Unified Messaging Worker Process (UMWorkerProcess.exe) encountered an unhandled exception "%1" during an incoming call with ID "%2". The call was disconnected. |
System |
|
1035 |
UMCore |
Error |
LogAlways |
The Unified Messaging server encountered an error when trying to access the mailbox for user "%1". Error: %2 Object: %3 |
System |
|
1037 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has started successfully. |
System |
|
1038 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service was unable to start. More information: "%1" |
System |
|
1039 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has been stopped successfully. |
System |
|
1040 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service could not be stopped. More information: "%1" |
System |
|
1041 |
UMService |
Error |
LogAlways |
The operating system was unable to create job object "%1" during the initialization of the Microsoft Exchange Unified Messaging service. Job objects allow multiple processes to be managed as a unit. The Microsoft Exchange Unified Messaging service was stopped. To resolve this error, first try restarting the Unified Messaging server. The Win32 exception error that was returned was: "%2" |
System |
|
1042 |
UMService |
Error |
LogAlways |
The operating system was unable to set properties on job object "%1" during the initialization of the Microsoft Exchange Unified Messaging service. A job object allows a group of processes to be managed as a unit. The Microsoft Exchange Unified Messaging service was stopped. To resolve this error, first try restarting the Unified Messaging server. The Win32 exception error that was returned was: "%2" |
System |
|
1043 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service was not able to start because the executable file "%1" for the Unified Messaging Worker Process does not exist. To resolve this issue, copy the default file located on the Exchange Server 2010 DVD into the \bin folder in the installation directory. |
System |
|
1044 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service failed to create an instance of the Unified Messaging Worker Process. %1 |
System |
|
1045 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service stopped because the Unified Messaging Worker Process exceeded the configured maximum number of consecutive crashes, %1. To resolve this error, restart the Microsoft Exchange Unified Messaging service. |
System |
|
1046 |
UMService |
Information |
LogAlways |
The Unified Messaging (UM) Worker Process has terminated. The state of the UM Worker Process is "%1". |
System |
|
1047 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has requested that a new Unified Messaging Worker Process be created. |
System |
|
1048 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging (UM) Worker Process because it was unable to get data from the old UM Worker Process. |
System |
|
1049 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process because the number of incoming calls ("%1") has exceeded the configured maximum, "%2". |
System |
|
1050 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process because the number of threads ("%1") exceeded the configured maximum, "%2". |
System |
|
1051 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process because the working set ("%1 MB") has exceeded the configured maximum: "%2 MB" |
System |
|
1052 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process. The previous Worker Process had been running since "%1", and reached its configured maximum age at "%2". |
System |
|
1053 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process because the number of health monitoring "heartbeats" missed ("%1") exceeded the configured maximum, "%2". |
System |
|
1055 |
UMService |
Information |
LogAlways |
The Unified Messaging Worker Process was terminated because the configured maximum lifetime was exceeded. |
System |
|
1056 |
UMService |
Information |
LogAlways |
The state of the Unified Messaging Worker Process has changed. Previous state = "%1". Current state = "%2". |
System |
|
1057 |
UMWorkerProcess |
Error |
LogAlways |
An unhandled exception occurred in a Unified Messaging Worker Process: "%1". |
System |
|
1058 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service was not able to redirect the call with ID "%1" to an available Unified Messaging Worker Process. |
System |
|
1059 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has terminated the Unified Messaging Worker Process because a control channel could not be established. |
System |
|
1074 |
UMService |
Error |
LogAlways |
The Unified Messaging server failed to submit the message to the Hub Transport server using header file "%1". The header file was moved to "%2". Make sure that your antivirus software is not modifying the header files in the voice mail folder. Error "%3". |
System |
|
1077 |
UMCore |
Information |
LogAlways |
The Unified Messaging server has received a request to disconnect the user "%1" on the call with ID "%2". |
System |
|
1078 |
UMCore |
Warning |
LogAlways |
The Unified Messaging Worker Process is attempting to recover from an exception "%1" that was encountered during a call with ID "%2". |
System |
|
1079 |
UMCore |
Warning |
LogAlways |
The VoIP platform encountered an exception "%1" during the call with ID "%2". This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the Unified Messaging server. The Unified Messaging server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support. |
System |
|
1083 |
UMClientAccess |
Warning |
LogAlways |
The Unified Messaging Web service was unable to process a "%1" request for user "%2". The error was "%3". |
System |
|
1084 |
UMCore |
Information |
LogAlways |
The call with ID "%1" ended because the Unified Messaging server disconnected. |
System |
|
1090 |
UMService |
Information |
LogAlways |
The IP gateway at %1 responded promptly to a PING request. |
System |
|
1091 |
UMService |
Warning |
LogAlways |
The Unified Messaging server was unable to issue a Session Initiation Protocol (SIP) Option request to the IP gateway or IP PBX named "%1". The operational status of the IP gateway or IP PBX will not be sent to the server. The error received was "%2". |
System |
|
1092 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has created a new Unified Messaging Worker Process because the temporary directory size reached "%1" MB, which exceeded the maximum specified size, which is "%2" MB. |
System |
|
1103 |
UMService |
Error |
LogAlways |
XML schema validation failed for file "%1" at line "%2". The error was "%3". A Unified Messaging configuration data file has been modified and the new changes do not match the expected schema. To resolve this issue, undo any recent changes you have made to the file or replace the file on the Unified Messaging server with the file of the same name located on the Exchange 2010 DVD. |
System |
|
1104 |
UMService |
Warning |
LogAlways |
The Microsoft Exchange Unified Messaging service was unable to read the Unified Messaging Worker Process retire time from the configuration data. The Unified Messaging Worker Process retire time is being set to the default value, which is "%1". Reason: "%2" |
System |
|
1105 |
UMWorkerProcess |
Warning |
LogAlways |
The Unified Messaging server could not find a UM IP gateway that allows outgoing calls. |
System |
|
1112 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service will attempt to use a certificate with the following details: IssuerName = "%1", SerialNumber = "%2", Thumbprint = "%3", IsSelfSigned = "%4", NotValidAfter = "%5". The path to this certificate is "%6". |
System |
|
1113 |
UMService |
Warning |
LogPeriodic |
The Unified Messaging server failed to exchange the required certificates with a UM IP gateway to enable Transport Layer Security (TLS) for an incoming call. More information: "%1". |
System |
|
1114 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service will attempt to start in secured mode. |
System |
|
1115 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service will attempt to start in unsecured mode. |
System |
|
1116 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service has received notification that a new Transport Layer Security (TLS) certificate must be used. The Microsoft Exchange Unified Messaging service will not process any new calls from an IP gateway until the new TLS certificate can be used. |
System |
|
1117 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service was configured to use a new certificate and used the new certificate successfully. |
System |
|
1118 |
UMService |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service has encountered a problem trying to use the newly assigned certificate for Transport Layer Security (TLS). The Microsoft Exchange Unified Messaging service was stopped. To resolve this issue, replace the current certificate with another one. The exception error was "%1". |
System |
|
1119 |
UMService |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service created a new Unified Messaging Worker Process so that a new certificate can be used. |
System |
|
1120 |
UMService |
Warning |
LogAlways |
The certificate that is used to establish secure communication with an IP gateway using Transport Layer Security (TLS) is nearing its expiration date. By default, this event is first logged 30 days before the certificate expires, and then logged one time each day until the certificate is replaced. If the certificate that is stored on the Unified Messaging server is not replaced before it expires, the Microsoft Exchange Unified Messaging service will stop, and the Unified Messaging server will not be able to process any calls. To resolve this issue, install a new certificate on the Unified Messaging server and the IP gateways that are being used by the Unified Messaging server. |
System |
|
1124 |
UMService |
Warning |
LogAlways |
No IP gateways were found for the Microsoft Exchange Unified Messaging service. |
System |
|
1125 |
UMClientAccess |
Information |
LogAlways |
The Microsoft Exchange Unified Messaging service will attempt to use a certificate with the following information: IssuerName ="%1", SerialNumber = "%2", Thumbprint = "%3", IsSelfSigned = "%4" , NotValidAfter = "%5" |
System |
|
1126 |
UMWorkerProcess |
Warning |
LogPeriodic |
The Unified Messaging server failed to exchange the required certificates to enable Transport Layer Security (TLS) with an IP gateway. More information: "%1". |
System |
|
1127 |
UMWorkerProcess |
Warning |
LogAlways |
The Audio Compression Manager failed to convert from the audio format "%1" to audio format "%2": "%3". If this conversion continues to fail, you can either change the audio codec setting on the UM dial plan or change the audio codec setting on the user's UM-enabled mailbox. |
System |
|
1133 |
UMCore |
Error |
LogAlways |
Unified Messaging detected a corrupted custom greeting "%1" for user "%2". The user's custom greeting will be deleted and the Unified Messaging server will use a default greeting until the user records another custom greeting. |
System |
|
1138 |
UMCore |
Error |
LogAlways |
The Microsoft Exchange Unified Messaging service failed to start. The service was not able to create and register the Simple Mail Transfer Protocol (SMTP) service principal name (SPN) for the Unified Messaging server. The Win32 error code returned was "%1". |
System |
|
1142 |
UMCore |
Information |
LogAlways |
"%1" active calls that were associated with remote end point "%2" were disconnected. An administrator with the appropriate permissions chose to disable all incoming calls immediately on Unified Messaging server "%3". |
System |
|
1143 |
UMCore |
Information |
LogAlways |
"%1" active calls have been disabled on the Unified Messaging server. An administrator with the appropriate permissions chose to disable all incoming calls immediately. |
System |
|
1147 |
UMCore |
Warning |
LogAlways |
The Unified Messaging server was unable to retrieve the IP address for IP gateway "%1". |
System |
|
1148 |
UMService |
Warning |
LogAlways |
The Unified Messaging server could not obtain a DNS record for the following hosts: "%1". Verify that your UM IP gateway and DNS server have been configured correctly. |
System |
|
1149 |
UMWorkerProcess |
Warning |
LogAlways |
The Unified Messaging server could not locate a DNS record for the following hosts: "%1". To resolve this issue, verify that your UM IP gateways and your DNS server are configured correctly. |
System |
|
1151 |
UMService |
Warning |
LogPeriodic |
The Session Initiation Protocol (SIP) stack that is installed on the Unified Messaging server has encountered an unhandled exception. More information: "%1". |
System |
|
1152 |
UMCore |
Warning |
LogAlways |
The Unified Messaging server has received a SIP header that is not valid from an incoming call with ID "%1". Header details follow: "%2" |
System |
|
1159 |
UMCore |
Warning |
LogAlways |
The call with ID "%1" was disconnected by the Unified Messaging server because of a system error. |
System |
|
1165 |
UMWorkerProcess |
Warning |
LogAlways |
No IP gateways were found for the Microsoft Exchange Unified Messaging service. |
System |
|
1166 |
UMWorkerProcess |
Warning |
LogAlways |
The Unified Messaging server encountered an error while trying to access the Active Directory directory service to determine the UM IP gateways that are associated with this server. More information: "%1" |
System |
|
1167 |
UMService |
Warning |
LogAlways |
The Unified Messaging server encountered an error while trying to access the Active Directory directory service to determine the UM IP gateways that are associated with this server. More information: "%1" |
System |
|
1168 |
UMCallData |
Information |
LogAlways |
Call data: %1 |
System |
|
1174 |
UMWorkerProcess |
Warning |
LogAlways |
An error occurred while the Unified Messaging server was performing the following operation: "%1" for user "%2". "%3" |
System |
|
1175 |
UMCore |
Warning |
LogAlways |
The UM IP gateways "%1" and "%2" cannot be configured with the same IP address. Check your UM IP gateway and DNS server configuration. |
System |
|
1176 |
UMCore |
Warning |
LogAlways |
UM dial plan "%2" does not include the following dial groups "%1". |
System |
|
1400 |
UMService |
Warning |
LogPeriodic |
The IP gateway or IP PBX did not respond to a PING request from the Unified Messaging server. The error code that was returned is "%2" and the error text is "%3". |
System |