You are currently browsing the archives for the SBS 2008 category.

Issues After Disabling IPv6 on Your NIC on SBS 2008

If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:

  • Microsoft Exchange services fail to start
  • Server hangs at “Applying Computer Settings…” (can eventually logon after 30 – 60 minutes)
  • Network icons show as offline
  • Some or all of the following events
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: Error

Description:
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: 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.

———————-

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).

Resolution

To resolve this issue all you have to do is re-check IPv6 in the properties of you NIC and reboot.

image

NOTE: IPv4 must also be enabled.

Properly Disabling IPv6

SBS 2008 is designed to fully support IPv6 and has IPv6 enabled by default. Most users should never need to disable IPv6, however if you must disable IPv6 here is how to disable it properly:

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 (http://support.microsoft.com/kb/322756/)

  1. Uncheck Internet Protocol Version 6 (TCP/IPv6) on your Network Card.
  2. In Registry Editor, locate and then click the following registry subkey: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpip6Parameters
  3. Double-click DisabledComponents to modify the DisabledComponents entry.
    Note If the DisabledComponentsentry is unavailable, you must create it. To do this, follow these steps:

    1. In the Edit menu, point to New, and then click DWORD (32-bit) Value.
    2. Type DisabledComponents, and then press ENTER.
    3. Double-click DisabledComponents.
  4. Enter “ffffffff” (eight f’s), and then click OK:

    image

  5. Reboot the SBS 2008 server.

RRAS (VPN) Note: If you plan to enable VPN on your SBS 2008 server, you MUST also Export and then Delete the following registry key: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesRemoteAccessRouterManagersIpv6

If you do not delete this key you will get an 20103 Event when trying to start RRAS with IPv6 disabled. You must reboot after removing this key.

Categories: SBS 2008Bookmark

Error Installing Exchange 2007 SP3 on SBS 2008

Error Installing Exchange 2007 SP3 on SBS 2008

Mark Berry July 14, 2010

Today I wanted to install Exchange Service Pack 3 on my SBS 2008 box. MSKB 982423 says the only thing to worry about is Forefront, which I’m not using. I ran setup.exe as an Administrator. The Readiness checks passed fine. However within a few seconds of starting the upgrade, I got this error:

Unable to remove product with code 6574fdc2-40fc-405a-9554-22d1ce15686b. Error opening installation log file. Verify that the specified log file location exists and that you can write to it. Error code is 1622.

The only option was to click Finish and start looking for answers.

Exchange Is Down, Can’t Re-Run Setup

At this point, the service pack setup has stopped and disabled all Exchange services, so your Exchange server is offline. If you re-run setup, the Readiness checks fail with a message that the metabase cannot be accessed. The linked advice is to uninstall and re-install Internet Information Services. (Yeah, right.) So yes, the web server is also offline.

Through some trial and error, and with the help of this Technet article, I found that all I needed to do was re-enable and start these two IIS services:

World Wide Web Publishing Service
IIS Admin Service

IIS 6 Compatibility components not installed
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see “Microsoft Exchange Analyzers” at http://go.microsoft.com/fwlink/?linkid=34707.]Topic Last Modified: 2011-10-25

Microsoft® Exchange Server 2007 Setup cannot continue its attempt to install the Client Access Server server role, the Mailbox server role, or the Exchange 2007 Administrative Tools on the following Windows operating systems:

  • Windows Server 2008 R2
  • Windows Server 2008
  • Windows 7 (Administrative Tools only)
  • Windows Vista (Administrative Tools only)

This problem occurs because the Internet Information Server (IIS) 6 Metabase Compatibility component and the IIS 6 Management Console component are not installed.

Exchange 2007 setup requires that the computer on which you are installing the Exchange 2007 Client Access server role, the Mailbox server role, or the Exchange 2007 Administrative Tools has the IIS 6 Metabase Compatibility component and the IIS 6 Management Console component installed.

To resolve this problem, install the IIS 6 Metabase Compatibility component on the destination computer, and then rerun Microsoft Exchange Setup.

Install the IIS 6.0 Management Compatibility Components in Windows Server 2008 R2 or in Windows Server by using the Server Manager tool

  1. Click Start, click Administrative Tools, and then click Server Manager.
  2. In the navigation pane, expand Roles, right-click Web Server (IIS), and then click Add Role Services.
  3. In the Select Role Services pane, scroll down to IIS 6 Management Compatibility.
  4. Click to select the IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, and IIS 6 Management Console check boxes.
  5. In the Select Role Services pane, click Next.
  6. In the Confirm Installations Selections pane, click Install.
  7. Click Close to exit the Add Role Services wizard.

Install the IIS 6.0 Management Compatibility Components in Windows 7 or in Windows Vista from Control Panel

  1. Click Start, click Control Panel, click Programs and Features, and then click Turn Windows features on or off.
  2. Open Internet Information Services.
  3. Open Web Management Tools.
  4. Open IIS 6.0 Management Compatibility.
  5. Click to select the IIS 6 Metabase and IIS 6 configuration compatibility, IIS 6 WMI Compatibility, and IIS 6 Management Console check boxes.
  6. Click OK.

 

 

With that, when I re-ran the SP3 setup, the Readiness checks passed—and I was back to the upgrade failure:

Exchange 2007 SP3 error

Manually Uninstall Microsoft Full Text Indexing Engine for Exchange

A little digging in C:ExchangeSetupLogsExchangeSetup.log and I saw that this error occurred when working on MSFTE.MSI. That corresponds to some Internet research that identifies the component as the Microsoft Full Text Indexing Engine for Exchange. I boldly followed the advice in this thread to manually uninstall that component:

MsiExec.exe /X {6574fdc2-40fc-405a-9554-22d1ce15686b}

Then I re-started the two IIS services and re-ran the Exchange SP3 installation.

Worked This Time

This time, the Preparing Setup step finished quickly. I got a bit nervous when the Remove Exchange Files step seemed stuck, but it finally finished after 21 minutes. The entire process took just under 37 minutes. No reboot was requested, and Exchange and the web server are back online.

Exchange 2007 SP3 complete

Google “{6574fdc2-40fc-405a-9554-22d1ce15686b}” and you’ll see that people have been getting this error since Exchange 2007 SP1. If I can uninstall the product from the command line, why can’t the service pack setup uninstall it?

Categories: SBS 2008Bookmark

How to install Exchange Server 2007 SP3 on a computer that is running Windows SBS 2008

This article discusses the steps that are required to install Microsoft Exchange Server 2007 Service Pack 3 (SP3) on a computer that is running Windows Small Business Server (Windows SBS) 2008.

To download and install Microsoft Exchange Server 2007 SP3, visit the following Microsoft website:

Note Microsoft Exchange Server 2007 Service Pack 2 (SP2) on a computer that is running Windows SBS 2008, you first had to install an installation tool. For more information about the Microsoft Exchange Server 2007 SP 2 Installation Tool for Windows SBS 2008, click the following article number to view the article in the Microsoft KNowledge Base:

974271  Description of the Microsoft Exchange Server 2007 Service Pack 2 Installation Tool for Windows Small Business Server 2008

This tool is not required to install Microsoft Exchange Server 2007 SP3 on a computer that is running Windows SBS 2008.

MORE INFORMATION

If Microsoft Forefront Security for Exchange Server is installed on the computer, you must first disable the Forefront Client Security (FCS) scan engine. To do this, follow these steps:

  1. Stop the following services:
    • FSCController
    • Microsoft Exchange Information Store
    • Microsoft Exchange Transport
  2. Open an elevated command prompt.

    To open an elevated command prompt, click Start

    the Start button

    , type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.

    User Account Control permission

    If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

  3. Change the current directory to the following directory:
    C:Program Files (x86)Microsoft Forefront SecurityExchange Server
  4. At the command prompt, type the following command, and then press ENTER:
    fscutility /disable

    After you run this command, you receive the following message:

    Removing dependencies…
    dependency on FSCController removed from Microsoft Information Store
    dependency on FSEIMC removed from Microsoft Exchange Transport Service
    Microsoft Exchange Transport Service Agent registration removed

    Status: Microsoft Forefront Server Security NOT Integrated.

After the Forefront Client Security (FCS) scan engine is disabled, you should be able to install the service pack.

After the service pack setup is complete, you must enable Forefront Client Security (FCS) scan engine if you disabled it. To do this, follow these steps:

  1. Stop the following services:
    • Microsoft Exchange Information Store
    • Microsoft Exchange Transport
  2. Open an elevated command prompt.

    To open an elevated command prompt, click Start

    the Start button

    , type cmd in the Start Search box, right-click cmd.exe in the Programs list, and then click Run as administrator.

    User Account Control permission

    If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

  3. Change the current directory to the following directory:
    C:Program Files (x86)Microsoft Forefront SecurityExchange Server
  4. At the command prompt, type the following command, and then press ENTER:
    fscutility /enable
  5. Restart the following services:
    • Microsoft Exchange Information Store
    • Microsoft Exchange Transport

Known issues that may occur after you install Exchange Server 2007 SP3

After you install Exchange Server 2007 SP3, you may be unable to access the following Web sites:

  • https://sites/owa
  • https://sites/remote

Note This issue occurs only if the Internet Address Management wizard has not already been run on the computer.

To resolve this issue, edit the bindings for the SBS Web Applicationssite to select the correct certificate. To do this, follow these steps:

  1. Open Internet Information Services (IIS) Manager.
  2. Expand server_name.

    Note The server_name placeholder represents the name of the server.

  3. Expand Web Sites.
  4. Right-click SBS Web Applications, and then click Edit Bindings.
  5. Click HTTPs port 443, and then click Edit.
  6. Under SSL certificate, select the Sites certificate.
Categories: SBS 2008Bookmark