none
Error: 0x8004010f , Event ID: 1025, Source: MSExchangeIS Mailbox Store,MS Exchange 2010 SP1 RRS feed

  • Question

  • My configuration is Exchange 2010 SP1, Windows Server 2008 R2 SP1.

    All MS Exchange roles are assigned to one MS Exchange Server with Antivirus and Antispam SW together.

    Except this problem everything looks fine.

     

    In Application Log on my MS Exchange Server, I have 4 reoccurring logs /always all together/:

    Event ID: 1025, Source: MSExchangeIS Mailbox Store 

    An error occurred on database "Mailbox Database 1073144232".

    Function name or description of problem: Cannot generate Read Notification when Sender Data is missing!!!!

    Error: 0x8004010f

    Event ID: 1025, Source: MSExchangeIS Mailbox Store 

    An error occurred on database "Mailbox Database 1073144232".

    Function name or description of problem: EcSetRNProps:

    Error: 0x8004010f

    Event ID: 1025, Source: MSExchangeIS Mailbox Store

    An error occurred on database "Mailbox Database 1073144232".

     

    Event ID: 1025, Source: MSExchangeIS Mailbox Store 

    An error occurred on database "Mailbox Database 1073144232".

    Function name or description of problem: EcGenerateNRN:

     

    I have found problems, solutions, symptoms with the same Event ID, but only for MS Exchange 2003, or older.
    I tried to apply these solutions in MS Exchange 2010, but with no success.
    I defragmented database with ESEUTIL, I ran ISINTEG in Exchange 2010 SP1 is it  New-MailboxRepairRequest cmdlet.
    I tried to check permissions with Best Practices Analyzer but no security, or security related errors found.
    No success.



    Wednesday, March 23, 2011 8:06 AM

Answers

  • Dear All,

    problem was old fashion IMAP client connecting on one of my mailboxes.

    I changed my custom application version and problem disappear.

    Best regards,

    Boris.

     


    • Marked as answer by BorisASK Monday, June 13, 2011 8:33 AM
    Monday, June 13, 2011 8:31 AM

All replies

  • Hello,

     

    It seems the issue only occurs to one problematic mailbox database “Mailbox Database 1073144232”.

     

    We can try creating a new mailbox database and monitor if the 1025 event ID also occur for the new mailbox database. If it does not occur on the new mailbox database, we can workaround this issue by moving all the mailboxes to the new database.

     

    Thanks,

    Simon

    Thursday, March 24, 2011 9:57 AM
    Moderator
  • Hello,

    I moved all mailboxes to new created database.

    Everything looks fine, but next morning I have the same errors on new database.

    Since that time, errors are repeated every hour on new database with same symptoms as on old one.

    Old database is still running. DB is empty and no error is producing since I moved of all the mailboxes.

    Have you any other idea, what to do?

     Best regards,

    Boris

    Wednesday, March 30, 2011 7:39 AM
  • Hi Boris,
    We can also schedule a downtime and dismount the problematic mailbox database, then try running Isinteg to repair the problematic database:
    ISINTEG –s ServerName –fix –test alltests
    After pressing Enter, please choose related database and press Enter to start the process.
    For more information about ISINTEG, please refer to the following article:
    Description of the Isinteg utility
    http://support.microsoft.com/kb/182081
    After repairing the mailbox database until 0 error and 0 warning, please mount this mailbox database and check this issue again.
    Thanks,
    Simon
    Wednesday, March 30, 2011 9:15 AM
    Moderator
  • Hello,

    I think that ISINTEG is not possible to use on Exchange 2010 SP1.

    This is console output:


    C:\Program Files\Microsoft\Exchange Server\V14\Bin>ISINTEG -s EXCHSRV -fix -test
     alltests
    Microsoft Exchange Information Store Integrity Checker v14.01.0218.015
    Copyright (c) 1986-2000 Microsoft Corp.    All rights reserved.
    Usage:

    C:\Program Files\Microsoft\Exchange Server\V14\Bin>

    No switches, help or something similar is not working, still the same reply:

    Microsoft Exchange Information Store Integrity Checker v14.01.0218.015
    Copyright (c) 1986-2000 Microsoft Corp.    All rights reserved.
    Usage:

    C:\Program Files\Microsoft\Exchange Server\V14\Bin>

    I think that ISINTEG is not working anymore, just one way is to use New-MailboxRepairRequest cmdlet, but it says that,

    there is no problem.

    Any idea?

    Best regards,

    Boris.

     

    Wednesday, March 30, 2011 3:29 PM
  • Hello Boris,

     

    Yes, since E14, we use New-MailboxRepairRequest cmdlet to replace the isinteg command.

     

    Since there is no error reported after running the Mailbox Repair, we can confirm that the statue of the database is healthy and we can safely ignore the event warnings. You can also check the Exbpa to see if it reports any issues about the specific mailbox database.

     

    Thanks,

    Simon

    Thursday, March 31, 2011 6:12 AM
    Moderator
  • Hello Simon, 

    I tried to run New-MailboxRepairRequest with these parameters again:

    New-MailboxRepairRequest -Database "Mailbox Database" -CorruptionType AggregateCounts,SearchFolder,ProvisionedFolder,Folderview

    No errors I've found in event log viewer but problem still persists

    Service MSExchangeMailboxAssistants. Managed Folder Mailbox Assistant for database Mailbox Database (4f30bd52-eda1-4faf-9a3c-4d85cc5e6237) reached a work cycle checkpoint (Duration: 23:28:02.1105205, Database Completely Healthy During Work Cycle: Yes). 45 mailboxes were successfully processed. 0 mailboxes were skipped due to errors. 0 mailboxes were processed separately. There are 0 mailboxes remaining on this database which will be processed during the next work cycles.

     In Exbpa I can't find anything what could be cause of the problem.

    Errors are still repeating every hour.

    Maybe ...

    I removed old Exchange Server 2003 using this KB one month ago:

     

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

    MS in this KB says: Microsoft recommends that you do not remove the original Administrative groups from an organization. I did it this way and left old Administrative Group, but removed old groups and permissions as recommended. 

    Can this be the cause of problem?

    Is it safe to remove it?

    Thanks,

     

    Boris
    • Marked as answer by BorisASK Monday, June 13, 2011 8:29 AM
    • Unmarked as answer by BorisASK Monday, June 13, 2011 8:30 AM
    Monday, April 4, 2011 2:47 PM
  • Dear All,

    problem was old fashion IMAP client connecting on one of my mailboxes.

    I changed my custom application version and problem disappear.

    Best regards,

    Boris.

     


    • Marked as answer by BorisASK Monday, June 13, 2011 8:33 AM
    Monday, June 13, 2011 8:31 AM