none
EWS is not working correctly on single CAS server in NLB cluster RRS feed

  • Question

  • Hi guys, 

    we have BES 5.0.4 MR3 with Exchange 2007 SP3 UR10. There are 2 CAS servers in NLB. 

    EWS is configured based on KB20157 (http://www.blackberry.com/btsc/KB20157). besadmin account has ExtendedRights ms-Exch-EPI-May-Impersonate, ms-Exch-EPI-Impersonation on mail server and ms-Exch-EPI-Impersonation on each CAS in NLB cluster. Windows authentication for EWS folder and correct permissions for besadmin are set up. 

    Problem is: SoapAction=GetItem gives error 500 when besadmin account connects to EWS on CAS2. 
    As the result BB users don't receive meeting request on her devices only when BES is using EWS from second CAS server (CAS2) 

    In MAGT: 

    rQueuedStateRecord - COM Exception: Code = 80131501, WCode = 0000, Code meaning = Unknown error 0x80131501, Source = System.Web.Services 
    [30588] (06/07 11:45:07.388):{0x185C} {user2@company.com} EwsOperations::FilterQueuedStateRecord - Description = An internal server error occurred. 
    [30587] (06/07 11:45:07.404):{0x17F0} {user3@company.com} EwsOperations::FilterQueuedStateRecord - COM Exception: Code = 80131501, WCode = 0000, Code meaning = Unknown error 0x80131501, Source = System.Web.Services 
    [30588] (06/07 11:45:07.404):{0x17F0} {user3@company.com} EwsOperations::FilterQueuedStateRecord - Description = An internal server error occurred. 

    With IE from BES I can connect to https://<cas server>/ews/exchange.asmx to both CAS servers by name and by cluster name. 

    I thought that that such errors might occur after recent UR10 installation, but both CAS are running the same Exchange version. 

    When I remove second CAS from NLB and CAS1 becomes primary node, eveything works fine. 

    I've recreated EWS directory on CAS2 Remove-WebServicesVirtualDirectory/New-WebServicesVirtualDirectory CMDlets, however, I still have errors when my besadmin account accesses EWS directory on CAS2: 

    2013-06-10 09:45:57 10.xx.1.19 POST /EWS/Exchange.asmx SoapAction=GetItem;Version=1;RpcC=67;RpcL=405;LdapC=7;LdapL=16; 443 domain.local\besadmin 10.xx.1.10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4234) 500 0 0 670 

    Important this is, Only Getitem doesn't work. Everything else seems ok. 

    2013-06-10 09:45:57 10.xx.1.19 POST /EWS/Exchange.asmx SoapAction=ConvertId;Version=1;RpcC=0;RpcL=0;LdapC=8;LdapL=32; 443 domain.local\besadmin 10.xx.1.10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4234) 200 0 0 62 
    2013-06-10 09:45:57 10.xx.1.19 POST /EWS/Exchange.asmx SoapAction=FindItem;Version=1;RpcC=12;RpcL=62;LdapC=6;LdapL=31; 443 domain.local\besadmin 10.xx.1.10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4234) 200 0 0 93 
    2013-06-10 09:45:57 10.xx.1.19 POST /EWS/Exchange.asmx SoapAction=ConvertId;Version=1;RpcC=0;RpcL=0;LdapC=5;LdapL=15; 443 domain.local\besadmin 10.xx.1.10 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.4234) 200 0 0 15

    • Edited by anazarov Monday, June 10, 2013 11:08 AM
    Monday, June 10, 2013 11:06 AM

Answers

  • Hi

    Performance counters are corrupted, this dependency will cause a GetItem call made to Exchange Web Services to fail.

    You can follow below KB to Rebuild the Windows Performance Counter Library values on the Client Access Server(s).

    http://support.microsoft.com/kb/2264110

    Cheers


    Zi Feng
    TechNet Community Support

    • Marked as answer by anazarov Tuesday, June 11, 2013 7:28 AM
    Tuesday, June 11, 2013 7:17 AM
    Moderator

All replies

  • Hi

    Performance counters are corrupted, this dependency will cause a GetItem call made to Exchange Web Services to fail.

    You can follow below KB to Rebuild the Windows Performance Counter Library values on the Client Access Server(s).

    http://support.microsoft.com/kb/2264110

    Cheers


    Zi Feng
    TechNet Community Support

    • Marked as answer by anazarov Tuesday, June 11, 2013 7:28 AM
    Tuesday, June 11, 2013 7:17 AM
    Moderator
  • Exactly. Just posting this solution to all my opened threads on forums. Thanks!

    Issue was caused by Performance Counters corruption. "Microsoft Exchange Server 2007 Service Pack 2 introduces a dependency that requires reading the value of a performance counter.  If the performance counters are corrupted, this dependency will cause a GetItem call made to Exchange Web Services to fail."

    Resolution: http://support.microsoft.com/kb/2264110


    Tuesday, June 11, 2013 7:28 AM