Exchange 2010 MailboxAssistants Service Terminated Unexpectedly Event 7031

Hi,

I am getting this error frequently, Exchange 2010 on Server2008 R2. I am not seeing any errors from users. Any thoughts?

Log Name:      System
Source:        Service Control Manager
Date:          25/03/2010 10:28:07
Event ID:      7031
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EX1.******.local
Description:
The Microsoft Exchange Mailbox Assistants service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7031</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2010-03-25T10:28:07.366944700Z" />
    <EventRecordID>9091</EventRecordID>
    <Correlation />
    <Execution ProcessID="544" ThreadID="10384" />
    <Channel>System</Channel>
    <Computer>EX1.*****.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Microsoft Exchange Mailbox Assistants</Data>
    <Data Name="param2">1</Data>
    <Data Name="param3">5000</Data>
    <Data Name="param4">1</Data>
    <Data Name="param5">Restart the service</Data>
  </EventData>
</Event>

Thanks,
S.
Sam_RendellAsked:
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.

Glen KnightCommented:
first think I would suggest is get Exchange 2010 Rollup 2 installed: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6d3ae3e0-3982-46d6-9e9c-7d7d63fae565

If that doesn't fix it run the Exchange Best Practice analyzer and see what this brings back (it's in the toolbox section of the Exchange management console)
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
Sam_RendellAuthor Commented:
I will install rollup2 this evening.

Running the best practice thingy it seems the domainprep hasn't worked properly.

Active Directory domain '*****' has an unrecognized Exchange signature. Current DomainPrep version: 12639.

I ran the Exch2010 install with the correct permission so it should have done it automatically.

Anyway can you tell me which setup switches I should be using to sort this error?

Cheers,
S.
0
Sam_RendellAuthor Commented:
Ok I found the switch command

setup.com /pl

I need to check it is safe to run with the legacy switch after the exchange 2010 installation has already been done though.

Ta.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Glen KnightCommented:
Exchange 2010 should do the domainprep when it installs if it hasn't been done beforehand.

However there is no problem with running this again.

All you need to do is run the following:

setup /PrepareLegacyExchangePermissions
setup /PrepareSchema
setup /PrepareAD
0
Sam_RendellAuthor Commented:
Thanks man.
0
Sam_RendellAuthor Commented:
Interesting, I have successfully run the domain preps.

Now best practise still shows the same "Active Directory domain '*****' has an unrecognized Exchange signature. Current DomainPrep version: 12639." error but now it also completely fails to connect to any of my exchange servers to test them.

Doesn't seem good!

S.
0
Glen KnightCommented:
Can you run DCDIAG on your domain controllers please and post the results?
0
Sam_RendellAuthor Commented:

DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests
   
   Testing server: Abingdon\ABI-FS01
      Starting test: Connectivity
         ......................... ABI-FS01 passed test Connectivity

Doing primary tests
   
   Testing server: Abingdon\ABI-FS01
      Starting test: Replications
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from SITE-FS11 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 12:49.15.
            Replication of new changes along this path will be delayed.
         [Replications Check,ABI-FS01] A recent replication attempt failed:
            From SITE-FS18 to ABI-FS01
            Naming Context: DC=Leadbitter,DC=local
            The replication generated an error (8524):
            Win32 Error 8524
            The failure occurred at 2010-03-25 16:19.14.
            The last success occurred at 2009-07-29 11:22.04.
            22944 failures have occurred since the last success.
            The guid-based DNS name 1790dfbd-f125-4b40-b3d4-66f79bbf45b4._msdcs.Leadbitter.local
            is not registered on one or more DNS servers.
         [SITE-FS18] DsBind() failed with error 1722,
         Win32 Error 1722.
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from SITE-FS11 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 12:49.24.
            Replication of new changes along this path will be delayed.
         [Replications Check,ABI-FS01] A recent replication attempt failed:
            From SITE-FS18 to ABI-FS01
            Naming Context: CN=Configuration,DC=Leadbitter,DC=local
            The replication generated an error (8524):
            Win32 Error 8524
            The failure occurred at 2010-03-25 16:19.16.
            The last success occurred at 2009-07-29 11:15.24.
            22944 failures have occurred since the last success.
            The guid-based DNS name 1790dfbd-f125-4b40-b3d4-66f79bbf45b4._msdcs.Leadbitter.local
            is not registered on one or more DNS servers.
         [Replications Check,ABI-FS01] A recent replication attempt failed:
            From SITE-FS18 to ABI-FS01
            Naming Context: CN=Schema,CN=Configuration,DC=Leadbitter,DC=local
            The replication generated an error (8524):
            Win32 Error 8524
            The failure occurred at 2010-03-25 16:19.19.
            The last success occurred at 2009-07-29 11:17.24.
            22941 failures have occurred since the last success.
            The guid-based DNS name 1790dfbd-f125-4b40-b3d4-66f79bbf45b4._msdcs.Leadbitter.local
            is not registered on one or more DNS servers.
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from ABI-FS08 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 14:49.23.
            Replication of new changes along this path will be delayed.
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from SITE-FS11 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 12:49.35.
            Replication of new changes along this path will be delayed.
         [Replications Check,ABI-FS01] A recent replication attempt failed:
            From SITE-FS18 to ABI-FS01
            Naming Context: DC=DomainDnsZones,DC=Leadbitter,DC=local
            The replication generated an error (1256):
            Win32 Error 1256
            The failure occurred at 2010-03-25 16:19.14.
            The last success occurred at 2009-07-29 11:19.24.
            22944 failures have occurred since the last success.
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from ABI-FS08 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 14:49.23.
            Replication of new changes along this path will be delayed.
         REPLICATION LATENCY WARNING
         ABI-FS01: This replication path was preempted by higher priority work.
            from SITE-FS11 to ABI-FS01
            Reason: Win32 Error 8418
            The last success occurred at 2010-03-25 12:49.36.
            Replication of new changes along this path will be delayed.
         [Replications Check,ABI-FS01] A recent replication attempt failed:
            From SITE-FS18 to ABI-FS01
            Naming Context: DC=ForestDnsZones,DC=Leadbitter,DC=local
            The replication generated an error (1256):
            Win32 Error 1256
            The failure occurred at 2010-03-25 16:19.14.
            The last success occurred at 2009-07-29 11:19.24.
            22944 failures have occurred since the last success.
         ......................... ABI-FS01 passed test Replications
      Starting test: NCSecDesc
         ......................... ABI-FS01 passed test NCSecDesc
      Starting test: NetLogons
         ......................... ABI-FS01 passed test NetLogons
      Starting test: Advertising
         ......................... ABI-FS01 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... ABI-FS01 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... ABI-FS01 passed test RidManager
      Starting test: MachineAccount
         * The current DC is not in the domain controller's OU
         ......................... ABI-FS01 failed test MachineAccount
      Starting test: Services
         ......................... ABI-FS01 passed test Services
      Starting test: ObjectsReplicated
         ......................... ABI-FS01 passed test ObjectsReplicated
      Starting test: frssysvol
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         ......................... ABI-FS01 passed test frssysvol
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x8000043B
            Time Generated: 03/25/2010   16:16:32
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 03/25/2010   16:20:42
            (Event String could not be retrieved)
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 03/25/2010   16:20:42
            Event String: The attempt to establish a replication link for

         An Error Event occured.  EventID: 0xC00007FA
            Time Generated: 03/25/2010   16:20:42
            (Event String could not be retrieved)
         An Warning Event occured.  EventID: 0x80000785
            Time Generated: 03/25/2010   16:20:42
            Event String: The attempt to establish a replication link for

         ......................... ABI-FS01 failed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 03/25/2010   16:25:55
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 03/25/2010   16:25:56
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 03/25/2010   16:26:01
            (Event String could not be retrieved)
         ......................... ABI-FS01 failed test systemlog
   
   Running enterprise tests on : Leadbitter.local
      Starting test: Intersite
         ......................... Leadbitter.local passed test Intersite
      Starting test: FsmoCheck
         ......................... Leadbitter.local passed test FsmoCheck
0
Glen KnightCommented:
How many Domain Controllers do you have?
0
Sam_RendellAuthor Commented:
23

We have a lot of remote sites.

S.
0
Glen KnightCommented:
Oh :(

how many do you have onsite at the location you are working at?
Where are the FSMO roles?
What else is in the DC's?
What's the Active Directory site name where you are at the moment?

Looks like you have an Active Directory Replication problem.  I can help you fix it but I am mobile at the moment so it might take me a while.

0
Sam_RendellAuthor Commented:
Yeah it is a pain, I'm hoping to start reducing the numbers now our WAN links don't go up and down all the time.

There are DCs 2 on this site.

I'm not sure what is up with Site-FS11 but Site-FS18 I must have turned off ages ago and forgotten to demote.

FSMO is new to me, I just had a quick read, basically any DC is allowed to make changes, however I am the only one who makes changes so there shouldn't be any conflicts. Some times I make changes on remote DCs to avoid waiting for replication to a remote site.

Site DCs also provide file shares and  print services. But only for 4-10 users or so.

S.
0
Sam_RendellAuthor Commented:
Read more;

I have never moved any FSMO roles. So they will all be on Abi-FS01

If there is a handy command to list what is where I'll give it a go. But I haven't found one on the web yet.
0
Sam_RendellAuthor Commented:
Confirmed, all FSMO roles are on Abi-FS01.
0
Sam_RendellAuthor Commented:
I am done for the day now I will pick this up again tomorrow 8am GMT.

Thanks for helps so far.
0
Glen KnightCommented:
Can you run: Netdom query fsmo
0
Sam_RendellAuthor Commented:
Morning!

I ran netdom query fsmo and has suspected all roles are on FS01

I tidied off the dead DC FS18 yesterday. Here is todays DCdiag


DC Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial non skippeable tests
   
   Testing server: Abingdon\ABI-FS01
      Starting test: Connectivity
         ......................... ABI-FS01 passed test Connectivity
   
   Testing server: Malvern\SITE-FS15
      Starting test: Connectivity
         ......................... SITE-FS15 passed test Connectivity
   
   Testing server: Tremough\SITE-FS16
      Starting test: Connectivity
         ......................... SITE-FS16 passed test Connectivity
   
   Testing server: Abingdon\ABI-FS08
      Starting test: Connectivity
         ......................... ABI-FS08 passed test Connectivity
   
   Testing server: ChathamPlace\SITE-FS19
      Starting test: Connectivity
         ......................... SITE-FS19 passed test Connectivity
   
   Testing server: NorthHantsHospital\SITE-FS18
      Starting test: Connectivity
         ......................... SITE-FS18 passed test Connectivity
   
   Testing server: Cardiff\CAR-FS02
      Starting test: Connectivity
         ......................... CAR-FS02 passed test Connectivity
   
   Testing server: Inglewood\SITE-FS12
      Starting test: Connectivity
         ......................... SITE-FS12 passed test Connectivity
   
   Testing server: HarlowLC\SITE-FS11
      Starting test: Connectivity
         ......................... SITE-FS11 passed test Connectivity
   
   Testing server: Solihull\SITE-FS17
      Starting test: Connectivity
         ......................... SITE-FS17 passed test Connectivity
   
   Testing server: Guildford\SITE-FS21
      Starting test: Connectivity
         ......................... SITE-FS21 passed test Connectivity
   
   Testing server: Plymouth\PLY-FS01
      Starting test: Connectivity
         ......................... PLY-FS01 passed test Connectivity
   
   Testing server: Bristol\BRI-FS04
      Starting test: Connectivity
         ......................... BRI-FS04 passed test Connectivity
   
   Testing server: HoldenhurstRd\SITE-FS01
      Starting test: Connectivity
         ......................... SITE-FS01 passed test Connectivity
   
   Testing server: Paragon\SITE-FS02
      Starting test: Connectivity
         ......................... SITE-FS02 passed test Connectivity
   
   Testing server: Uxbridge\SITE-FS03
      Starting test: Connectivity
         ......................... SITE-FS03 passed test Connectivity
   
   Testing server: Bettws\SITE-FS04
      Starting test: Connectivity
         ......................... SITE-FS04 passed test Connectivity
   
   Testing server: Wallingford\SITE-FS14
      Starting test: Connectivity
         ......................... SITE-FS14 passed test Connectivity
   
   Testing server: Coventry\SITE-FS05
      Starting test: Connectivity
         ......................... SITE-FS05 passed test Connectivity
   
   Testing server: Southampton\SOT-FS02
      Starting test: Connectivity
         ......................... SOT-FS02 passed test Connectivity

Doing primary tests
   
   Testing server: Abingdon\ABI-FS01
      Starting test: Replications
         ......................... ABI-FS01 passed test Replications
      Starting test: NCSecDesc
         ......................... ABI-FS01 passed test NCSecDesc
      Starting test: NetLogons
         ......................... ABI-FS01 passed test NetLogons
      Starting test: Advertising
         ......................... ABI-FS01 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... ABI-FS01 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... ABI-FS01 passed test RidManager
      Starting test: MachineAccount
         * The current DC is not in the domain controller's OU
         ......................... ABI-FS01 failed test MachineAccount
      Starting test: Services
         ......................... ABI-FS01 passed test Services
      Starting test: ObjectsReplicated
         ......................... ABI-FS01 passed test ObjectsReplicated
      Starting test: frssysvol
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         ......................... ABI-FS01 passed test frssysvol
      Starting test: kccevent
         ......................... ABI-FS01 passed test kccevent
      Starting test: systemlog
         ......................... ABI-FS01 passed test systemlog
   
   Testing server: Malvern\SITE-FS15
      Starting test: Replications
         ......................... SITE-FS15 passed test Replications
      Starting test: NCSecDesc
         ......................... SITE-FS15 passed test NCSecDesc
      Starting test: NetLogons
         ......................... SITE-FS15 passed test NetLogons
      Starting test: Advertising
         ......................... SITE-FS15 passed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... SITE-FS15 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... SITE-FS15 passed test RidManager
      Starting test: MachineAccount
         * The current DC is not in the domain controller's OU
         ......................... SITE-FS15 failed test MachineAccount
      Starting test: Services
         ......................... SITE-FS15 passed test Services
      Starting test: ObjectsReplicated
         ......................... SITE-FS15 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... SITE-FS15 passed test frssysvol
      Starting test: kccevent
         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/08/2008   11:44:49
            Event String: All domain controllers in the following site that

         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/08/2008   11:44:49
            Event String: All domain controllers in the following site that

         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/08/2008   11:44:49
            Event String: The Knowledge Consistency Checker (KCC) has

         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/08/2008   11:44:49
            Event String: All domain controllers in the following site that

         An Warning Event occured.  EventID: 0x8000061E
            Time Generated: 04/08/2008   11:44:49
            Event String: All domain controllers in the following site that

         An Error Event occured.  EventID: 0xC000051F
            Time Generated: 04/08/2008   11:44:49
            Event String: The Knowledge Consistency Checker (KCC) has

         An Warning Event occured.  EventID: 0x800004F1
            Time Generated: 04/08/2008   11:44:50
0
Sam_RendellAuthor Commented:
I'm not sure why FS18 is now showing as working, I have removed it's machine account and the "northhants" site doesn't exist in site and services.
0
Glen KnightCommented:
Now that you have removed the failed DC does Exchange pick up the fact the schema has been updated now?
0
Sam_RendellAuthor Commented:
No and it still isn't testing any of the selected exchange boxes.
0
Glen KnightCommented:
I am not sure what that last statement means?
0
Sam_RendellAuthor Commented:
Screen dump attached, was working before.
BestPrac.jpg
0
Glen KnightCommented:
Interesting.

The first thing to do is make sure that all your Exchange servers and Domain Controllers are using a valid internal DNS server for DNS, there should be no ISP changes in here.

Then restart the Exchange Servers one by one and see if this allows you to run the BPA
0
Sam_RendellAuthor Commented:
All servers have fixed IP and DNS settings they only use our two local internal DNS servers. I just checked to make sure no mistake had been made there and it is all as I would expect. I have restarted ex2 and ex3 but I can't restart CAS1 or EX1 at the moment.

ex2 and 3 are still not showing on the best practice whats'it
0
Glen KnightCommented:
Sorry, that picture says that the scan has completed.  You then need to click the link to see the report.
0
Sam_RendellAuthor Commented:
The report just says "Active Directory domain '*****' has an unrecognized Exchange signature. Current DomainPrep version: 12639" but it doesn't display any info for the servers as it did before.
0
Glen KnightCommented:
OK, by all acounts this is a known problem that will be fixed with Exchange 2010 Service Pack 1 :(

See here: http://social.technet.microsoft.com/Forums/en/exchange2010/thread/0d76559d-946b-4915-a54a-ee3914081f2e the accepted answer is from an Exchange MVP
0
Sam_RendellAuthor Commented:
Oh great so the problem I was trying to fix by following MS instruction didn't need fixing and in the process I have broken it further.

I didn't see any mention of it not connecting to servers in the thread.

Maybe I should just ignore the best practice thing for now what do you think?

The original system error has been fixed by applying rollup2 so thanks for that :o) I wish I hadn't run the BPA :(  
0
Glen KnightCommented:
The BPA thing is just a bug so don't worry too much about that it will be fixed in SP1 but your original problem has been resolved so that's great.

>>I didn't see any mention of it not connecting to servers in the thread.
What is it you are unable to connect to?
0
Sam_RendellAuthor Commented:
The first time I ran the BPA it connected to all 4 servers did a little progress bar for each one (this took a couple of minutes) and then finished with ticks instead of red crosses and the results page showed items for each server.

Since rerunning the DomainPrep. It now says pending next to each server then just finishes in 10 secs and shows the red crosses and doesn't show any items for the servers on the results page.
0
Glen KnightCommented:
I think this is all part of the same "bug"
0
Sam_RendellAuthor Commented:
fingers crossed any ways thanks for all your help.

Lookout for my next problem posted shortly ;o)
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
Exchange

From novice to tech pro — start learning today.