Ron Murray
2022-Oct-12 02:24 UTC
[Samba] Exchange Active Directory Topology service crashes over samba box
I'm running samba on a Debian bookworm system, connected to our AD domain. Worked fine until a week ago, when Exchange crashed on an "Event 4027, MSExchange ADAccess". The error message muttered something about "Process msexchangerepl.exe: WCF request to the Microsoft Exchange Active Directory Topology service on server (TopologyClientTcpEndpoint (localhost) failed.? Active Directory server <my samba box> is not available. Error message: Active directory response: A local error occurred". This upset my boss, so I turned off all the samba daemons and disabled them. All was fine until last night, when Exchange crashed again, this time with "Event 1003, MSExchange Front End HTTP Proxy". "[Unknown] An iinrenal server error occurred. The unhandled exception was: Microsoft.Exchange.Data.Directory.ADTransientException: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error detasils Active Direcvtory server <my samba box> is not available. Error message: Active directory response: A local error occurred.. --->System.ServiceModel.FaultException`1[Microsoft.Exchange.Data.Directory.TopologyDiscovery.TopologyServiceFault]: Active Directory server <my samba box> is not available. Error message: Active directory response: A local error occurred." Anyone seen anything like this before? Any suggestions on how to fix it? Thanks, -- Ron Murray <rjmx at rjmx.net> PGP Fingerprint: 4D99 70E3 2317 334B 141E 7B63 12F7 E865 B5E2 E761 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: <http://lists.samba.org/pipermail/samba/attachments/20221011/c7b0bc93/signature.sig>
Rowland Penny
2022-Oct-12 05:48 UTC
[Samba] Exchange Active Directory Topology service crashes over samba box
On 12/10/2022 03:24, Ron Murray via samba wrote:> I'm running samba on a Debian bookworm system, connected to our AD > domain. Worked fine until a week ago, when Exchange crashed on an > "Event 4027, MSExchange ADAccess". The error message muttered something > about "Process msexchangerepl.exe: WCF request to the Microsoft > Exchange Active Directory Topology service on server > (TopologyClientTcpEndpoint (localhost) failed. > > Active Directory server <my samba box> is not available. Error message: > Active directory response: A local error occurred". > > This upset my boss, so I turned off all the samba daemons and disabled > them. All was fine until last night, when Exchange crashed again, this > time with "Event 1003, MSExchange Front End HTTP Proxy". > > "[Unknown] An iinrenal server error occurred. The unhandled exception > was: Microsoft.Exchange.Data.Directory.ADTransientException: The call > to Microsoft Exchange Active Directory Topology service on server > 'TopologyClientTcpEndpoint (localhost)' returned an error. Error > detasils Active Direcvtory server <my samba box> is not available. > Error message: Active directory response: A local error occurred.. --- >> System.ServiceModel.FaultException`1[Microsoft.Exchange.Data.Directory > .TopologyDiscovery.TopologyServiceFault]: Active Directory server <my > samba box> is not available. Error message: Active directory response: > A local error occurred." > > Anyone seen anything like this before? Any suggestions on how to fix > it? > > Thanks,I have to ask, why are you running an unreleased Debian version in production ? The other questions I have to ask, how are you running Samba (DC, Unix domain member) and how is exchange connected to it ? Rowland