Microsoft distributes Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release.
Symptoms
On a computer that is running Windows XP, you have Microsoft SQL Server 2000 installed. When you try to install Microsoft SQL Server 2008 or Microsoft SQL Server 2008 Service Pack 1 (SP1), you receive the following error message:
Object reference not set to an instance of an object.
Additionally, the following error message is logged in the SQL Server Setup log:
<Date><Time> Slp: The following is an exception stack listing the exceptions in outermost to innermost order
<Date><Time> Slp: Inner exceptions are being indented
<Date><Time> Slp:
<Date><Time> Slp: Exception type: System.NullReferenceException
<Date><Time> Slp: Message:
<Date><Time> Slp: Object reference not set to an instance of an object.
Cause
This problem occurs because the registry entries that specify the version and the language for SQL Server 2000 Tools are missing or incorrect.
Resolution
SQL Server 2008
Important You must use this hotfix if you are running the release version of SQL Server 2008.
You can slipstream the release version of SQL Server 2008 and this cumulative update to avoid the problem that is mentioned in the "Symptoms" section.For more information about how to slipstream an installation of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
955392 How to update or slipstream an installation of SQL Server 2008
The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
971490 Cumulative update package 6 for SQL Server 2008Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released
SQL Server 2008 Service Pack 1
Important You must use this hotfix if you are running SQL Server 2008 Service Pack 1.
You can slipstream the release version of SQL Server 2008 and this cumulative update to avoid the problem that is mentioned in the "Symptoms" section.For more information about how to slipstream an installation of SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
955392 How to update or slipstream an installation of SQL Server 2008
The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
971491 Cumulative update package 3 for SQL Server 2008 Service Pack 1Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Workaround
To work around this problem, use one of the following methods.
Method 1
Reinstall the client components of SQL Server 2000, and then install SQL Server 2008 or SQL Server 2008 SP1.
Method 2
-
Click Start, click Run, type regedit, and then click OK.
-
Locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\CurrentVersion
-
On the Edit menu, point to New, and then click String Value.
-
Type CurrentVersion, and then press ENTER.
-
Double-click CurrentVersion, type 8.00.0194 in the Value data box, and then click OK.
-
On the Edit menu, point to New, and then click DWORD Value.
-
Type Language, and then press ENTER.
-
Double-click Language, type 1300 in the Value data box, and then click OK.
-
Exit Registry Editor.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
