You receive a "No description found" error message when you create an SSIS package or a SQL Server maintenance plan in SQL Server 2005 (922546)



The information in this article applies to:

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Workgroup
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium Based Systems
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard X64 Edition

SYMPTOMS

When you try to create a Microsoft SQL Server 2005 Integration Services (SSIS) package or a SQL Server maintenance plan, you receive the following error message:
No description found
This issue occurs when you install the original release version of Microsoft Office Visio 2003 after you install SQL Server 2005.

Note You may also experience this problem when you run the SQL Server Import and Export Wizard.

CAUSE

This problem occurs because the Microsoft Office Visio 2003 Setup program incorrectly sets the registry entries for Microsoft Core XML Services (MSXML). In this case, the wrong version of the Msxml.dll file is being used when you create SSIS packages or maintenance plans.

RESOLUTION

To resolve this problem, install Microsoft Office Visio 2003 Service Pack 1. For more information about how to obtain Visio 2003 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

873460 How to obtain the latest service pack for Visio 2003

WORKAROUND

To work around this problem, uninstall Visio 2003, and then reregister MSXML 3.0 or MSXML 4.0 for SQL Server 2005. To reregister MSXML, click Start, click Run, type the following command, and then click OK:

Regsvr32 "C:\WINDOWS\system32\msxml3.dll"

Note This command assumes that you want to reregister MSXML 3.0 and that the .dll file is located in the C:\WINDOWS\system32\ folder.

STATUS

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

Modification Type:MajorLast Reviewed:7/19/2006
Keywords:kbtshoot kbExpertiseAdvanced kbsql2005ssis kbprb KB922546 kbAudDeveloper kbAudITPRO