Unable to Enable or Disable Unified Messaging on any user Mailbox - HTTP status 405: Method Not Allowed. RRS feed

  • Question

  • Hello Team,

    We are running Exchange setup wherein UM is configured on Exchange 2016 server. When we try to access any Details of Existing User mailbox for UM or when we try to Enable or Disable the feature on the User mailbox we get the following error :

    Unified Messaging PIN info couldn't be retrieved for mailbox 'user@domain.com' : An error occurred while accessing the user's mailbox. Details: The request failed with HTTP status 405: Method Not Allowed.

    Tried creating a New user mailbox, the issue remains the same.

    Event's generated :

    The Microsoft Exchange Unified Messaging service on the Mailbox server encountered an error while trying to process the message with header file "C:\Program Files\Microsoft\Exchange Server\V15\UnifiedMessaging\voicemail\ff289b17-e02c-4be8-aab2-df1e87599c62.txt". Error details: "Microsoft.Exchange.UM.UMCommon.CDROperationException: An error occurred while accessing the Call Data Records. The request failed with HTTP status 405: Method Not Allowed. ---> System.Net.WebException: The request failed with HTTP status 405: Method Not Allowed.
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.Exchange.SoapWebClient.HttpAuthenticator.NetworkServiceHttpAuthenticator.AuthenticateAndExecute[T](CustomSoapHttpClientProtocol client, AuthenticateAndExecuteHandler`1 handler)
       at Microsoft.Exchange.UM.UMCommon.UMMailboxAccessorEwsBinding.InvokeWebServiceCommand(Func`1 function)
       at Microsoft.Exchange.UM.UMCommon.UMMailboxAccessorEwsBinding.CreateUMCallDataRecord(CreateUMCallDataRecordType request)
       at Microsoft.Exchange.UM.UMCommon.CrossServerMailboxAccess.EWSUMCallDataRecordAccessor.<>c__DisplayClass5.<CreateUMCallDataRecord>b__4()
       at Microsoft.Exchange.UM.UMCommon.UMMailboxAccessorEwsBinding.ExecuteEWSOperation(Action function, DiagnosticHelper tracer)
       --- End of inner exception stack trace ---

    Server stack trace: 
       at Microsoft.Exchange.UM.UMCommon.CrossServerMailboxAccess.EWSUMCallDataRecordAccessor.CheckForErrors(Exception e)
       at Microsoft.Exchange.UM.UMCommon.CrossServerMailboxAccess.EWSUMCallDataRecordAccessor.CheckResponse(Exception e, ResponseMessageType response)
       at Microsoft.Exchange.UM.UMCommon.CrossServerMailboxAccess.EWSUMCallDataRecordAccessor.CreateUMCallDataRecord(CDRData cdrData)
       at Microsoft.Exchange.UM.UMCore.CDRPipelineContext.PrepareUnProtectedMessage()
       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.UMCore.SynchronousPipelineStageBase.SynchronousWorkDelegate.EndInvoke(IAsyncResult result)
       at Microsoft.Exchange.UM.UMCore.SynchronousPipelineStageBase.EndSynchronousWork(IAsyncResult r)"


    Certificate subject name *.compasshousingalliance.org is not valid. UM local monitoring sip options probe will fail System.ArgumentException: The specified routing host name '*.compasshousingalliance.org' isn't valid    at Microsoft.Exchange.Data.Transport.RoutingHost..ctor(String address)    at Microsoft.Exchange.UM.UMCore.SipPeerManager.GetSipPeerFromUMCertificateSubjectName()


    UM can't save the Call Data Record message to the EDiscovery mailbox. More information "The number of call data record messages being processed in the Unified Messaging pipeline has exceeded the maximum limit. Please check whether the EDiscovery mailbox with DistinguishedName CN=SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9},OU=SystemMailboxOU,DC=cha,DC=compasshousingalliance,DC=org or MailboxDatabase CN=Mailbox Database 1216166907,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=cha,DC=compasshousingalliance,DC=org is down.".

    Kindly suggest or help !


    Binu Kumar
    Managing Director, Aarbin Technology Pvt Ltd.

    Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, July 18, 2018 6:21 AM


  • Checked and found Exchange version is running RTM 

    Exchange Server 2016 RTM

    October 1, 2015


    Applied Exchange 2016 CU10 and the issue is fixed. 

    Exchange Server 2016 CU10

    June 19, 2018



    Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, July 19, 2018 7:10 AM