Windows 2012 Server running Exchange 2010 - Event ID 9045

Hello,

We have a Windows 2012 server running Exchange 2010.

I have noticed that over the past few days I keep seeing the following event in the Windows 2012 Event Application log :-

Source MSExchange Assistant
Event ID 9045

Service MSExchangeMailboxAssistants. The assistant Junk E-mail Options Assistant stopped processing database Mailbox Database 1577978229 (f3026357-e864-4d1c-8712-4afddc6b7f00) because the database is in an unhealthy state.


I dont like seeing anything that states the database is unhealthy, so the question is, what does it mean, and what, if anything should I do to address this.

Any advice appreciated.

Thanks.
LVL 1
nigelbeatsonAsked:
Who is Participating?
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.

Miguel Angel Perez MuñozCommented:
First of all, have you checked this database?

Run Test-ExchangeSearch -MailboxDatabase "Mailbox Database 1577978229"
0
Cliff GaliherCommented:
It means exactly what it sounds like it means. Somehow the exchange database has become corrupt. You should definitely look at addressing the problem.

Depending on your backup strategy, the safest route is to restore a backup of the database to a new store and replay the logs since the backup to bring you fully up to date. Done properly, there is zero data loss and you get a database with no corruption.

Of course if this has been happening and has gone unnoticed for awhile, as it sounds like it may have been, then this may not be an option. Some people are also not comfortable with restoring a database into a new store or making that transition. The common tool for working with an existing database is ESEUTIL and it does have a repair mode. It is very good at repairing issues, but depending on the amount of corruption, how it occurred, and other factors, sometimes the process of repair is to simply remove bad records...in other words some data loss.

Those are the two easiest paths and I wouldn't wade in any deeper unless one or both fail for some reason.
0

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
Miguel Angel Perez MuñozCommented:
Sometimes damaged mailbox causes databases inconsistent. Simply deleting and recreating mailbox resolve inconsistency. I suggest you test database first to determine restoration needs.
0
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.

nigelbeatsonAuthor Commented:
Yes, it has been happening for several days.

Can I run - Test-ExchangeSearch -MailboxDatabase "Mailbox Database 1577978229" whilst exchange is still being used?

What would cause such a thing to happen? Its a relatively new installation ie new server and new software. Been running for 4 to 5 months.

Thanks
0
Miguel Angel Perez MuñozCommented:
You can do with server working, there is no downtime.
0
nigelbeatsonAuthor Commented:
Can I presume I run - Test-ExchangeSearch -MailboxDatabase "Mailbox Database 1577978229" from the exchange management shell?
0
nigelbeatsonAuthor Commented:
I ran the test, and after a few seconds we got :-

[PS] C:\Windows\system32>Test-ExchangeSearch -MailboxDatabase "Mailbox Database 1577978229"

Database     Server       Mailbox      ResultFound SearchTime Error
                                                   InSeconds
--------     ------       -------      ----------- ---------- -----
Mailbox D... FSAMS2       SystemMai... True        92.641

What does this tell us?

Many thanks
0
Gareth GudgerCommented:
So it sounds like there is corruption in one of your databases.

For me personally a much easier way to deal with this (with zero downtime) is to create a brand new database. Then move your users to the new database. Any corruption is skipped during the move. Delete the old database. DONE!
0
nigelbeatsonAuthor Commented:
Many thanks t all.
0
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
Windows Server 2012

From novice to tech pro — start learning today.

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.