Windows could not stop the microsoft exchange active directory topology service

Windows could not stop the microsoft exchange active directory topology service Error 1061: the service cannot accept control messages at this time

I have restarted the service and getting the above mentioned error while starting the active directory topology service and other Exchange front-end service.  Please comment if any one face the same issue.
Muhammad AsifSenior Solutions ArchitectAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Radhakrishnan RSenior Technical LeadCommented:

Have you tried to restart the Domain Controller instead of the Exchange server? Usually this error get fix if you restart the DC. If issue still persists, look at your DC and see if it has any issues.
Scott CSenior EngineerCommented:
First off....What version of Server and what version of Exchange?

Have you rebooted the server?  

Please provide the above information and see if a reboot fixes the issue.
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
The Exchange version is 2016 and we have run the IISCrypto tool ( to resolve the SSL issue.  As it required to restart the server so I have just restart the server.

We have two domain controller in two sites.
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.

Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Any suggestions?
Radhakrishnan RSenior Technical LeadCommented:
Have you rebooted the Domain Controllers? if not, I would suggest to reboot them following the exchange server reboot and check.
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
Should I need to reboot all the Exchange servers? This is production environment so it is difficult to restart the domain controllers. Can you please let me know why I need to reboot the domain controllers?
Radhakrishnan RSenior Technical LeadCommented:

The NetLogon service determines site association membership at startup and every 15 minutes. The Microsoft Exchange Discovery Topology service maintains this information by caching the information in the msExchServerSite attribute of the Exchange server object, in order to reduce load on active directory and DNS. Therefor, you might need to restart the DC's and Exchange.
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
It seems that  I have not explained the issue properly. Here I am rephrasing the issue.

I have installed IIS Crypto to resolve the SSL issue on Exchange 2106 CU5 as mentioned in this link:

After it as its required to restart the server so I have restarted it. However after restarting the server, Microsoft Echange frontend transport service is trying to start but it is not starting.  Microsoft Exchange Transport service is also not starting and I can not start or stop it as both options ( start or stop) are grayed out.

The other services Microsoft Information is also stop. I try to open Powershell then I am getting this error

New-PSSession : [main-ex02.domain.local] Connecting to remote server main-ex02.domain.local failed with the following
error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response
from the destination computer. The content type is absent or invalid. For more information, see the
about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...

If we try to browse the ECP then we are getting this error:

Server Error in '/ecp' Application.

RpcServerUseProtseq TCP/IP
  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

 Exception Details: Microsoft.Exchange.Rpc.RpcException: RpcServerUseProtseq TCP/IP

Source Error:

 An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.  

Stack Trace:

[RpcException: RpcServerUseProtseq TCP/IP]
   Microsoft.Exchange.Rpc.RpcServerBase.ThrowRpcException(String message, Int32 rpcStatus) +138
   Microsoft.Exchange.Rpc.RpcServerBase.RegisterServer(Type type, ObjectSecurity sd, UInt32 desiredAccess, ValueType mgrTypeGuid, Void* mgrEpv, String annotation, Boolean isLocalOnly, Boolean autoListen, UInt32 maxCalls) +422
   Microsoft.Exchange.Data.ApplicationLogic.ProcessAccessManager.RegisterComponent(IDiagnosable diagnosable) +547
   Microsoft.Exchange.HttpProxy.ProxyApplication.<Application_Start>b__0() +42
   Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(Action tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate) +32
   Microsoft.Exchange.HttpProxy.ProxyApplication.Application_Start(Object sender, EventArgs e) +262

[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
   System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +529
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +169
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +169
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +396
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +333

[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +525
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +124
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +700


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2106.0
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
We have managed to resolve this case. The issue was comming to due to an invalid registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet

The internet registry making all the issues under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc.  We have deleted the internet registy from HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc, rebooted the server and everything is working again.
This was debugged by Microsoft Team for another person and fortunitly he has posted the solution. For reference please refer to this link:

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
Muhammad AsifSenior Solutions ArchitectAuthor Commented:
I have  found a solution by myself.
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

From novice to tech pro — start learning today.