Hi, I'm having problems with my Exchange 2007 Server, basically the services wont. The Active directory services fails with an event error :-The Microsoft Exchange Active Directory Topology Service service terminated with service-specific error 2147942414 (0x8007000E).Any ideas?Best Regards, Tim

Hey Tim,We're having the exact same problem on a fresh install on Windows Server 2008 running Exchange Server 2007 SP1.We've found some documentation pointing to the Remote Registry service - it must be running for Exchange. Ours was disabled so I'm rebooting with it set to Automatic now. I'll let you know the outcome....No go. I'll keep you updated.

I just started experiencing this problem as well after installing "Symantec Information Foundation Mail Security For MSE 6.0.5.218". I'm not positive it is related but it sure looks likely. Has anyone figured out how to fix it? I'm running out of ideas. Simply uninstalling the Symantec product has not fixed the problem.

Me too - I ran into this a couple of weeks ago on a new 2008 x64 box with Exchange 2007 and MSE 6.0.5.218. I still have not gotten fixed yet. I was hoping that perhaps MSE 6.0.6 (which was released yesterday) might help, but it hasn't. Fortunetly this is not a production Exchange server yet, but was suppose to be already...

Yeah its really bad... I wish the installer would have said it wasnt compatible with Windows Server 2008! I mean its been out for ages already, I just assumed that it was...Oh well... I demoted the Win2k8 DC (Exchange 2k7 SP1 is on the same box) and I have renamed the box and created two HyperV virtual servers. One has become the new Win2k8 DC and the other is going to be the Exchange 2007 server. I am going to follow the instructions found @ http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3479592&SiteID=17&mode=1 to recover my exchange server databases back to the virtual server which has the same computer name that the host server previously had for the exchange install. I figure it'll be better this way... I was just a bit scared to be doing this with a release candidate (RC1) of Hyper-V which is why I didnt do this in the first place... but oh well! GL getting yours fixed... best bet if your Exchange server isnt a DC is to do what is suggested in the instructions in the above URL. Let me know how it turns out, I'll do the same...

The resolution is @ http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3482957&SiteID=17&mode=1. Shame I was too impatient to wait lol...

We traced our problem to installing Symantec AntiVirus - it totally crashed Exchange. Uninstalling Symantec still didn't fix the problem. It created some permanent damage.We're still waiting for Symantec to get an Exchange 2008 and Windows Server 2008 supported version. We've been checking regularly, but as of today, Friday, June 13, 2008, the new verison has not arrived.

Hi GuysI had same problem on my exchange setup and I couldnt figured it out myself . Microsoft engineer helped me to fix the issue by using KB article http://support.microsoft.com/kb/954204/en-us This issue occurs because Symantec Mail Security modifies the following registry subkey to write event logs only for Symantec applications: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\Application\CustomSDTherefore, when Exchange services tries to log events in the event log, Exchange services receives an "access denied" error message, and Exchange services cannot be started. Back to the top RESOLUTION Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in WindowsTo resolve this issue, follow these steps: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then right-click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\ApplicationNotice that there is a value for the CustomSD registry entry. This value resembles the following value: "O:BAGUDA;;CC;;;S-1-5-21-1564639177-1417944463-942302423-13664)(A;;CC;;;S-1-5-21-1564639177-1417944463-942302423-13665)" 3. Right-click the CustomSD entry, and then click Delete. 4. Restart the computer.Good luck