DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 960161 - Last Review: December 20, 2008 - Revision: 3.1

Bug #: 50003774 (SQL Hotfix)

Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.

On This Page

SYMPTOMS

Consider the following scenario:
  • You have a Microsoft SQL Server 2005 Integration Services package.
  • In SQL Server 2005 Management Studio, you configure a job that contains a step that runs the Integration Services package.
  • You update the data source on the Data Sources tab, and then you click OK to save the changes.
  • You edit the job step again to make some other changes. You do not click the Data Sources tab.
  • You click OK to save the changes.
In this scenario, the changes to the data source are lost.

When this problem occurs, related problems also occur. These problems include the following problems:
  • The Integration Services package tries to connect to the wrong server.
  • If the default connection strings inside the Integration Services package are not valid, the connection fails.
  • You receive one of the following error messages:

    Error message 1
    SSIS Error Code DTS_E_SQLTASK_FAILEDTOACQUIRECONNECTION:
    Failed to acquire connection "<Servername.DatabaseName>". Connection may not be configured correctly or you may not have the right permissions on this connection.
    Error message 2
    SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER:
    The AcquireConnection method call to the connection manager "<Servername.DatabaseName>" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed."
    Note The <Servername.DatabaseName> placeholder represents the server name and the database name of the connection manager that has experienced the failure inside the Integration Services package.

RESOLUTION

Cumulative update information

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.

The fix for this issue was first released in Cumulative Update 11 for SQL Server 2005 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
958735  (http://support.microsoft.com/kb/956854/LN/ ) Cumulative update package 11 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  (http://support.microsoft.com/kb/937137/LN/ ) 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.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.

The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
959195  (http://support.microsoft.com/kb/959195/LN/ ) Cumulative update package 1 for SQL Server 2005 Service Pack 3
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:
960598  (http://support.microsoft.com/kb/960598/LN/ ) The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. 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:
  • When you edit a job step that runs an Integration Services package, make sure that you click the Data Sources tab so that the changes to the connection managers are initialized and saved.
  • Do not use the Data Sources tab to set the connection strings. Instead, create a package configuration file and provide edited values of the connection strings for the connection manager. You can update the connection strings by modifying the XML configuration file.
For more information about how to create and set a package configuration file, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/ms140213(SQL.90).aspx (http://msdn.microsoft.com/en-us/library/ms140213(SQL.90).aspx)
Or, visit the "Creating Package Configurations" section of the following Microsoft Web site:
http://technet.microsoft.com/en-us/library/cc966389.aspx (http://technet.microsoft.com/en-us/library/cc966389.aspx)

STATUS

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

MORE INFORMATION

You can use the job step metadata that is saved in the MSDB database to check the missing /CONNECTION switches in the Integration Services job step command definitions. You can use the following statements to confirm these connections:
-- See all SSIS job steps where the Data Source is present
select J.name, JS.*
from msdb.dbo.sysjobsteps JS
join msdb.dbo.sysjobs J
on J.job_id=JS.job_id
where subsystem='SSIS'
and command like '%/CONNECTION%'

-- See all SSIS job steps where the Data Source is not present
select J.name, JS.*
from msdb.dbo.sysjobsteps JS
join msdb.dbo.sysjobs J
on J.job_id=JS.job_id
where subsystem='SSIS'
and command not like '%/CONNECTION%'

-- See all SSIS job steps where the Data Source is missing and was updated within the past 7 days
select datediff(dd,J.date_modified,getdate()) as LastEditDaysAgo, J.name, J.date_modified, J.version_number, JS.*
from msdb.dbo.sysjobsteps JS
join msdb.dbo.sysjobs J
on J.job_id=JS.job_id
where subsystem='SSIS'
and command not like '%/CONNECTION%'
and datediff(dd,date_modified,getdate())<7

REFERENCES

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
958735  (http://support.microsoft.com/kb/958735/LN/ ) Cumulative update package 11 for SQL Server 2005 Service Pack 2
For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137  (http://support.microsoft.com/kb/937137/LN/ ) List of the builds that are available after SQL Server 2005 Service Pack 2 was released
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  (http://support.microsoft.com/kb/935897/LN/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089  (http://support.microsoft.com/kb/913089/LN/ ) How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711 (http://go.microsoft.com/fwlink/?LinkId=71711)
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:
822499  (http://support.microsoft.com/kb/822499/LN/ ) New 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  (http://support.microsoft.com/kb/824684/LN/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
Keywords: 
kbsurveynew kbhotfixrollup kbfix kbqfe kbexpertiseadvanced KB960161
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support