I've had a reoccuring problem with Exchange becoming unresponsive. When the issue is noticed, if i try to sign into the server via RDP or at the Console it hands during logon and the only solution is to perform a hard reset. In the Application Logs I find MANY event ID 1 MSExchange Autodiscover referring to unable to locate the Global Catalog in the forrest. I also find several Event ID 1309 ASP.NET error messages related to OWA. http exception request time out As well as MS Exchange EdgeSync Event ID 1026 Topology load generated transient exception Active Directory operation failed on name.domain.local. This error could have been caused by user input or by the Active Directory server being unavailable. Please retry at a later time. Additional information: Active directory response: The operation was aborted because the client side timeout limit was exceeded. .. EdgeSync must be able to acquire current Exchange topology data from the Active Directory directory service to properly operate. The Edge Transport server will attempt to load the topology again. There is no pattern to the times in which it occurs, it occurs during peak and off-peak hours. I do find errors in the System Log taht relate to NTFS File system structure on the disk is corrupt and unusable, i will run a chkdsk during our off peak hours. Although i'm not totally convinced that's the actual cause of the probelm. Is there anything else that could cause this issue?

Version information? Does EXBPA show anything? If you are getting errors about the file system then that would be of a concern which should be checked. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.