Export (0) Print
Expand All

Check Parameters for the System Configuration Checker

Updated: 14 April 2006

As part of SQL Server 2005 Setup, the System Configuration Checker (SCC) scans the computer where Microsoft SQL Server 2005 will be installed. The SCC checks for conditions that prevent a successful SQL Server installation. Before Setup starts the SQL Server 2005 Installation Wizard, the SCC retrieves the status of each check item, compares the result with required conditions, and provides guidance for removal of blocking issues. All of the SCC check items are network enabled; checks can run on a local computer, as well as in remote and cluster situations.

The following table describes check parameters for the SCC, requirements, and remedies that will allow Setup to successfully install SQL Server 2005.

Check item Description Remedy for failure

Windows Management Instrumentation (WMI) service requirement

WMI service must be available. A failed check on this item will block Setup.

The SCC will report the incompatibility.

Microsoft XML Core Services (MSXML) requirement

MSXML is required for some SQL Server 2005 components. If required, it will be installed by SQL Server Setup.

This is not a blocking issue for Setup.

Operating System minimum level requirement

The SCC checks the operating system for minimum requirements.

For more information, see Hardware and Software Requirements for Installing SQL Server 2005.

Operating System version and service pack (SP) level requirement

Microsoft Windows 2000 SP4, Microsoft Windows XP SP2, or Microsoft Windows Server 2003 is required. Any unsupported operating system blocks Setup.

Users cannot apply a service pack to Datacenter operating system editions without going through the Original Equipment Manufacturer (OEM).
ms143753.note(en-US,SQL.90).gifNote:

The user is pointed to online Help to see the operating system requirement, or to Windows Update Component for installing Windows service packs on the destination computer. In cases where computers are running Datacenter editions, users must contact the OEM for service pack installation. For more information, see Hardware and Software Requirements for Installing SQL Server 2005.

SQL Server compatibility with operating system requirement

The operating system type must support the given SQL Server edition. For example, SQL Server Enterprise Edition can only be installed on Windows 2000 or later. A failed check on this item will block Setup.

The user is pointed to online help to see the matrix of operating system and SQL Server editions. For more information, see Hardware and Software Requirements for Installing SQL Server 2005

Minimum hardware requirement

Hardware must satisfy minimum CPU and memory requirements. SCC will warn the user but will not block Setup if the minimum or recommended processor speed check is not met. No warning will appear on multiprocessor machines.

SCC verifies the memory available when Setup starts. SCC will warn the user but will not block Setup if the minimum or recommended RAM check is not met. Memory requirements are for this release only, and do not reflect additional memory requirements of the operating system.

For more information, see Hardware and Software Requirements for Installing SQL Server 2005.

Feature availability1,2

The SQL Server feature selection tree will check for prerequisites before displaying SQL Server components available to install.

The SCC displays results in the SCC report, including features that will not be available and their dependencies.

Pending reboot requirement

SQL Server Setup cannot run if files required by Setup are locked by other services, processes, or applications. A failed check on this item will block Setup.

The SCC will recommend that users reboot the operating system and then run Setup again.

Performance monitor counter requirement

The SCC checks registry key values to verify proper incrementing for installation of SQL Server perfmon counters. A failed check on this item will block Setup.

Users must update the registry. To manually update the registry key, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005.

Default installation path permission requirement

The SCC will verify drive formatting and read/write permissions. Setup also requires that SQL Server be installed to an uncompressed drive. A failed check on this item will block Setup.

If the drive is unformatted, read-only, or compressed, the SCC will generate an error.

COM+ catalog requirement

The SCC will verify the current COM+ catalog configuration.

The SCC will identify issues and make recommendations. For more information, see the readme file or Setup Known Issues document on the SQL Server 2005 CD.

System administrator privilege requirement

The user running Setup must have administrator privileges on all destination computers: local, remote, and all cluster nodes where SQL Server will be installed.

The SCC will tell the user to log off and log on again either after adding administrator privileges to the account, or using another account that has administrator privileges.

Enable default administrative share directory requirement (Remote/Cluster only)

All cluster nodes must have the default administrative share admin$ enabled, so that cluster installation processes can access its system files. A failed check on this item will block Setup.

The SCC will ask to fix the problem by enabling this default share directory.

1 Microsoft Internet Information Services (IIS) 5.0 or later is required for Reporting Services installations.

2 Microsoft Internet Explorer 6.0 SP1 is required for installations of the Report Designer component of Reporting Services.

Community Additions

ADD
Show:
© 2014 Microsoft