|
Issues After Disabling IPv6 on Windows SBS 2008
By default, IPv6 is enabled on Windows SBS 2008. If you disable the IPv6
protocol on your Windows SBS 2008 server you may see the following issues.
Case 1: The Exchange doesn't work with the Event ID 1002
as shown below:
Event Source: MSExchangeSetup
Event ID: 1002
Task Category: Microsoft Exchange Setup
Level: Error
Keywords: Classic
Description:
Exchange Server component Hub Transport Role failed.
Error:
Error: An error occurred. error code was 2147504141 message was The property
cannot be found in the cache.."
Case 2: After disabling IPv6 on SBS 2008, the SBS hangs at
"Applying Computer Settings..." for a long time.
Case 3: Exchange doesn't work with the following Event ID
2102, 2105, 2114, 2601, 7005, 7022, 7024, 7044 and 8197 as shown below:
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: 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: MSExchangeTransportLogSearch
Event ID: 7005
Task Category: General
Level: Error
Description:
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: Warning
Description:
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: Error
Description:
The Microsoft Exchange Transport service hung on starting.
Source: Service Control Manager
Event ID: 7024
Task Category: None
Level: Error
Description:
The Microsoft Exchange Information Store service terminated with
service-specific error 0 (0x0).
Source: MSExchangeFBPublish
Event ID: 8197
Task Category: General
Level: Error
Description:
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.
|
