Answered by:
Exchange services not starting

Question
-
Dear Team,
The query is about our testing Exchange DB issues and the services on one of the server is not being started,
We found that the exchange services on the server X.X.X.X are not starting and when checked on Event viewer we found the occurrence of below event ids: Event 1004 for exchangefastsearch (Under Application) and Event id: 7031 service control manager( Under System).
The exchange DB status on the problematic server is shown as service down and on the other servers of DAG the status is shown as unknown. We have successfully removed all McAfee components from the problematic server. However still the services on the server is not starting.
NOTE: We have removed the McAfee only from one of the DAG server ,although we have total of 3 servers( 2 in Main site and 1 in DR site)
M.A.FAROOQ
Monday, June 22, 2020 8:32 PM
Answers
-
Hi mafarooq,
Did this problem occur after updating Exchange 2016 CU15?Please note that all servers within a DAG must be running the same version of Exchange.
Based on my knowledge and research, the Third-party tools may cause this error to occur, and couldn't be sure that Exchange server will return to normal work after uninstalling.
Please follow the steps and see if the issue is resolved:
1. Please configure a file share Witness for your DAG.
For more information:Configure Witness Server in Exchange 2016 & 2013.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
2. Please migrate the database on the damaged Exchange server to another primary site and activate it as an active database copy. This will ensure that the data on your damaged server continues to be used.
1) In the EAC, go to Servers > Databases.
2) Select the database whose copy you want to activate.
3) In the Details pane, under Database Copies, click Activate under the database copy you want to activate.
4) Click yes to activate the database copy.
For more information:Activate a mailbox database copy
3. Then you could run the follow command to remove the damaged Exchange server from DAG. After completing the removal, you could try to upgrade the damaged Exchange server to Exchange 2016 CU16, during the upgrade process, your Exchange service will be overwritten and installed.
Remove-DatabaseAvailabilityGroupServer -Identity <> -MailboxServer <>
For more information:Manage database availability group membership.
This Exchange Server 2016 - High Availability and Disaster Recovery Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.
Regards,
Lucas Liu
Exchange Server 2016 - High Availability and Disaster Recovery forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.
For more information, please refer to the sticky post.
- Proposed as answer by Lucas_ LiuMicrosoft contingent staff Thursday, July 16, 2020 9:06 AM
- Marked as answer by mafarooq Monday, July 20, 2020 9:00 PM
Wednesday, July 15, 2020 9:13 AM -
Hi mafarooq,
I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Thanks for your understanding.
This Exchange Server 2016 - High Availability and Disaster Recovery Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.
Regards,
Lucas Liu
Exchange Server 2016 - High Availability and Disaster Recovery forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.
For more information, please refer to the sticky post.
- Marked as answer by mafarooq Monday, July 20, 2020 9:00 PM
Monday, July 20, 2020 1:29 AM
All replies
-
Hi
So manually starting them gives you an error? What error are you getting?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Tuesday, June 23, 2020 4:39 AM -
Hi mafarooq,
According to the error information you provided, these error message show a service stops unexpectedly and how many times it failed.
Please run the command below, it will display specific error messages, you could know which services stop running. Then please try to manually start the service and set the startup type to automatic in Services.msc and see if the issue is resolved.
Get-MailboxDatabaseCopyStatus | FL
For more information you could refer to:Database status showing ServiceDown.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Tuesday, June 23, 2020 7:24 AM -
Thanks Edward for the reply.
When i try to start the services manually for example information store service, i get the below error.
The Microsoft exchange information store on local computer started and then stopped.
some services stop automatically it they are not in use by other services or program.s
M.A.FAROOQ
Tuesday, June 23, 2020 10:10 AM -
Thanks Lucas for the reply.
i executed the above cmdlet on exchange powershell and i got the error as below.
"A server-side administrative operation has failed. The database copy does not have a replication instance running."
When i try to start the services manually for example information store service, i get the below error.
The Microsoft exchange information store on local computer started and then stopped.
some services stop automatically it they are not in use by other services or program.M.A.FAROOQ
Tuesday, June 23, 2020 10:12 AM -
It might be that a windows update applied that caused a system issue or an attempt to upgrade went wrong, I do not know the environment.
Has Mcafee also not caused an issue?
Just want to make sure that you didnt restore the machine from a snapshot at all or backup?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Tuesday, June 23, 2020 10:23 AM -
There are regular windows updates on the server on monthly basis and which update may have cause the issue its difficult to predict.
and also McAfee products has been removed from the server(even from registry)
M.A.FAROOQ
Wednesday, June 24, 2020 7:44 AM -
What CU of Exchange 2016 are you on?
Have you tried doing an upgrade to a newer CU?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Wednesday, June 24, 2020 7:57 AM -
we have recently installed CU15 with Exchange server 2016
M.A.FAROOQ
Wednesday, June 24, 2020 8:14 AM -
Hi Mafarooq,
Have to tried to recover these problematic services by following steps. which may be helpful:
1. Open the service.
2. Right-Click the service that you want to recover, select properties.
3. Click the Recovery tab and specify the recovery actions for the service.
For more information you could refer to:Event ID 7031: Service Crash.
By the way, what specific services cannot be started?
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Wednesday, June 24, 2020 11:24 AM -
Hi
If nothing else works you may need to look at doing a recovery install on a new server with the same and then reseed your DAG.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
- Proposed as answer by Joy_ZhangMicrosoft contingent staff Thursday, June 25, 2020 8:13 AM
Wednesday, June 24, 2020 11:44 AM -
Dear Team,
sorry for the delayed reply.
Kindly be informed that after our investigation we found that the database services are down due to WitnessShareInUse as NONE:
Please advise as we cannot move the active database from problematic server to other server during recovery server(since we had plan to recover the DAG member)
Kindly find the below snapshot from the server.
i executed the command :
Get-DatabaseavailbilityGroup -status | Fl *wktness*, start, stop, operational.
and got the output as
WitnessShareInUse as NONE:
M.A.FAROOQ
- Edited by mafarooq Friday, June 26, 2020 1:32 PM
Friday, June 26, 2020 1:29 PM -
Dears,
Is there any support in this subject.
Appreciate your reply.
M.A.FAROOQ
Saturday, June 27, 2020 8:19 PM -
Hi mafarooq,
According to the information you provided, it is still not possible to confirm whether the service fails to start is a problem in the direction of windows or a problem in the direction of Exchange.
If it is an Exchange problem, even if the recovery operation is performed on the new server, the recovered Exchange server will still have problems.
So if you could, please check the logs in Event Viewer, such as Application, Security, and System. If there are related errors, please share with us, but please note that hidden your personal information .
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Tuesday, June 30, 2020 9:57 AM -
Dear Lucas,
i really appreciate your response on the ongoing subject:
The following Event ids are found
Event 1004 for exchangefastsearch (Under Application)
Event id: 7031 service control manager( Under System).
M.A.FAROOQ
Tuesday, June 30, 2020 2:44 PM -
Hi mafarooq,
About Event id 7031,I provided a related solution above, What is the result of the operation?
According to the information you provided, more than one Exchange service can't be starting, it should be noted that there are dependencies between Exchange services, so before you start the Exchange service, please make sure that the relevant Exchange service has been started.
For more information you could refer to:Overview of Exchange services on Exchange servers.
If you could, please share the detailed error information recorded in the log, which will include the specific stopped service. Please note that hidden your personal information.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Thursday, July 2, 2020 7:51 AM -
Hi Mafarooq,
Can you please check if Microsoft Exchange Active Directory Topology service is started or not? If not can you try to start it and if it fails, check the event ID's under Application, System. If this service is not started, then there could be issues with communication between Exchange and Active directory, permissions, etc.
Did the issue started after the CU15 installation, if so did the installation complete successfully?
Thanks,
Ashok M My blog
________________________________________________________________
Please mark the reply as an answer if you find it is helpful :-)
________________________________________________________________Thursday, July 2, 2020 9:22 AM -
Hi Ashok,
thanks for the reply.
Kindly be informed that Microsoft Exchange Active Directory Topology service is running and the other servcies which are running are
Microsoft Exchange Anti-Spam, Microsoft Exchange Health Manager Services are running and all other exchange services are not starting.
M.A.FAROOQ
Thursday, July 2, 2020 12:31 PM -
Hi Lucas,
thanks for the usual support.
Kindly be informed that i tried to restart the Exchange Information Store Service and its not starting
i have attached the screenshots for the status and application event.
M.A.FAROOQ
Thursday, July 2, 2020 12:43 PM -
M.A.FAROOQ
Thursday, July 2, 2020 12:43 PM -
Hi Mafarooq,
Have you tried restarting the Microsoft Exchange Active Directory Service or a server reboot?
Event id 4999 states that the process did not load but for the actual error, we need to check the events generated before/after this for Information store for more detailed information.
Thanks,
Ashok M My blog
________________________________________________________________
Please mark the reply as an answer if you find it is helpful :-)
________________________________________________________________- Proposed as answer by Ashokm_14 Wednesday, July 8, 2020 6:11 AM
Thursday, July 2, 2020 2:04 PM -
Hi mafarooq,
Could you share detailed error information about event id 1004 and event id 7031, which will indicate which services are suddenly terminated.
If you find other related error information, please share with us.
Please note that hide your private information.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
- Proposed as answer by Lucas_ LiuMicrosoft contingent staff Tuesday, July 7, 2020 6:43 AM
Monday, July 6, 2020 10:59 AM -
Hi ashok,
I restarted the Microsoft Exchange Active Directory Service and also did a reboot for the server.
i will share the events shortly.
M.A.FAROOQ
Wednesday, July 8, 2020 2:48 PM -
Hi Mafarooq,
Is it still the same? And yes, share the events.
Thanks,
Ashok M My blog
________________________________________________________________
Please mark the reply as an answer if you find it is helpful :-)
________________________________________________________________Wednesday, July 8, 2020 5:59 PM -
Hi Ashok,
Thanks for the follow up , appreciated.
Again the issue persists.
kindly find the events when trying to restart the information store service.
M.A.FAROOQ
Thursday, July 9, 2020 1:09 PM -
Hi mafarooq,
Have you made any settings or changes before this issue occurred?
Are you trying to start other services? Will you get the same error?
1. I noticed that the service shown in your error log is Microsoft Exchange Mailbox Transport Delivery service , Does this error occur when you start it or when you start the MSExchangeIS service?
2. Please open the IIS and make sure that all the application pools are started.
3. According to the Microsoft’s official document, we could know that whether the Microsoft exchange information store service can run normally is related to RPC. Have you open the firewall? If yes, please try to temporarily turn it off and start the service again.
4. According to my research, if the IPv6 is not enabled and the Exchange server is not synchronized with the DC time, the A service cannot start normally. So please try to enable the IPv6 on the Exchange server and DC. And please check if the Exchange server is synchronized with the DC time.
Regards,
Lucas Liu
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Saturday, July 11, 2020 7:22 AM -
Dear Lucas,
kindly find the reply to the below queries.
1. I noticed that the service shown in your error log is Microsoft Exchange Mailbox Transport Delivery service , Does this error occur when you start it or when you start the MSExchangeIS service?
Reply: When i start the service MSExchangeIS service
2. Please open the IIS and make sure that all the application pools are started.
Reply: All the IIS applicaitn pools are started and working (screenshot is attached)
3. According to the Microsoft’s official document, we could know that whether the Microsoft exchange information store service can run normally is related to RPC. Have you open the firewall? If yes, please try to temporarily turn it off and start the service again.
Reply: As per security concerns FireWall cannot be stopped.
4. According to my research, if the IPv6 is not enabled and the Exchange server is not synchronized with the DC time, the A service cannot start normally. So please try to enable the IPv6 on the Exchange server and DC. And please check if the Exchange server is synchronized with the DC time.
M.A.FAROOQ
Saturday, July 11, 2020 10:00 AM -
Hi mafarooq,
Did this problem occur after updating Exchange 2016 CU15?Please note that all servers within a DAG must be running the same version of Exchange.
Based on my knowledge and research, the Third-party tools may cause this error to occur, and couldn't be sure that Exchange server will return to normal work after uninstalling.
Please follow the steps and see if the issue is resolved:
1. Please configure a file share Witness for your DAG.
For more information:Configure Witness Server in Exchange 2016 & 2013.
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
2. Please migrate the database on the damaged Exchange server to another primary site and activate it as an active database copy. This will ensure that the data on your damaged server continues to be used.
1) In the EAC, go to Servers > Databases.
2) Select the database whose copy you want to activate.
3) In the Details pane, under Database Copies, click Activate under the database copy you want to activate.
4) Click yes to activate the database copy.
For more information:Activate a mailbox database copy
3. Then you could run the follow command to remove the damaged Exchange server from DAG. After completing the removal, you could try to upgrade the damaged Exchange server to Exchange 2016 CU16, during the upgrade process, your Exchange service will be overwritten and installed.
Remove-DatabaseAvailabilityGroupServer -Identity <> -MailboxServer <>
For more information:Manage database availability group membership.
This Exchange Server 2016 - High Availability and Disaster Recovery Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.
Regards,
Lucas Liu
Exchange Server 2016 - High Availability and Disaster Recovery forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.
For more information, please refer to the sticky post.
- Proposed as answer by Lucas_ LiuMicrosoft contingent staff Thursday, July 16, 2020 9:06 AM
- Marked as answer by mafarooq Monday, July 20, 2020 9:00 PM
Wednesday, July 15, 2020 9:13 AM -
Hi mafarooq,
I'm here to confirm with you if your issue has been resolved. If the problem is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.
Thanks for your understanding.
This Exchange Server 2016 - High Availability and Disaster Recovery Forum will be migrating to a new home on Microsoft Q&A, please refer to this sticky post for more details.
Regards,
Lucas Liu
Exchange Server 2016 - High Availability and Disaster Recovery forum will be migrating to a new home on Microsoft Q&A! We invite you to post new questions in the new forum.
For more information, please refer to the sticky post.
- Marked as answer by mafarooq Monday, July 20, 2020 9:00 PM
Monday, July 20, 2020 1:29 AM -
Thanks all for the support,
I have done the recovery of exchange server and will be following the procedures.
Performing an Exchange Server Recovery
M.A.FAROOQ
Monday, July 20, 2020 9:02 PM