You are currently offline, waiting for your internet to reconnect

Small Business Server 2011 starts slowly and many services do not start

Symptoms
On a computer that is running Windows Small Business Server 2011 or Windows Small Business Server 2008, you might experience one or more of the following issues:
  • Microsoft Exchange services do not start.
  • The server stops responding while "Applying Computer Settings", but can eventually log on in 30 to 60 minutes.
  • The network icons show as offline.
In Windows Small Business Server 2011, you might see one or more of the following events in the Application log in Event Viewer:


Click here to see the Application log events

Source: MSExchange ADAccess
Date: 1/12/2011 3:02:20 PM
Event ID: 2102
Task Category: Topology
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1736). All Domain Controller Servers in use are not responding:
SBS7.contoso.local

Source: MSExchangeRepl
Date: 1/12/2011 3:01:39 PM
Event ID: 3154
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Active Manager failed to mount database Mailbox Database on server SBS7.contoso.local. Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)


Source: MSExchangeRepl
Date: 1/12/2011 3:01:38 PM
Event ID: 3154
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Active Manager failed to mount database Public Folder Database <> on server SBS7.contoso.local. Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionNotFound: Unable to mount database. (hr=0x8004010f, ec=-2147221233)

Source: MSExchange Mailbox Replication
Date: 1/12/2011 3:01:08 PM
Event ID: 1007
Task Category: Service
Level: Warning
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
The Mailbox Replication service was unable to determine the set of active mailbox databases on a mailbox server.
Mailbox server: SBS7.contoso.local
Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)


Source: MSExchangeIS
Date: 1/12/2011 3:00:46 PM
Event ID: 5000
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Unable to initialize the Microsoft Exchange Information Store service. - Error 0x96f. Log Name: Application


Source: MSExchangeIS
Date: 1/12/2011 3:00:46 PM
Event ID: 1121
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Error 0x96f connecting to Active Directory.


Source: MSExchange ADAccess
Date: 1/12/2011 3:00:37 PM
Event ID: 2604
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1736). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object SBS7 - Error code=80040a01.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.

Source: MSExchangeThrottling
Date: 1/12/2011 3:00:33 PM
Event ID: 1002
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
The Microsoft Exchange Throttling Service encountered an Active Directory error while building an RPC security descriptor. This failure may indicate that no Domain Controllers are available at this time. The service will be stopped. Failure details: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.


Log Name: Application
Source: MSExchangeRPC
Date: 1/12/2011 3:00:29 PM
Event ID: 1008
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
Encountered unexpected error when starting MSExchangeRPC service. Error details: The wait operation timed out (258)


Source: MSExchangeProtectedServiceHost
Date: 1/12/2011 3:00:27 PM
Event ID: 2011
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
An unexpected failure has occurred. No modules were loaded and the service will perform no work. Diagnostic information:
Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.


Source: MSExchangeRepl
Date: 1/12/2011 3:00:18 PM
Event ID: 2155
Task Category: Service
Level: Error
Keywords: Classic
User: N/A
Computer: SBS7.contoso.local
Description:
The Third Party Replication Manager could not access Active Directory. Error: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.. Initialization will be retried automatically.






In Windows Small Business Server 2008, you might see one or more of the following events in the Application log and the System log in Event Viewer:

Application Log Events

Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). 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.


Source: MSExchange ADAccess
Event ID: 2601
Task Category: General
Level: Warning
Description:
Process MSEXCHANGEADTOPOLOGY (PID=952). 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=80040a01. The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.


Source: MSExchange ADAccess
Event ID: 2102
Task Category: Topology
Level: Error
Description:
Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local


Source: MSExchange ADAccess
Event ID: 2105
Task Category: Topology
Level: Warning
Description:
Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).


Source: MSExchange ADAccess
Event ID: 2114
Task Category: Topology
Level: ErrorDescription:
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). 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.


Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: ErrorDescription:
Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.



Source: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: ErrorDescription:
Microsoft Exchange couldn't read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server localhost did not return a suitable domain controller.

System Log Events

Source: Service Control Manager
Event ID: 7044
Task Category: None
Level: WarningDescription:
The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant



Source: Service Control Manager
Event ID: 7022
Task Category: None
Level: ErrorDescription:
The Microsoft Exchange Transport service hung on starting.

Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: ErrorDescription:
The Microsoft Exchange Information Store service terminated with service-specific error 0 (0x0).





Cause
This issue might occur if the Internet Protocol Version 6 (TCP/IPv6) has been disabled in the Local Area Connection Properties dialog box.


Resolution
To enable Internet Protocol Version 6 (TCP/IPv6) in the Local Area Connection Properties dialog box, follow these steps:
  1. Click Start, and then click Control Panel.
  2. If Network and Internet is visible, click it. Otherwise, go to the next step.
  3. Click Network and Sharing Center and then on the left, click Manage network connections.
  4. Right-click the local area connection, and then click Properties.
  5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  6. In the Local Area Connection Properties dialog box, select the Internet Protocol Version 6 (TCP/IPv6) check box, and then click OK.
Note: Internet Protocol Version 4 (TCP/IPv4) must also be enabled.
More information
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 How to back up and restore the registry in Windows


Windows Small Business Server 2011 and Windows Small Business Server 2008 are designed to fully support IPv6. By default, IPv6 is enabled. Typically, you should never need to disable IPv6. However, if you must disable IPv6, here is how to disable it properly:
  1. In the Local Area Connection Properties dialog box, clear the Internet Protocol Version 6 (TCP/IPv6) check box.
  2. Click Start, type regedit, and then under Programs, click regedit.
  3. In Registry Editor, locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
  4. Double-click DisabledComponents to modify the DisabledComponents entry.
    Note If the DisabledComponents entry is unavailable, you must create it. To do this, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents, and then press ENTER.
    3. Double-click DisabledComponents.

  5. Type ffffffff (eight f’s), and then click OK.
  6. Restart the server running Windows Small Business Server. 
Note If you plan to enable VPN on the server running Small Business Server, you must also Export and then Delete the following registry key: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\RouterManagers\Ipv6
 If you do not delete this key, you will get an 20103 Event when you try to start RRAS with IPv6 disabled. You must reboot after removing this key.
Properties

Article ID: 2677009 - Last Review: 07/12/2013 10:21:00 - Revision: 4.1

Windows Small Business Server 2011 Standard, Windows Small Business Server 2008 Standard

  • kbsurveynew KB2677009
Feedback