FIX: DTS Package Created on Uplevel (2.5/2.6) MDAC May Fail on Computer with Downlevel (2.1) MDAC

View products that this article applies to.

This article was previously published under Q255900

BUG #: 57559 (SQLBUG_70)

Expand all | Collapse all

SYMPTOMS

A Data Transformation Services (DTS) package that was created on a Microsoft Windows 2000 computer may not run when scheduled on a server without Microsoft Data Access Components (MDAC) version 2.5 installed. The same problem occurs if you run the package on the server with DTSRun. The error message that occurs is:

DTSError returned.
DTSRun: Loading...
DTSRun: Executing...
DTSRun OnStart: DTSStep_DTSExecuteSQLTask_1
DTSRun OnError: DTSStep_DTSExecuteSQLTask_1, Error = -2147217887 (80040E21)
Error string: Errors occurred
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0
Error Detail Records:
Error: -2147217887 (80040E21); Provider Error: 0 (0)
Error string: Errors occurred
Error source: Microsoft OLE DB Provider for SQL Server
Help file:
Help context: 0
DTSRun OnFinish: DTSStep_DTSExecuteSQLTask_1
DTSRun: Package execution complete.

Back to the top

CAUSE

This problem has been isolated to a connection property that is new with the SQL Server OLE-DB Provider, which comes with MDAC 2.5 named General Timeout.

When a DTS package is saved, the connection properties are enumerated and saved within the package. When a DTS package is run, the connection properties that were saved are then applied. This means that, when you run the package, an attempt is made to provide a value for the General Timeout connection property. Since this property did not exist before MDAC version 2.5, it causes a pre-MDAC 2.5 SQL Server OLEDB provider to error.

Back to the top

WORKAROUND

To work around this problem, install MDAC 2.5 (or later) on the computer that is to run the DTS package that was created on Windows 2000. For current and past releases of MDAC, see the following Microsoft Web site at:

http://msdn2.microsoft.com/en-us/data/aa937730.aspx (http://msdn2.microsoft.com/en-us/data/aa937730.aspx)

Back to the top

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

274799 (http://support.microsoft.com/kb/274799/ ) INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

Back to the top