Unified Messaging Administrative Errors and Events
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
Microsoft Exchange Server 2007 Unified Messaging (UM) generates administrative events in Event Viewer so that you can troubleshoot and verify the performance of UM administrative 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 Administrative Error and Events
Table 1 provides a list of the UM administrative events that you can use to troubleshoot and monitor Unified Messaging.
Table 1 Administrative events
| Event ID | Category | Event type | Logging | Value or description | Class |
|---|---|---|---|---|---|
1015 |
UMManagement |
Information |
LogAlways |
User "%1" has been successfully enabled for Unified Messaging. |
Administrative |
1016 |
UMManagement |
Information |
LogAlways |
User "%1" has been disabled for Unified Messaging. |
Administrative |
1017 |
UMManagement |
Information |
LogAlways |
The Unified Messaging mailbox for UM-enabled user "%1" has been successfully unlocked. |
Administrative |
1018 |
UMManagement |
Information |
LogAlways |
The Outlook Voice Access PIN for user "%1" has been changed. |
Administrative |
1060 |
UMManagement |
Information |
LogAlways |
A new UM dial plan named "%1" was created. |
Administrative |
1061 |
UMManagement |
Information |
LogAlways |
A new UM IP gateway named "%1" with IP address "%2" has been created. |
Administrative |
1062 |
UMManagement |
Information |
LogAlways |
A new Unified Messaging hunt group named "%1" has been created with pilot identifier "%2" and is associated with UM dial plan "%3". |
Administrative |
1063 |
UMManagement |
Information |
LogAlways |
The dial plan named "%1" has been removed. |
Administrative |
1064 |
UMManagement |
Information |
LogAlways |
IP gateway "%1", which has IP address "%2", has been removed. |
Administrative |
1065 |
UMManagement |
Information |
LogAlways |
The UM hunt group "%1" with the pilot identifier "%2" that is associated with UM dial plan "%3" has been removed. |
Administrative |
1066 |
UMManagement |
Information |
LogAlways |
Unified Messaging server "%1" has been enabled. |
Administrative |
1067 |
UMManagement |
Information |
LogAlways |
The UM IP gateway "%1" with IP address "%2" has been enabled. |
Administrative |
1068 |
UMManagement |
Information |
LogAlways |
The Unified Messaging server named "%1" has been disabled. |
Administrative |
1069 |
UMManagement |
Information |
LogAlways |
The Unified Messaging IP gateway "%1" with the IP address "%2" has been disabled. |
Administrative |
1070 |
UMManagement |
Information |
LogAlways |
A new UM auto attendant named "%1" was created and associated with UM dial plan "%2". |
Administrative |
1071 |
UMManagement |
Information |
LogAlways |
The UM auto attendant named "%1" has been enabled. |
Administrative |
1072 |
UMManagement |
Information |
LogAlways |
The auto attendant named "%1" has been disabled. |
Administrative |
For More Information
For more information about performance objects and counters that are available for Unified Messaging, see Performance Counter Reference for Unified Messaging.
For more information about how to troubleshoot a Unified Messaging server, see Unified Messaging Server Issues.
For more information about other errors and events for Unified Messaging, see Unified Messaging Errors and Events Reference.