We help IT Professionals succeed at work.

SBS 2011 Exchange issues

jts2020
jts2020 asked
on
478 Views
Last Modified: 2016-05-17
After i installed some updates Sunday night to my SBS 2011 server my Exchange System Attendant  will not start at all.
When trying to start manually, i get:
Windows could not start the Microsoft Exchange System Attendant service on local computer.
Error 1067: the process terminated unexpectedly.

also, the Microsoft Exchange Replication keeps crashing.
event id is 7031.
The Microsoft Exchange Replication service terminated unexpectedly. It has done this 1 (times). the following corrective action will be taken in 5000 milliseconds. Restart service.

My users can't connect to to check new email.
Previous auto email forwards still work (meaning email auto forwards previously configured in exchange still work so when i send email to user@crashedserver.com it still goes to user@mybusiness.com

i spent the entire day restoring the server from a full backup (saturday night) backup hoping it was going to be fix since the problem happened sunday night after doing updates and a restart. But that didn't work.
i was able to fully restore everything but the services are still down.

Finally, running the Microsoft Windows Server Solutions Best Practices Analyzer reports this errors:
1. Windows SBS is not the Domain Naming Master
2. Windows SBS is not the Infrastructure Master
3. Windows SBS is not the Primary Domain Controller Master
4. Windows SBS is not the Relative ID (RID) Master
5. Windows SBS is not the Schema Master.

thanks,

jts2020
Comment
Watch Question

strivoliIT Manager
CERTIFIED EXPERT

Commented:
What kind of full backup did you restore? Was it a BRM+SS+C Drive?
Where is Exchange installed? Is it on C: on on another drive?

Author

Commented:
I did a full restored (bare metal to new hard drives).
the hardware setup was
RAID1 with two 250GB Dell OEM HDs (C: drive)
One 2TB where some Windows\Temp\ files where located (Y: drive)
Another 2TB where the Exchange Database was moved via the SBS Server 2011 Standard Console (Z: drive)
But Exchange was initially installed in the default C:\ drive and only the data was moved. The actual program is still on the C:\Program Files..
i was running out of space on the C: drive so i had to moved it.
strivoliIT Manager
CERTIFIED EXPERT

Commented:
It seams there is another server in the same domain. Is it an AD server?

Author

Commented:
it's the only server.
I am Running SBS 2011.

However, i am also running VM Ware Workstation with 1 Server 2008 R2 and 3 Windows 7 Pro as guests (this are mainly use just for remote users to connect from offsite via RDP).
But the windows server 2008 it's only a member servers, nothing else.
strivoliIT Manager
CERTIFIED EXPERT

Commented:
One of the first Exchange services involved is the Information Store. Is it up? If it isn't can you start it manually? If it fails, even manually, does the system return any useful info even watching at the Event Log Viewer?

Author

Commented:
Information Store start automatically just fine.
the only two services that fail are
Exchange Replication - keeps crashing every couple of minutes
Exchange System Attendant - will not start at all.
i get error 1067: The Process terminated unexpectedly.

i'll attached some pics i took with my phone
IMG-1459.JPG
IMG-1458.JPG
IMG-1457.JPG

Author

Commented:
looking more at the Exchange Mgt Console.
Right-clicking the Public Folder Database and trying to Mount the Database i get:
Error 0x6d9 (there are no more endpoints available from the endpoint mapper) from cli_MountDatabase3

also,
 Couldn't mount the database that you specificied. Specified database: Public Folder Database 0166175050; Error code: An Active Manager operation failed. Error, The Microsoft Exchange Replication service may not be running on server SBS.domain.local.
Specified RPC error message: Error 0x6d9

Thanks,

Author

Commented:
and the Main Mailbox Database shows as Unknown under the Monted title of the exchange Database Management (while the Public shows as Dismounted).
strivoliIT Manager
CERTIFIED EXPERT

Commented:
The 1st and 2nd pic you posted suggest you should check if 3 services are running. Are they running?
Andy MIT Systems Manager
CERTIFIED EXPERT

Commented:
"Finally, running the Microsoft Windows Server Solutions Best Practices Analyzer reports this errors:
1. Windows SBS is not the Domain Naming Master
2. Windows SBS is not the Infrastructure Master
3. Windows SBS is not the Primary Domain Controller Master
4. Windows SBS is not the Relative ID (RID) Master
5. Windows SBS is not the Schema Master."

This would indicate that the FSMO roles have been moved off of the server. I've seen SBS have all sorts of problems when this happens - I'd manually check each role to ensure the server still owns it. Not sure if this is actually related to the exchange issues but it's worth looking at due to the way SBS integrates everything together.

Author

Commented:
all services are running (again except for System Attendant and Exchange Replication).

obviously, i would not move the FSMO or any role from my only Server/DC.
all this happened out of nowhere after restarting the server.

how can i check each role manully?
Andy MIT Systems Manager
CERTIFIED EXPERT

Commented:
Hi

The following should help you determine the roles owner accordingly:

http://blogs.technet.com/b/mempson/archive/2007/11/08/how-to-find-out-who-has-your-fsmo-roles.aspx
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.