Hi AllI have just found that our exchange server is missing the system attendant service. When trying to run a change from setup, it fails withMailbox Role FailedError: The following error was generated when '$error.Clear; start-SetupService -ServiceName MSExchangeSA' was run: 'Service 'MSExchangeSA' isn't installed on this server.'
- Microsoft Exchange System Attendant 2010
- Exchange 2016 Migration Cannot Open Mailbox System Attendant
.Service 'MSExchangeSA' isn't installed on this server.I have confirmed the service is missing not just stopped or disabled.This was a transition install from a 2003 Exchange box around 18 Months ago. There didn't seem to have any errors during the transition. However I have just been made aware the OAB is not updating and I'm assuming it is because the SA service is not running.All other parts of Exchange are running fine, OWA, Outlook Anywhere and Active Sync.Is there any other way to install this services?Cheers. SystemAttendant is responsible for Free+Busy, OAB generation e.t.c.- If Exchange on a DC?- Most of the times SA not starting would be due to Network related issues.- Have you added the bootpause key and resumed the setup and do you still face the issue with the setup failing?- the current setup you have is not optimal as the mailbox role is partially configured and we have to fix it.What other Exchange roles do you have on this box? Was this a fresh installation (when first deployd) or has there been any kind of upgrade option like (SP1 to SP2) performed?- Fix the network / dns related issues and resume the setup and ping back errors if you encounted any!M.P.K ( Exchange 2003/2007/2010/E15(2013)) Please remember to click “Vote As Helpful' if it really helps and 'Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question.
This Informationis provided is 'AS IS' and confers NO Rights!! HiIt's not that the service wont start, the service is not install. Because it is not there OAB generation fails.If you try to modify exchange from the progams option on the control panel you get an errorSummary: 3 item(s). 1 succeeded, 1 failed.Elapsed time: 00:00:06Preparing SetupCompletedElapsed Time: 00:00:03Mailbox RoleFailedError:The following error was generated when '$error.Clear; start-SetupService -ServiceName MSExchangeSA' was run: 'Service 'MSExchangeSA' isn't installed on this server.' .Service 'MSExchangeSA' isn't installed on this server.Elapsed Time: 00:00:02Finalizing SetupCancelledThis was a migration from Exchange 2003.The old 2003 exchange server was a DC, however the new exchange server is not.The old exchange server is still on the network, however all Exchange services are stopped, but the system attendant service is on this old server.
If I complete the uninstall of Exchange 2003 from this box, exchange 2010 on the new server breaks.Can not install SP1 or SP2 and I think this is because SA is missingI need to work out how to get the SA role onto this exchange box so OAB works and then I can complete removal from the old server. If Exchange on a DC?- Most of the times SA not starting would be due to Network related issues.- Have you added the bootpause key and resumed the setup and do you still face the issue with the setup failing?- the current setup you have is not optimal as the mailbox role is partially configured and we have to fix it.What other Exchange roles do you have on this box? Was this a fresh installation (when first deployd) or has there been any kind of upgrade option like (SP1 to SP2) performed?- Fix the network / dns related issues and resume the setup and ping back errors if you encounted any!Have you followed this? Did you check for Network related issues and did you fix them in case if you have any?M.P.K ( Exchange 2003/2007/2010/E15(2013)) Please remember to click “Vote As Helpful' if it really helps and 'Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. This Informationis provided is 'AS IS' and confers NO Rights!!
We're in the process of upgrading our servers from Exchange 2010 to Exchange 2013. During the installation of Exchange 2013 some things went wrong as why it could not be fully installed. It stopped at step 7 of 15 or so. After reinstalling the server and doing a disaster recovery, Exchange 2013 installed successfully (well, 'successfully' till now).As we configured the new Exchange installation, we discovered that the Mailbox Database was unmounted. We discovered the Mailbox Database files weren't created: there are no transaction logs nor is there an.edb file at the path the database should be stored. I guess this is due to the failed installation which we recovered using Disaster Recovery.Is there a way to somehow re-create this database, recover it or just completely remove Exchange 2013 from the server and AD so we can just start over again and do it right this time (uninstalling is impossible at the moment cause it thinks there are still mailboxes (Migration Mailbox, that is) being stored in the missing database, which we can't delete cause then it errors out saying the database can't be mounted)?
Can you disable the mailbox and try again? I was able to disable the mailbox on my install with the database it resides in dismounted. Get-Mailbox -Arbitration -Database nameofmissingdb ft nameDisable-Mailbox Migration.guid -ArbitrationMake sure to record the actual name (or find it in the Users container in ADUC). After you get a mailbox database online, you can run: Enable-Mailbox Migration.guid -ArbitrationSet-Mailbox Migration.guid -Arbitration -ProhibitSendQuota '300 MB'Here's a helpful link that goes through the process with other system mailboxes. You said it was the existence of the mailbox preventing you from proceeding with the uninstall.
Microsoft Exchange System Attendant 2010
Exchange 2016 Migration Cannot Open Mailbox System Attendant
Are you also rebuilding AD? If not, it's still there. You'll have to use adsiedit to remove it from Configuration Services Microsoft Exchange ORGNAME Administrative Groups Exchange Administrative Group (FYDIBOHF23SPDLT) Databases.
When you delete it here, it's deleted from Exchange. That will leave you with orphaned system mailboxes though, for which you'll have to follow the instructions above to recreate.–Jun 21 '13 at 23:10.