You experience issues in the original release of System Center Configuration Manager 2007 after you upgrade some site databases to SQL Server 2008

Consider the following scenario:

• You are running the original release of Microsoft System Center Configuration Manager 2007.
• You upgrade the site databases to Microsoft SQL Server 2008.

In this scenario, you experience the following issues.

Issue 1

You cannot view the site status by clicking the Site System Status node in the Configuration Manager console. Additionally, an error message that resembles the following is logged in the Sitestat.log file:Issue 2

The Configuration Manager console exits unexpectedly (crashes) when you click and then update the following node:Additionally, an entry that resembles the following may be logged in the Smsprov.log file:

Some changes were introduced in SQL Server 2008 that are not managed by the original release of System Center Configuration Manager 2007. Therefore, you may experience the issues that are described in the "Symptoms" section.

To resolve these issues, apply this hotfix before you upgrade the site databases to SQL Server 2008. You must apply this hotfix on the following servers:

• Primary site servers that are using SQL Server 2008 to host the database
• Secondary site servers that report to primary sites that are using SQL Server 2008 to host the database
• Servers that have the Configuration Manager 2007 console installed and connected to a site that uses SQL Server 2008 to host the database
• Servers that host a remote SMS provider

Important This hotfix contains a new version of the AdminConsole.xml file. If you have modified this file to apply some customizations in your environment, you must reapply these modifications to the new version after you apply this hotfix. When you apply this hotfix, the installation process backs up the old AdminConsole.xml file in the following location:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix has been replaced by the hotfix 970170. To resolve this problem, you can install hotfix 970170. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

System Center Configuration Manager 2007, x86-based version

System Center Configuration Manager 2007, x64-based version

Recommended installation sequence

Note SQL Server 2008 is not supported during the installation of a System Center Configuration Manager 2007 site. To use SQL Server 2008, you must first use SQL Server 2005 to deploy your site, and then you can upgrade SQL Server 2005 to SQL Server 2008.

To use SQL Server 2008 for site database implementation in the original release of Configuration Manager 2007, we recommend that you follow these steps during deployment:

1. Install SQL server 2005 and the original release of Configuration Manager 2007.
2. Apply this hotfix (955229).
3. Upgrade site databases from SQL Server 2005 to SQL Server 2008.

After you upgrade SQL Server 2005 to SQL Server 2008, you can apply this hotfix to any other applicable systems or locations, as described in the "Resolution" section.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about similar issues that occur in System Center Configuration Manager 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: