Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 19214

Exchange 2010 Hub Transport Error

$
0
0

I get this error during the Hub Transport Role installation: 

Error:

The following error was generated when "$error.Clear();

         if ($RoleStartTransportService)

         {

                 start-SetupService -ServiceName MSExchangeTransport

         }

       " was run: "Service 'MSExchangeTransport' failed to reach status 'Running' on this server.".

Service 'MSExchangeTransport' failed to reach status 'Running' on this server.

I've done the following:

  •  Administrative Tools - Local Security Policy - Local Policies - User Rights Assignment, and add the Exchange Servers group in Manage auditing and security log Properties.
  • Active Directory Users and Computers – domain.com – Builtin, and add the Exchange Trusted Subsystem as a member of the Administrators group.
  • Navigated to C:\Windows\System32\Drivers\Etc and open the hosts file in notepad. Delete theIPV6 entry.
  • Enabled IPv6 in Local Area Connection
  • Open Registry Editor.  Locate the following registry subkey:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters.  In the details pane, click New, and then click DWORD (32-bit) Value.Type DisabledComponents, and then press ENTER. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.
  • netsh int tcp set global chimney=disabled

And I see this in the Application log:

Log Name:      Application
Source:        MSExchange ADAccess
Date:          12/28/2012 3:37:32 PM
Event ID:      2114
Task Category: Topology
Level:         Error
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1428). 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.





Viewing all articles
Browse latest Browse all 19214

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>