none
Mac and OOF broken after SP2 install, Lots of ASP.NEt event 1309 "IndexOutOfRangeException" in application eventlog

    Question

  • After installing Exchangee 2010 SP2 on my front end servers, the application logs are littered with the message below;

    Users are reporting they can not access Out of Office from outlook and Mac users appear to not be able to connect at all.

    Any tips / hints to resolve this ?

     

     

    Log Name:      Application
    Source:        ASP.NET 2.0.50727.0
    Date:          12/18/2011 4:10:11 PM
    Event ID:      1309
    Task Category: Web Event
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      cas-fqdn
    Description:
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 12/18/2011 4:10:11 PM
    Event time (UTC): 12/18/2011 9:10:11 PM
    Event ID: 0e2872d3353547dc9b1500ddfb1ef737
    Event sequence: 1384
    Event occurrence: 299
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/1/ROOT/EWS-1-129687140985834513
        Trust level: Full
        Application Virtual Path: /EWS
        Application Path: C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\
        Machine name: CAS-NETBIOSNAME
     
    Process information:
        Process ID: 5220
        Process name: w3wp.exe
        Account name: NT AUTHORITY\SYSTEM
     
    Exception information:
        Exception type: IndexOutOfRangeException
        Exception message: Index was outside the bounds of the array.
     
    Request information:
        Request URL: https://cas-fqdn:443/EWS/Exchange.asmx
        Request path: /EWS/Exchange.asmx
        User host address: 192.168.46.58
        User: DOMAIN\username
        Is authenticated: True
        Authentication Type: NTLM
        Thread account name: NT AUTHORITY\SYSTEM
     
    Thread information:
        Thread ID: 15
        Thread account name: NT AUTHORITY\SYSTEM
        Is impersonating: False
        Stack trace:    at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.SetBugdetSnapshotResourceInfo(String budgetResourcesString)
       at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.FetchThrottlingData()
       at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.Commit()
       at Microsoft.Exchange.Services.Global.Application_EndRequest(Object sender, EventArgs e)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
     
     
    Custom event details:

    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="ASP.NET 2.0.50727.0" />
        <EventID Qualifiers="32768">1309</EventID>
        <Level>3</Level>
        <Task>3</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2011-12-18T21:10:11.000000000Z" />
        <EventRecordID>413269</EventRecordID>
        <Channel>Application</Channel>
        <Computer>CAS-FQDN</Computer>
        <Security />
      </System>
      <EventData>
        <Data>3005</Data>
        <Data>An unhandled exception has occurred.</Data>
        <Data>12/18/2011 4:10:11 PM</Data>
        <Data>12/18/2011 9:10:11 PM</Data>
        <Data>0e2872d3353547dc9b1500ddfb1ef737</Data>
        <Data>1384</Data>
        <Data>299</Data>
        <Data>0</Data>
        <Data>/LM/W3SVC/1/ROOT/EWS-1-129687140985834513</Data>
        <Data>Full</Data>
        <Data>/EWS</Data>
        <Data>C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\</Data>
        <Data>CAS-NETBIOS-Name</Data>
        <Data>
        </Data>
        <Data>5220</Data>
        <Data>w3wp.exe</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>IndexOutOfRangeException</Data>
        <Data>Index was outside the bounds of the array.</Data>
        <Data>https://cas-server-fqdn:443/EWS/Exchange.asmx</Data>
        <Data>/EWS/Exchange.asmx</Data>
        <Data>192.168.46.58</Data>
        <Data>username</Data>
        <Data>True</Data>
        <Data>NTLM</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>15</Data>
        <Data>NT AUTHORITY\SYSTEM</Data>
        <Data>False</Data>
        <Data>   at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.SetBugdetSnapshotResourceInfo(String budgetResourcesString)
       at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.FetchThrottlingData()
       at Microsoft.Exchange.Diagnostics.RequestDetailsLoggerBase.Commit()
       at Microsoft.Exchange.Services.Global.Application_EndRequest(Object sender, EventArgs e)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&amp; completedSynchronously)
    </Data>
      </EventData>
    </Event>

    Sunday, December 18, 2011 9:29 PM

Answers

  • The following workaround fixed the issue for me;

    1) Using Exchange Management Console; go into the properties of each mailbox database that contains special characters in it's name and change the name of the database to avoid round brackets (dash and space are ok, round brackets are especially bad)
    2) Using "Services" in Server manager on mailbox servers, restart the "Microsoft Exchange Throttling" service
    3) Using "IIS management" on Client Access servers, recycle the "MSExchangeServiecsAppPool"

    and to quote from Hitchhiker's Guide to the Galaxy: "Normality has been restored."

    • Marked as answer by adenhaan Wednesday, January 11, 2012 10:54 PM
    Wednesday, January 11, 2012 10:29 PM

All replies

  • Hi adenhaan,

    Seems like some other partners have the same issue. And the issue has been already researched.

    Exchange 2010 SP2 IndexOutOfRangeException

    http://social.technet.microsoft.com/Forums/da-DK/exchange2010/thread/88ddaf28-de7a-4048-af27-4972b11a212a

    However, resetting EWS VD is worthing trying.

    Server Configuration->Client Access->Actions->Reset Virtual Directory...

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Frank Wang

    TechNet Community Support

    Monday, December 19, 2011 8:24 AM
  • Frank, Thanks for link, It indeed appears that I am not alone. Resetting VD doesn't really help / make the error messages go away (maybe some temporary relief for brief moment but hard to tell with so many users).

    The bottom line of that linked article is : wait for fix.

    Do you concur ?

    Monday, December 19, 2011 2:29 PM
  • Hi adenhaan,

    Sorry for the inconvenience. Due to the urgence, I would suggest you make a call to PSS directly. If it is confirmed to be a bug, you won't be charged.

    http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone


    Frank Wang

    TechNet Community Support

    Tuesday, December 20, 2011 1:59 AM
  • Opened case with PSS.

    All client functions that are relying on EWS are affected;

    Outlook 2007/2010: Free Busy, OOF

    Oulook 2011 for mac : sending email (sometimes fails, sometimes sends duplicates), Free / busy, OOF

    only clients that are not affected are OWA and Activesync.

     

    Wednesday, December 21, 2011 12:19 AM
  • Known issue, fix in progress.
    Saturday, December 24, 2011 8:15 PM
  • xC0000005, Thanks for update / confirmation. Will look forward to getting hotfix through my open Case.
    Sunday, December 25, 2011 6:33 PM
  • Known issue, fix in progress.


    Is there an update on this issue?

    I currently have a client down/seriously degraded because of it. I have a PSS case open but they are giving me a run around and not even really acknowledging that it’s a known bug.

    Wednesday, January 04, 2012 9:56 PM
  • Last update on my PSS case was on December 29th;

    "We are consolidating a few other cases with the same symptom and have escalated to the proper group for traction. We are still testing the fix though. I’ve let the team know that you are willing to try out a private hotfix or an interim update, so hopefully we’ll have something for you soon!"

    Time goes by so slowly for those who wait

    Monday, January 09, 2012 9:15 PM
  • I've posted a response to this issue in the following thread in another MS Exchange Forum, please take a look. I'll post an update there as well, as soon as one is available. Thanks for your patience.

    http://social.technet.microsoft.com/Forums/da-DK/exchange2010/thread/88ddaf28-de7a-4048-af27-4972b11a212a


    Sr. Program Manager, Product Quality, Exchange Client Access Server
    Tuesday, January 10, 2012 10:47 PM
  • The following workaround fixed the issue for me;

    1) Using Exchange Management Console; go into the properties of each mailbox database that contains special characters in it's name and change the name of the database to avoid round brackets (dash and space are ok, round brackets are especially bad)
    2) Using "Services" in Server manager on mailbox servers, restart the "Microsoft Exchange Throttling" service
    3) Using "IIS management" on Client Access servers, recycle the "MSExchangeServiecsAppPool"

    and to quote from Hitchhiker's Guide to the Galaxy: "Normality has been restored."

    • Marked as answer by adenhaan Wednesday, January 11, 2012 10:54 PM
    Wednesday, January 11, 2012 10:29 PM
  • Thank you for a help!!!

    Weird brackets can be that dangeours.


    ---------- Ondrej Zilinec - Cievo ----------

    Monday, March 26, 2012 11:34 AM