• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 610
  • Last Modified:

Exchange 5.5 MTA Service Issues

I'm trying to recover from a recent disaster on our Exchange 5.5 server.
I've installed a new server NT4 SP6a & Exchange 5.5 SP4. I've managed to recover the priv.edb & pub.edb from backups (both are in a consistant state) but the MTA service won't start. The Event log give 3 errors. 1 on ESE97 - Event ID 145 and the other 2 are giving Events 1120 & 5000 on the Exchange IS.

Can anyone shed any light on this, I'm starting to loose too much hair and sleep!
1 Solution

After some looking into, it seems as if your database is in an inconsistant state. Here's some info.. So first thing to look for is if you have permissions (explains why it can't mount the store). Else, try to fix the database..


As per Microsoft: "This issue can occur if the Exchange Server service account does not have Write permission to the Priv.edb file. The ability to write to this file can be restricted by insufficient NTFS file system (NTFS) rights to the PRIV.EDB file, or by a read-only file attribute applied to the PRIV.EDB file". See Q245058 for more details.

Did you perform a hard recovery on both priv and pub? What type of restore did you perform ... was it an offline or online restore? If it was an online restore, after you got the IS started ... did you run IS/DS consistency adjuster?

Need a little more information ... can you also list the exact events showing up ... have you considered turning up logging on MSExchangeMTA?
njwilkinsonAuthor Commented:
I've run eseutil /mh on both the pub & priv edb's and they both report back as in a consistant state. I checked the permissions on the files and they are both okay.

I restored both of the files from an offline backup. I've also removed any logs files that are remaining and ran isinteg -patch.

I can get the IS running it's just the MTA.

I turned up the logging for the MTA, the for the application log results are:-

EventID: 100
Source: ESE97
Desc: MSExchangeIS (182) The database engine 05.2653.0011 started.

EventID: 145
Source: ESE97
Desc: MSExchangeIS (182) The database engine could not access the file called E:\exchsrvr\Mdblogs\edb.log.

EventID: 1120
Source MSExchangeIS
Desc: Error 0xfffffbf8 initializing the Microsoft Exchange Server Information Store database.

Event ID: 5000
Source: MSExchangeIS
Desc: Unable to initialize the Microsoft Exchange Information Store service. Error 0xfffffbf8.

In the system log there was also:-

EventID: 7024
Source: Service Control Manager
Desc: The Microsoft Exchange Message Transfer Agent service terminated with service-specific error 4294966264.

Any help greatly appreciated.
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

your root problem appear to be this one

EventID: 145
Source: ESE97
Desc: MSExchangeIS (182) The database engine could not access the file called E:\exchsrvr\Mdblogs\edb.log.

try this link for a few tips on how to deal with it
njwilkinsonAuthor Commented:
Hi guys

I've managed to sort it. It turned out to be a missmatch in the store.exe and emsmta.exe.
Restored those from the offline backup we had and all is back up and running.

Thanks for your help.
Good job!
PAQed with points refunded (500)

Community Support Moderator
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now