none
Unified Messaging (UM) Subscriber Access Fails When Using Address Book Policies

    Question

  • Unified Messaging (UM) Subscriber Access  Fails When Using Address Book Policies

     

    We have a new deployment of Lync 2013 with LHP v2 and Exchange 2013 deployed using the hosting and multi-tenancy solutions and guidance documentation from Microsoft. We have completed validation of Exchange 2013 functionality and Lync functionality. All features work as expected except for subscriber access to the UM enabled mailbox. We have discovered through troubleshooting that when we remove the address book policy on a UM enabled mailbox this resolves the issue and we can access the subscriber access line and enter the users extension and PIN and then access voice mail, read emails, access contacts, and calendar. However when the Address Book Policy is enabled on the mailbox, which is recommended by Microsoft for LHPv2 deployments, we receive the following error on the Exchange 2013 Mailbox server:

     

    Log Name:      Application

    Source:        MSExchange Unified Messaging

    Date:          9/10/2013 1:36:32 PM

    Event ID:      1079

    Task Category: UMCore

    Level:         Warning

    Keywords:      Classic

    User:          N/A

    Computer:      XXXXXXXX.XXXX.XXXXXXXXXXXX.COM

    Description:

    The VoIP platform encountered an exception Microsoft.Exchange.UM.UMCommon.UmUserException: Access to Active Directory failed.

     

    Server stack trace:

       at Microsoft.Exchange.UM.UMCommon.Checksum..ctor(UMMailboxRecipient user, IPassword pwdImpl)

       at Microsoft.Exchange.UM.UMCommon.UmPasswordManager.Authenticate(EncryptedBuffer digits)

       at Microsoft.Exchange.UM.UMCore.GlobalActivityManager.DoLogon(UMSubscriber user, BaseUMCallSession vo, Boolean& successfulLogon)

       at Microsoft.Exchange.UM.UMCore.GlobalActivityManager.ExecuteAction(String action, BaseUMCallSession vo)

       at Microsoft.Exchange.UM.UMCore.FsmAction.Execute(ActivityManager m, BaseUMCallSession vo)

       at Microsoft.Exchange.UM.UMCore.HeavyBlockingOperation.Execute()

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.<>c__DisplayClass23.<.ctor>b__21()

       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)

       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

     

    Exception rethrown at [0]:

       at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)

       at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.HboDelegate.EndInvoke(IAsyncResult result)

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.EndOperation(IAsyncResult r)

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SubscriptionHelper.<>c__DisplayClass67`1.<>c__DisplayClass6a.<WrapCallback>b__66()

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.<CatchAndFireOnError>b__b() during the call with ID "<Names, phone number and contact information
    removed due to violation of code of conduct>
    ". This exception occurred at the Microsoft Exchange Speech Engine VoIP platform during an event-based asynchronous operation submitted by the server. The server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.

    Event Xml:

    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

      <System>

        <Provider Name="MSExchange Unified Messaging" />

        <EventID Qualifiers="32772">1079</EventID>

        <Level>3</Level>

        <Task>2</Task>

        <Keywords>0x80000000000000</Keywords>

        <TimeCreated SystemTime="2013-09-10T20:36:32.000000000Z" />

        <EventRecordID>247736</EventRecordID>

        <Channel>Application</Channel>

        <Computer> XXXXXXXX.XXXX.XXXXXXXXXXXX.COM.COM</Computer>

        <Security />

      </System>

      <EventData>

        <Data>Microsoft.Exchange.UM.UMCommon.UmUserException: Access to Active Directory failed.

     

    Server stack trace:

       at Microsoft.Exchange.UM.UMCommon.Checksum..ctor(UMMailboxRecipient user, IPassword pwdImpl)

       at Microsoft.Exchange.UM.UMCommon.UmPasswordManager.Authenticate(EncryptedBuffer digits)

       at Microsoft.Exchange.UM.UMCore.GlobalActivityManager.DoLogon(UMSubscriber user, BaseUMCallSession vo, Boolean&amp; successfulLogon)

       at Microsoft.Exchange.UM.UMCore.GlobalActivityManager.ExecuteAction(String action, BaseUMCallSession vo)

       at Microsoft.Exchange.UM.UMCore.FsmAction.Execute(ActivityManager m, BaseUMCallSession vo)

       at Microsoft.Exchange.UM.UMCore.HeavyBlockingOperation.Execute()

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.&lt;&gt;c__DisplayClass23.&lt;.ctor&gt;b__21()

       at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]&amp; outArgs)

       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

     

    Exception rethrown at [0]:

       at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)

       at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData&amp; msgData)

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.HboDelegate.EndInvoke(IAsyncResult result)

       at Microsoft.Exchange.UM.

    .&lt;&gt;c__DisplayClass67`1.&lt;&gt;c__DisplayClass6a.&lt;WrapCallback&gt;b__66()

       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.&lt;&gt;c__DisplayClassf.&lt;CatchAndFireOnError&gt;b__b()</Data>

        <Data><Names, phone number and contact information
    removed due to violation of code of conduct>
    </Data>

      </EventData>

    </Event>

     

    We opened a severity A case with Microsoft PSS (113082910702295) at the end of last month (8/29), but the PSS techs (listed below) we have been working with are extremely unresponsive taking a week to provide an update and only then indicating they've escalated the issue to senior members and the product group; however, it turns out escalation is lateral to another tier one tech. PSS is openly not responding to phone calls or requests on a severity A case which, without authorization, has been downgraded to severity C.

     

    This frustration with PSS is why we're turning to the community to see if others have seen this issue along with the hopes that someone at Microsoft actually cares about their customer and can put some pressure on PSS to actually work on this case. It seems calling the vendor is a dead end so our hope is someone out there has some suggestions on where we can go next.

     

    The techs involved are:

     

    Manager

    ===========

    <Names, phone number and contact information
    removed due to violation of code of conduct>

     

    Tech Leads

    ===========

    <Names, phone number and contact information
    removed due to violation of code of conduct>

     

    <Names, phone number and contact information
    removed due to violation of code of conduct>

     

    Due to Microsoft's behavior on this ticket we're starting to suspect that LHPv2 might not be production ready, especially if PSS cannot address an issue within a month. Are others experiencing this issue with LHPv2 or are we unique? Any ideas on how to resolve the issue are welcome. :)

     

    Thanks.




    Wednesday, September 25, 2013 12:09 AM

All replies