MSExchangeIS Mailbox Store warning

What version of Exchange are you running?

Oh sorry I forgot to add the most important information.

I am running Exchange 2007 SP2 on Windows Server 2003 64Bit

Thanks - doing some digging.  Back shortly.

http://web2.minasi.com/forum/topic.asp?TOPIC_ID=31677

Restarting the information store should resolve this ; have a read through on the above link

It sounds like you have a problem with the database and the suggested fix is to dismount the store and run isinteg -s {servername} -fix -test alltests against the store.
http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html 

mutahir - read further down that link - the next comment is "Spoke to soon"!

Hello alanhardisty and mutahir,

I I guess I will the command below a try.

isinteg -s servername -fix -test alltests

Since this server is in production I have to wait until off hours. Our mail database is currently 17G big. I have never run the command. Any idea how long it will take on a db file that size until it completes?

Thank you
Marcus

http://www.msexchange.org/tutorials/Exchange-ISINTEG-ESEUTIL.html

as you have to wait, read through the article on the above link for a good insight.

About 3-6 Gb per hour depending on your hardware / processor / memory.

Ok I will give that a try tonight or tomorrow night. Thank you very much for your time on this. I will keep you posted.

I finally got a maintenenance window tonight but it did not go so well. When I run the isinteg -s servername -fix -test alltests command then I see the following output.
===================================================================================

[PS] C:\>isinteg -s exchange1 -test alltests
Databases for server exchange1:
Only databases marked as Offline can be checked

Index  Status       Database-Name
Storage Group Name: First Storage Group
  1    Offline      Mailbox Database
Storage Group Name: Second Storage Group
  2    Offline      Public Folder Database
Enter a number to select a database or press Return to exit.
1
You have selected First Storage Group / Mailbox Database.
Continue?(Y/N)Y

Isinteg: the request to cancel verification process failed.
Isinteg: the request to stop verification process failed.
  The verification has probably been interrupted.
  Please review the log file for more information.
[PS] C:\>
===================================================================================
In the Application Log I found the following error:
===================================================================================
Event Type:      Error
Event Source:      MSExchange System Attendant Mailbox
Event Category:      General
Event ID:      4001
Date:            10/16/2009
Time:            11:15:03 PM
User:            N/A
Computer:      EXCHANGE1
Description:
A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds. Diagnostic information:

Cannot open mailbox /o=CustomCall Data Systems/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE1/cn=Microsoft System Attendant.
Microsoft.Exchange.Data.Storage.StorageTransientException: Cannot open mailbox /o=CustomCall Data Systems/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=EXCHANGE1/cn=Microsoft System Attendant. ---> Microsoft.Mapi.MapiExceptionIsintegMDB: MapiExceptionIsintegMDB: Unable to open message store. (hr=0x80004005, ec=1164)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=261]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=92][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x48C    
    Lid: 26937  
    Lid: 21921   StoreEc: 0x48C    
    Lid: 27962   ROP: ropExtendedError [250]
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 17097   StoreEc: 0x48C    
    Lid: 8620    StoreEc: 0x48C    
    Lid: 1750    ---- Remote Context End ----
    Lid: 26849  
    Lid: 21817   ROP Failure: 0x48C    
    Lid: 26297  
    Lid: 16585   StoreEc: 0x48C    
    Lid: 32441  
    Lid: 1706    StoreEc: 0x48C    
    Lid: 24761  
    Lid: 20665   StoreEc: 0x48C    
    Lid: 25785  
    Lid: 29881   StoreEc: 0x48C    
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx)
   at Microsoft.Mapi.ExRpcConnection.OpenMsgStore(OpenStoreFlag storeFlags, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, MapiStore msgStorePrivate, String& correctServerDn, ClientIdentityInfo clientIdentityAs, String userDnAs, String applicationId, CultureInfo cultureInfo)
   at Microsoft.Mapi.ConnectionCache.OpenMapiStore(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, ClientIdentityInfo clientIdentity, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId)
   at Microsoft.Mapi.ConnectionCache.OpenMailbox(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, WindowsIdentity windowsIdentityAs, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId)
   at Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)
   at Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)
   at Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString)
   at Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags)
   at Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString)
   at Microsoft.Exchange.Data.Storage.MailboxSession.OpenAsAdmin(ExchangePrincipal mailboxOwner, CultureInfo cultureInfo, String clientInfoString, Boolean useLocalRpc, Boolean ignoreHomeMdb)
   at Microsoft.Exchange.Data.Storage.MailboxSession.OpenAsAdmin(ExchangePrincipal mailboxOwner, CultureInfo cultureInfo, String clientInfoString)
   at Microsoft.Exchange.Servicelets.SystemAttendantMailbox.Servicelet.Work()

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
===================================================================================

Can anyone help please?

Thank you
Marcus

I found at eventid.net the following entry for the error:
====================================================================================
In my case, the problem was caused by a corrupted scheme in AD. On Exchange 2007 DVD, I ran setup.exe /p to recreate the scheme. The error messages stopped and nothing was lost. The queued messages were then delivered.
====================================================================================
I remember that we had some problems in the past because a entry in the schema got deleted and afterwards we where not able to mount the Public Folder database but the issue was solved after the schema was fixed manually.
I wonder if it would be a good idea to run this command or not. Please let me know if you have any thoughts on that.

Thank you
Marcus

Can you have a look at the following EE question with the same problem as this:
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_22981340.html
The Link in the question refers to this link - the one in the question is wrong if you click on it. http://technet.microsoft.com/en-us/library/bb232092.aspx 

Hello alanhardisty,

Thank you for you response. Thanks alot for your response but I believe that the size issue does not apply to us since our mail database is curently 18G - so that is not even close to the 50G.

Additionally I did not receive any further warnings or any errors since Friday. I think I will make some more research on the setup /p command because I know for a fact that there was a schema at some point.

For now I will close this question if I have any other questions then I will simply open a new one.

Thank you
Mc2102