MSExchangeTransport service does not start on reboot

Is IPv6 enabled on the exchange server NIC. If not enable it a see if it makes any difference.

A lot of posts talked about that and I tried enabling and disabling with the registry hack but it still does not start.

Thanks
-Dimitry

Go to ADSIEdit and change the following values:
1.…Services\Microsoft Exchange\CN=Organization\CN=Transport Settings->properties->Attribute:SubmissionContentLength
This value is not set by default, change it to 20MB (20480).
2….services\Microsoft Exchange\CN=Organization->properties->Attribute:DelivContLength
This value is not set by default, change it to 20MB (20480)

this shud work 100% !!

What about configuring the service retry interval a d a delayed start. My dogfood lab does this also and I just configured a delayed start for the service.

I am always weary about making changes to adsi.   If everything else fails then I will try that change.

I did do the retry interval on the service but did not set the delayed start.   I did not know about the delayed start option.   I will try rebooting this evening and will let you know the outcome.

I did check my adsi and
1.…Services\Microsoft Exchange\CN=Organization\CN=Transport Settings->properties->Attribute:SubmissionContentLength
This value is not set by default, change it to 20MB (20480).    .........

This value was set to 10240
 
2….services\Microsoft Exchange\CN=Organization->properties->Attribute:DelivContLength
This value is not set by default, change it to 20MB (20480)

This value was not set.

I saw other people post about this but do not understand how this would cause it from not starting.

Thanks
-Dimitry

did u try changing the value?

Not yet...have to wait till this evening when everyone is gone so I can reboot the server.    I will let you know if it works.

Thanks
-Dimitry

what does the event logs says. Any error warnings when this happens

neotiwary:  I made the changes but it did not fix it.   The service still did not start after reboot.

Radweld: I made a change to delayed start but that also did not fix the problem.

Any other ideas?

After looking at the event viewer here are some of the errors and warnings I see:
Level:  Warning
Source: Winlogon
Event ID:  6005
Task Category: None
The winlogon notification subscriber <GPClient> is taking long time to handle the notification event (CreateSession).

Level:  Error
Source: MSExchange ADAccess
Event ID:  2151
Task Category: General
Process w3wp.exe (AirSync) (PID=3152). An remote procedure call (RPC) request to the Microsoft Exchange Active Directory Topology service failed with error 1753 (Error 6d9 from HrGetServersForRole). Make sure that the Remote Procedure Call (RPC) service is running. In addition, make sure that the network ports that are used by RPC are not blocked by a firewall.

Level:  Error
Source: MSExchange ActiveSync
Event ID:  1015
Task Category: Server
Exchange ActiveSync experienced a transient error when it tried to access Active Directory information for user "". Exchange ActiveSync will try this operation again. If this event occurs infrequently, no user action is required. If this event occurs frequently, check network connectivity using PING or PingPath. You can also use the Test-ActiveSyncConnectivity cmdlet. More information:

Microsoft.Exchange.Data.Directory.ADTransientException: Exchange Active Directory Topology Service on server localhost cannot be contacted via RPC interface. Error 0x6D9. ---> Microsoft.Exchange.Rpc.RpcException: Error 6d9 from HrGetServersForRole
   at Microsoft.Exchange.Rpc.ADTopology.ADTopoRpcClient.HrGetServersForRole(String[] currentlyUsedServers, ServerRole role, Int32 serversRequested, ServerInfo[]& suitableServers, Int32[]& mapping)
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServersForRole(String[] currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[]& mapping)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetServersForRole(String[] currentlyUsedServers, ADServerRole role, Int32 serversRequested, Int32[]& mapping)
   at Microsoft.Exchange.Data.Directory.DSAccessTopologyProvider.GetConfigDCInfo(Boolean throwOnFailure)
   at Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateConfigNamingContexts()
   at Microsoft.Exchange.Data.Directory.TopologyProvider.GetConfigurationNamingContext()
   at Microsoft.Exchange.Data.Directory.ADSession.GetConnection(String preferredServer, Boolean isWriteOperation, Boolean isNotifyOperation, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.GetReadConnection(String preferredServer, ADObjectId& rootId)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCreator, CreateObjectsDelegate arrayCreator)
   at Microsoft.Exchange.Data.Directory.ADSession.Find(ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, CreateObjectDelegate objectCtor, CreateObjectsDelegate arrayCtor)
   at Microsoft.Exchange.Data.Directory.ADSession.Find[TResult](ADObjectId rootId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientSession.FindBySid(SecurityIdentifier sId)
   at Microsoft.Exchange.AirSync.ADHelper.TryGetADEntryFromSid(Byte[] sid)
   at Microsoft.Exchange.AirSync.AirSyncUser.InitializeFromLoggedOnIdentity()
   at Microsoft.Exchange.AirSyncHandler.Handler.BeginProcessRequest(HttpContext context, AsyncCallback asyncCallback, Object extraData)

Level:  Warning
Source: MSExchange ADAccess
Event ID:  2601
Task Category: General
Process MSEXCHANGEADTOPOLOGY (PID=1912). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,...> - Error code=80040934.
 The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

Let me know if you need more?

Thanks
-Dimitry

Just to confim that is exchange installed on a DC.Is that right.
If so thats expected
http://support.microsoft.com/kb/940845

Correct...the exchange is installed on the DC.   I tried following that kb in the past but it did not work.   I just tried it again and it also did not work.   The only difference I see is all the other Microsoft Exchange services are run under Local System and Microsoft Exchange Transport is running under Network Service.   Could that be preventing it from starting initially?   Permissions on Network Services?  

Thanks
-Dimitry

I changed to Local System and rebooted with no luck and then changed back to Network Service and rebooted again with no luck.

Can you try the below

http://www.nitingupta.in/blogs/index.php/2009/01/09/exchange-2007-on-domain-controller-global-catalog-services-do-not-start/

Is this the same as http://support.microsoft.com/kb/940845

Thanks
-Dimitry

Thank you!