This document describes a problem encountered when the Unity Connection Single Inbox feature is configured so that it works with Microsoft Exchange 2003 and also provides possible solutions to the problem.
Cisco recommends that you have knowledge of these topics:
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Once you configure the Single Inbox feature so that Cisco Unity Connection works with Microsoft Exchange 2003, you might notice that messages are not delivered to Exchange. The tests for Unified Messaging Services "account" and "user" pass, but if you review the Connection Mailbox Sync traces you might see this message:
HTTP 500 - Internal server error
Event Type: ErrorEvent Source: MSExchangeISEvent Category: GeneralEvent ID: 9667In addition, these events are also possible: 9666, 9667, 9668, and 9669. These events are received when "Named Properties" or "Replica Identifiers" are depleted for an Exchange database. For a possible solution, refer to this Microsoft Article.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
26-Jun-2013 |
Initial Release |