Muhammad Asif
asked on
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.
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.
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.
Have you rebooted the server?
Please provide the above information and see if a reboot fixes the issue.
ASKER
The Exchange version is 2016 and we have run the IISCrypto tool ( https://www.nartac.com/Products/IISCrypto) 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.
We have two domain controller in two sites.
ASKER
Any suggestions?
Have you rebooted the Domain Controllers? if not, I would suggest to reboot them following the exchange server reboot and check.
ASKER
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?
Hi,
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.
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.
ASKER
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: https://social.technet.microsoft.com/Forums/en-US/a858858c-71f4-4968-a49b-25559019148f/exchange-2016-owa-will-not-open-in-firefox-or-chrome?forum=Exch2016SD
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_Troubleshooti ng 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.Rpc Exception: 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.Rpc ServerBase .ThrowRpcE xception(S tring message, Int32 rpcStatus) +138
Microsoft.Exchange.Rpc.Rpc ServerBase .RegisterS erver(Type type, ObjectSecurity sd, UInt32 desiredAccess, ValueType mgrTypeGuid, Void* mgrEpv, String annotation, Boolean isLocalOnly, Boolean autoListen, UInt32 maxCalls) +422
Microsoft.Exchange.Data.Ap plicationL ogic.Proce ssAccessMa nager.Regi sterCompon ent(IDiagn osable diagnosable) +547
Microsoft.Exchange.HttpPro xy.ProxyAp plication. <Applicati on_Start>b __0() +42
Microsoft.Exchange.Common. IL.ILUtil. DoTryFilte rCatch(Act ion tryDelegate, Func`2 filterDelegate, Action`1 catchDelegate) +32
Microsoft.Exchange.HttpPro xy.ProxyAp plication. Applicatio n_Start(Ob ject sender, EventArgs e) +262
[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
System.Web.HttpApplication Factory.En sureAppSta rtCalledFo rIntegrate dMode(Http Context context, HttpApplication app) +529
System.Web.HttpApplication .RegisterE ventSubscr iptionsWit hIIS(IntPt r appContext, HttpContext context, MethodInfo[] handlers) +169
System.Web.HttpApplication .InitSpeci al(HttpApp licationSt ate state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +169
System.Web.HttpApplication Factory.Ge tSpecialAp plicationI nstance(In tPtr appContext, HttpContext context) +396
System.Web.Hosting.Pipelin eRuntime.I nitializeA pplication (IntPtr appContext) +333
[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
System.Web.HttpRuntime.Fir stRequestI nit(HttpCo ntext context) +525
System.Web.HttpRuntime.Ens ureFirstRe questInit( HttpContex t context) +124
System.Web.HttpRuntime.Pro cessReques tNotificat ionPrivate (IIS7Worke rRequest wr, HttpContext context) +700
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2106.0
I have installed IIS Crypto to resolve the SSL issue on Exchange 2106 CU5 as mentioned in this link: https://social.technet.microsoft.com/Forums/en-US/a858858c-71f4-4968-a49b-25559019148f/exchange-2016-owa-will-not-open-in-firefox-or-chrome?forum=Exch2016SD
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_Troubleshooti
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.Rpc
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.Rpc
Microsoft.Exchange.Rpc.Rpc
Microsoft.Exchange.Data.Ap
Microsoft.Exchange.HttpPro
Microsoft.Exchange.Common.
Microsoft.Exchange.HttpPro
[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
System.Web.HttpApplication
System.Web.HttpApplication
System.Web.HttpApplication
System.Web.HttpApplication
System.Web.Hosting.Pipelin
[HttpException (0x80004005): RpcServerUseProtseq TCP/IP]
System.Web.HttpRuntime.Fir
System.Web.HttpRuntime.Ens
System.Web.HttpRuntime.Pro
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2106.0
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have found a solution by myself.
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.