Ask a questionAsk a question
 

QuestionIMAP issues in Exchange 2010 RC

  • Thursday, August 27, 2009 8:37 AMJoakim Gyllstedt Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The IMAP service stops responding and generates the following error in eventlog:

    "Process Microsoft.Exchange.Imap4.exe (PopImap) (PID=6440). A budget charge was encountered that exceeded the limit of '5.32811666666667' minutes.  Budget Owner: 'Sid~[DOMAIN]\[USERNAME]~IMAP~False', Component: 'IMAP', CostType: 'CAS'."

    Does anyone have a clue what this means?

    Both exchange server and domain controller is running Windows Server 2008 R2 RTM.
    Joakim Gyllstedt C# MCP

All Replies

  • Thursday, September 03, 2009 5:24 PMIvan Vovk Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The very same issue with 2010 RC:

    Log Name: Application
    Source: MSExchange ADAccess
    Date: 9/3/2009 4:53:31 AM
    Event ID: 2917
    Task Category: General
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: EXCAS-E2.mydomain.local
    Description:
    Process Microsoft.Exchange.Imap4.exe (PopImap) (PID=5956). A budget charge was encountered that exceeded the limit of '8.38228333333333' minutes. Budget Owner: 'Sid~MYDOMAIN\myuser~IMAP~False', Component: 'IMAP', CostType: 'CAS'.

    Log Name: Application
    Source: MSExchange ADAccess
    Date: 9/3/2009 4:53:31 AM
    Event ID: 2917
    Task Category: General
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: EXCAS-E2.mydomain.local
    Description:
    Process Microsoft.Exchange.Imap4.exe (PopImap) (PID=5956). A budget charge was encountered that exceeded the limit of '8.39296666666667' minutes. Budget Owner: 'Sid~MYDOMAIN\myuser~IMAP~False', Component: 'IMAP', CostType: 'Connection'.


    MCP, MCSA
  • Friday, September 04, 2009 12:14 AMvillaire11 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Add me to the list.  I am receiving the same error in my event log.  Exchange 2010RC, DC is Win Server 2008R2.
    This problem is completely locking up Windows Live Mail IMAP clients.  The Exchange 2010 Beta worked fine.
  • Wednesday, September 09, 2009 7:10 PMmshish Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm also having serious IMAP issues in 2010RC on 2008R2 RTM. I can't get anything useful in the eventlog and for some reason the IMAP service isn't writing a log (despite a location being set in the .config for the executable).

    Basically, any IMAP client connects, after about 5 commands the server returns an Bad Command Error Code 12 and says bye. I've tried using all sorts of clients and basic telnet. Restarting the IMAP service is the only way to recover, but again after about 5 commands the server stops functioning.
  • Wednesday, September 23, 2009 4:00 PMmshish Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Has anyone had any progress getting IMAP to work properly?
  • Thursday, October 08, 2009 8:09 AMcm_vsl Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    same here ... gathering the folder list and downloading headers works, downloding the message always results in various 0x800CC.. errors
    tried with apple mail, outlook express, windows mail, live mail, outlook XP, 2003, 2007, Entourage, thunderbird, opera mail, ect.
    also most clients connect only if authorization is set to basic (no TLS) ... W2K8 R2 + XCH 2010 RC
    interestingly POP3 works, but clearly not useful if one likes to have mails on an exchange server ....
  • Thursday, October 22, 2009 2:13 AMvillaire11 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    IMAP is still broken on Exchange 2010 RC running on Server 2008R2.  This is a serious flaw that needs to be addressed?

    Any update on this Microsoft?