You are currently offline, waiting for your internet to reconnect

FIX: You experience problems when you use SQL Server Business Intelligence Development Studio to create an SSIS package after you install SQL Server 2005 Service Pack 2

Extended support for SQL Server 2005 ends on April 12, 2016

If you are still running SQL Server 2005 after April 12, 2016, you will no longer receive security updates and technical support. We recommend upgrading to SQL Server 2014 and Azure SQL Database to achieve breakthrough performance, maintain security and compliance, and optimize your data platform infrastructure. Learn more about the options for upgrading from SQL Server 2005 to a supported version here.

Bug #: 50001018 (SQL Hotfix)
SYMPTOMS
You install Microsoft SQL Server 2005 Service Pack 2 (SP2). Then, you use SQL Server Business Intelligence Development Studio (BIDS) to create a SQL Server 2005 Integration Services (SSIS) package. When you do this, you may experience the following symptoms.

Symptom 1

When you run an SSIS package that contains a Back Up Database task in BIDS, the LocalConnectionForLogging property for the task is not set to a correct value.

Symptom 2

Consider the following scenario. You create an SSIS package in BIDS. You add a Back Up Database task to the SSIS package. You set the backup type for the task to differential log or transactional log. You set the task to back up all databases. In this scenario, when you run the package in BIDS, you receive the following error message:
Error: The Execute method on the task returned error code 0x80004003 (Object reference not set to an instance of an object.). The Execute method must succeed, and indicate the result using an "out" parameter.

Symptom 3

Consider the following scenario. You create an SSIS package in BIDS. You add a Back Up Database task to the SSIS package. You set the backup type for the task to differential log or transactional log. You set the task to back up one or more specific databases. When you reopen the SSIS package in BIDS, the database that is selected for the task disappears from a list in the Back Up Database Task dialog box.
RESOLUTION

Cumulative update information

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2
Note 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 2005 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Properties

Article ID: 938087 - Last Review: 06/27/2007 16:33:06 - Revision: 2.4

Microsoft SQL Server 2005 Developer Edition, Microsoft SQL Server 2005 Enterprise Edition, Microsoft SQL Server 2005 Standard 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, Microsoft SQL Server 2005 Workgroup Edition

  • kbsql2005ssis kbpubtypekc kbqfe kbfix kbexpertiseadvanced kbprb KB938087
Feedback
html>