Microsoft Exchange 2007 database dismounting

I have an SBS 2008 server with Exchange 2007. It has just decided to dismount the Exchange database and therefore no emails can come or go. I can mount it for about five minutes - either by starting the Information Store service or just mounting from the Exchange Management Console - and emails start to come through but then it dismounts again.

The following errors logs are from the detailed report:

MSExchange ActiveSync      1016      16/03/2015 18:27:39      219
Event Details:    
Exchange ActiveSync has encountered repeated failures when it tries to access data on Mailbox server [SEVER01.newquip.local]. Exchange ActiveSync will temporarily stop making Exchange ActiveSync requests to the Mailbox server. The process will be postponed for [60] seconds. This may be caused if the Mailbox server is overloaded. If this event is frequently logged, review the Application log for other events that could indicate the root cause of performance problems on the Mailbox server specified in the event description.

MSExchangeIS      1159      16/03/2015 18:26:45      10
Event Details:    
Database error Disk IO error occurred in function JTAB_BASE::EcRetrieveColumnByPtagId while accessing the database "First Storage Group\Mailbox Database".

MSExchangeFBPublish      8206      16/03/2015 18:18:29      2
Event Details:    
Unable to prepare message table for polling thread processing on virtual machine SEVER01. The error number is 0x80004005. Make sure that the Microsoft Exchange Information Store service is running.

MSExchangeFBPublish      8197      16/03/2015 18:13:28      35
Event Details:    
Error initializing session for virtual machine SEVER01. The error number is 0x80040111. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.

MSExchange System Attendant Mailbox      4001      16/03/2015 18:12:06      32
Event Details:    
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=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SEVER01/cn=Microsoft System Attendant. Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException: Cannot open mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SEVER01/cn=Microsoft System Attendant. ---> Microsoft.Mapi.MapiExceptionLogonFailed: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231) Diagnostic context: Lid: 18969 EcDoRpcExt2 called [length=254] Lid: 27161 EcDoRpcExt2 returned [ec=0x0][length=116][latency=0] Lid: 23226 --- ROP Parse Start --- Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80040111 Lid: 26937 Lid: 21921 StoreEc: 0x80040111 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 ---- Remote Context Beg ---- Lid: 26426 ROP: ropLogon [254] Lid: 59409 Lid: 45073 Lid: 11173 StoreEc: 0x80040111 Lid: 22970 Lid: 8620 StoreEc: 0x80040111 Lid: 1750 ---- Remote Context End ---- Lid: 26849 Lid: 21817 ROP Failure: 0x80040111 Lid: 26297 Lid: 16585 StoreEc: 0x80040111 Lid: 32441 Lid: 1706 StoreEc: 0x80040111 Lid: 24761 Lid: 20665 StoreEc: 0x80040111 Lid: 25785 Lid: 29881 StoreEc: 0x80040111 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, Cultur

MSExchange Anti-spam Update      1017      16/03/2015 08:49:14      1
Event Details:    
Microsoft Exchange couldn''t successfully use the Microsoft Update agent: Exception from HRESULT: 0x80072EE2. Please see http://update.microsoft.com and update your client manually. Anti-spam updates will not be downloaded until this problem is fixed.

ESE      481      16/03/2015 18:26:45      10
Event Details:    
MSExchangeIS (2616) First Storage Group: An attempt to read from the file "E:\Exchange Database\Mailbox Database.edb" at offset 109619101696 (0x0000001985cec000) for 8192 (0x00002000) bytes failed after 4 seconds with system error 1 (0x00000001): "Incorrect function. ". The read operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup. For more information, click http://www.microsoft.com/contentredirect.asp.


I have had a quick read up on some of the errors and have, from advice given, tried the following:

1.      Restarted the Server.

2.     Checked all mailboxes to ensure no one was over their limit of 50GB - Two are near 40GB, otherwise most are quite
         small.

3.      Turned the backup off – it is using NT backup to backup all of the system.  This is just temporary to see if it helps

4.      Requested a Chkdsk /f/r on the volume holding the Exchange database – this is the main volume that most data is
        stored. SBS is running on a different system drive – C:

I am currently waiting for the chkdsk to finish – I therefore won’t be checking until the morning and hopefully it may be working.

If not, then any ideas or suggestions would be greatly appreciated.
Markieboy1OwnerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth_zinCommented:
Is the location you have the mailbox store Disk full? Or where the logs are going?
AmitIT ArchitectCommented:
From error, it looks you have Disk corruption issue. You might need to replace bad disk.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Markieboy1OwnerAuthor Commented:
Thanks for your comments.

The ChkDsk seems to have solved the issue. I am going to monitor it today and see how it goes so will leave the question open for now.
Seth_zinCommented:
That would have been my next suggestion. Me and a friend use to always say, chkdsk fixes everything, haha. Hope it keeps working!
Markieboy1OwnerAuthor Commented:
All is still working well so will close the question. Thanks again for your comments.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.