Microsoft Excahange Transport Service Not Starting
Here is my Problem We had a Windows 2000, Exchange 2000 Environment. i am trying to migrate to windows 2003-exchange 2007. i have managed to migrate my domain controller and removed windows 2000 domains and ready with windows 2003 domain controller. on second server i have installed all the prerequiesit for exchange--started exchange 2007 server installation. half theway installation failed saying that Microsoft Excahange Transport Service Not Starting, did a lots of reserach tried no dovelopment. i tried to uninstall..again stop when it reach transport service...i run DCDIAG to check my DNS, DC all the test passed...Domain controller is Windows 2003 R2 with SP2. Here are the application event Event ID.2116 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1184). The domain controller SEEFDC.seefproperties.com is running Windows (Unknown Operating System) (Unknown Service Pack). Exchange Active Directory Provider requires that domain controllers are running Windows Server 2003 Service Pack 1 or later versions of Windows. Event ID 2080 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1184). Exchange Active Directory Provider has discovered the following servers with the following characteristics: (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version) In-site: SEEFDC.seefproperties.com CDG 1 7 7 1 0 0 1 7 0 Out-of-site: Event ID 2114 Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1184). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Your help is apreciated...
September 30th, 2007 9:21am

Your server does not have the SACL Right That means that Exchange does not have the permissions to access the server DSAccess does not use any domain controller that does not have permissions to read the SACL on the nTSecurityDescriptor attribute in the domain controller. You must have at least one server that satisfies each role (C, D, or G), that is reachable for that role (the appropriate bit flag connected by an OR value in the Reachability column), and that shows 1 in the SACL right column. If you do not have these servers, confirm that the domain controller that shows 0 in the SACL right column has been domain-prepped Have you ran Setup /PrepareDomain? Can you run Setup /PerpareDomain or Setup /PrepareAllDomains again? Deli
Free Windows Admin Tool Kit Click here and download it now
October 3rd, 2007 1:31am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics