Microsoft KB Archive/928319
Article ID: 928319
Article Last Modified on 11/20/2007
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2005 Standard X64 Edition
- Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
- Microsoft SQL Server 2005 Enterprise X64 Edition
- Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
BUG#: 443335 (SQLBUDT)
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
When you run a Microsoft .NET Framework 1.0 or .NET Framework 1.1 application on a computer that has Microsoft SQL Server 2005 installed, you may experience one or more of the following symptoms:
- A Microsoft Windows Installer dialog box appears.
- The application restarts unexpectedly.
- An error message that resembles the following is logged in the Application log:
This problem occurs when the .NET Framework application tries to use Component Object Model interoperability (COM interop) to access Microsoft Core XML services (MSXML) 6.0. The application loads the Microsoft.SqlServer.MSXML6.dll interoperability assembly that is built into the .NET Framework 2.0. The assembly is registered during the installation of SQL Server 2005 Integration Services (SSIS). This assembly cannot be used by the .NET Framework 1.0 runtime or by the .NET Framework 1.1 runtime. Therefore, the application cannot load the assembly and assumes that the SSIS installation is broken. The application tries to repair the installation by starting the Windows Installer.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To work around this problem, you must remove the registry entries for the assemblies that are created during the SSIS installation. To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the HKEY_CLASSES_ROOT registry subtree.
- On the Edit menu, click Find, and then type Microsoft.SqlServer.MSXML6 in the Find what box.
- Remove all instances of Microsoft.SqlServer.MSXML6.
Note These registry entries are not actually required by SSIS. Therefore, SSIS will continue to operate correctly without them.
For example, assume that you find the Assembly registry entry under the following registry subkey:
This registry entry has the following value:
Microsoft.SqlServer.msxml6_interop, Version=184.108.40.206, Culture=neutral, PublicKeyToken=89845dcd8080cc91
- Exit Registry Editor.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
You cannot fix this problem by installing SQL Server 2005 Service Pack 2 (SP2). You must manually remove these registry entries. However, SQL Server 2005 SP2 no longer creates these registry entries during installation.
Steps to reproduce the problem
- Install SQL Server 2005.
- In Microsoft Visual Studio 2003, create a new ASP.NET Web application.
Add the following code to the Page_Load event handler.
Microsoft Visual C#
Microsoft Visual Basic .NET
- Press F5 to run the application.
Keywords: kbtshoot kbbug kbexpertiseadvanced kbsql2005ssis KB928319