Day: February 4, 2008

January 25, 2008

947282: Error message when you prepare an Active Directory forest for Exchange Server 2007: “Schema update failed”

You run the ForestPrep operation by using the setup.exe /prepareschema command in a Microsoft Windows Server 2003 domain. You do this to prepare a Windows Server 2003 Active Directory directory service forest for Microsoft Exchange Server 2007.

When you do this, you receive the following error message:
Schema update failed: An attribute with the same link identifier already exists

January 25, 2008

947282: Error message when you prepare an Active Directory forest for Exchange Server 2007: “Schema update failed”

You run the ForestPrep operation by using the setup.exe /prepareschema command in a Microsoft Windows Server 2003 domain. You do this to prepare a Windows Server 2003 Active Directory directory service forest for Microsoft Exchange Server 2007.

When you do this, you receive the following error message:
Schema update failed: An attribute with the same link identifier already exists

These look familar :-|

948000: You cannot start the Microsoft Exchange Transport service on an Exchange Server 2007 Hub server
You cannot start the Microsoft Exchange Transport service on a Microsoft Exchange Server 2007 Hub server. When this occurs, the following error message is logged the Application event log:
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Routing
Event ID: 5023
Description:
A transient configuration error was detected while the routing configuration was loading. Exception details: The local server isn’t a member of any routing group. : Microsoft.Exchange.Transport.Categorizer.TransientRoutingException: The local server isn’t a member of any routing group. At Microsoft.Exchange.Transport.Categorizer.RoutingGroupRelayMap.ValidateConfig(ExchangeTopology topology, RawRoutingConfigData rawConfigData, DateTime timestamp)at Microsoft.Exchange.Transport.Categorizer.RoutingTables.ValidateConfig(RawRoutingConfigData rawConfigData)at Microsoft.Exchange.Transport.Categorizer.RoutingTables.PopulateTables(RawRoutingConfigData rawConfigData)

947281: When you try to install Exchange Server 2007 Service Pack 1 on an Exchange Server 2007-based computer, Setup fails
When you try to install Microsoft Exchange Server 2007 Service Pack 1 (SP1) on a Microsoft Exchange Server 2007-based computer, Setup fails. Additionally, you receive the following error message:
Setup previously failed while performing the action “install”. You cannot resume setup by performing the action “BuildtoBuildUpgrade”

These look familar :-|

948000: You cannot start the Microsoft Exchange Transport service on an Exchange Server 2007 Hub server
You cannot start the Microsoft Exchange Transport service on a Microsoft Exchange Server 2007 Hub server. When this occurs, the following error message is logged the Application event log:
Event Type: Error
Event Source: MSExchangeTransport
Event Category: Routing
Event ID: 5023
Description:
A transient configuration error was detected while the routing configuration was loading. Exception details: The local server isn’t a member of any routing group. : Microsoft.Exchange.Transport.Categorizer.TransientRoutingException: The local server isn’t a member of any routing group. At Microsoft.Exchange.Transport.Categorizer.RoutingGroupRelayMap.ValidateConfig(ExchangeTopology topology, RawRoutingConfigData rawConfigData, DateTime timestamp)at Microsoft.Exchange.Transport.Categorizer.RoutingTables.ValidateConfig(RawRoutingConfigData rawConfigData)at Microsoft.Exchange.Transport.Categorizer.RoutingTables.PopulateTables(RawRoutingConfigData rawConfigData)

947281: When you try to install Exchange Server 2007 Service Pack 1 on an Exchange Server 2007-based computer, Setup fails
When you try to install Microsoft Exchange Server 2007 Service Pack 1 (SP1) on a Microsoft Exchange Server 2007-based computer, Setup fails. Additionally, you receive the following error message:
Setup previously failed while performing the action “install”. You cannot resume setup by performing the action “BuildtoBuildUpgrade”

I had this problem before with forefront (http://blogs.flaphead.dns2go.com/archive/2007/08/17/forefront-for-exchange.aspx) and I thought it was me.

Looks like it wasn’t! .. http://support.microsoft.com/kb/944752/

…

This problem occurs because the affected computer cannot reach the following Microsoft Web site:

http://crl.microsoft.com/pki/crl/products/CSPCA.crl
This problem occurs because of the following behavior:

• When the Microsoft .NET Framework 2.0 loads a managed assembly, the managed assembly calls the CryptoAPI function to verify the Authenticode signature on the assembly files to generate publisher evidence for the managed assembly.
• The CryptoAPI function checks a Certificate Revocation List (CRL) that is available at http://crl.microsoft.com. This action requires an Internet connection.
• If the Internet connection is blocked, the outgoing HTTP requests may be dropped. Therefore, an error message is not returned. This problem may also occur if the computer cannot resolve http://crl.microsoft.com. This long delay causes the CRL check to time out.
• The Service Control Manager (SCM) determines that the service is taking too long to start and that the service has exceeded the maximum service start time. Therefore, the SCM reports the error message, and the Exchange managed code services are not started.

I know I have covered this off, but just check it out again and found that this update had snuck in!  Maybe we will get the full details ..eventually!

This service pack also fixes the following issues.

Note These fixes were not previously released in a rollup package.