none
exchange 2007 event id 1022 error 1245 - Logon Failure on database

    Question

  • Hi, my exchage 2007 sp2 server has the next error:

    ---------------------------------------

    Log Name:      Application
    Source:        MSExchangeIS Mailbox Store
    Date:          3/23/2010 2:54:52 PM
    Event ID:      1022
    Task Category: Logons
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server
    Logon Failure on database "Storage Group\Mailbox Database" - Windows account domain\ServerName$; mailbox /o=organization/ou=Exchange Administrative Group ()cn=Recipients/cn=username.
    Error: 1245
    Client Machine: ServerName 
    Client Process: edgetransport.exe
    Client ProcessId: 0
    Client ApplicationId: Client=Hub Transport

    --------------------------------

    Each time a mailbox has its limit, the error is logged in event viewer application log and sometimes mapi client requiered log on ( windows with username and password).

    Thanks a lot for comments.

    Johan Montano r.

     

    Tuesday, March 23, 2010 8:20 PM

Answers

  • Hi all.

    I was checking again and this event is logged when I had quota limit and it is full.

    thanks a lot for comments.

    JMR.

    • Marked as answer by Johan M. R. _ Friday, March 26, 2010 10:42 PM
    Friday, March 26, 2010 10:42 PM

All replies

  • Have you seen this article?

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

    As you mentioned, it is because of the mailbox limit.  What is your mailbox policy? 

     


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, March 24, 2010 3:33 PM
  • Thanks for comments.

    The article kb 555420 doesn´t apply to my issue.

    I was checking and the issue is logged when the user limit has been full, is by desing I guess.

    Let me check today and I will update the case.

    Johan Montano R.

    Wednesday, March 24, 2010 6:57 PM
  • Mailbox size/quota is a custom configuration.  I believe you are getting this message because of the mailbox quota limit.  You can see mailbox quota the details on the following link:

    http://technet.microsoft.com/en-us/library/bb201753(EXCHG.80).aspx


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, March 24, 2010 7:14 PM
  • Hi Johan,

     

    Please make sure the mailbox is not being moved when the trying to access it. Do it happen only this user or some users? Is the mailbox a specific mailbox, just like system attendant mailbox? Please raise the limitation and let us know the result.

     

    Thanks,

     

    Elvis

     

     

    Thursday, March 25, 2010 8:04 AM
  • Hi all.

    I was checking again and this event is logged when I had quota limit and it is full.

    thanks a lot for comments.

    JMR.

    • Marked as answer by Johan M. R. _ Friday, March 26, 2010 10:42 PM
    Friday, March 26, 2010 10:42 PM
  • Thank you for your feedback.  

    Monday, March 29, 2010 2:42 AM
  • Note:

    These clients store Free/Busy information in public folders.

     

    •             If you have storage limits that are configured to disable mailboxes when a particular storage limit is reached, the following event may be logged on Hub Transport servers:

    Event ID: 1022

    Category: None

    Source: MSExchangeIS Mailbox Store

    Type: Error

    Description: Logon Failure on database "<database_name>" - Windows account Contoso\<ServerName>$; mailbox /o=ContosoOrganization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=<ServerName>/cn=Microsoft System Attendant

    Error: 1245

     

    This issue occurs when the ExchangeLegacyDN attributes of the affected user accounts point to a deleted Administrative group. In this scenario, you must update the ExchangeLegacyDN attribute for each affected user. The ExchangeLegacyDN attribute must be updated to the following conditions:

    •             The attribute must be converted to an X500 address type. Each user must have a unique X500 address.

    •             The attribute must be updated to use a unique ExchangeLegacyDN attribute as appropriate for the Administrative group in which the user account is located.

    You can use a bulk modification tool, such as LDIFDE or ADModify.NET to perform this operation. For detailed instructions about how to modify the ExchangeLegacyDN attribute, see step 5 under "To remove the last Exchange 2003 or Exchange 2000 server from an Exchange 2007 organization" in How to Remove the Last Legacy Exchange Server from an Organization1How to Remove the Last Legacy Exchange Server from an Organization1.

    For More Information

    ________________________________________

    For more information about how to use ADModify.NET, see the following Microsoft Web log (blog): ADModify.NET is here2.

     

    It is important to have a working System Attendant Mailbox.  It handles Free/Busy Info, is required for all mailbox moves, etc

     

    Thursday, May 26, 2011 7:05 PM