Microsoft KB Archive/247891
Article ID: 247891
Article Last Modified on 3/14/2006
- Microsoft SQL Server 7.0 Standard Edition
This article was previously published under Q247891
BUG #: 56355 (SQLBUG_70)
When a DTS package step fails, the Error file and Windows NT Event log does not provide any information on why the step failed, even though the DTS Wizard and Designer UI displays the full error in a message box.
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
Steps to Reproduce the Problem
Create a table with a primary key in SQL database and import from a text file with a duplicate key. Run the following script in SQL Query Analyzer:
CREATE TABLE DTS_Text ( Id INT NOT NULL PRIMARY KEY, Name CHAR(10) NOT NULL ) go
Create a text file with the following data:
1, "One" 2, "Two" 3, "Three" 1, "Fail"
- Create a Package with the DTS Import Wizard, point to the text file data source and SQLOLEDB as the destination. Select the table you created earlier. Save the package in SQL Server. When you execute the package, you will see an error message similar to the following:
Open the package in DTS Designer in SQL Enterprise Manager. Edit package properties and specify an Error file and also enable the option write completion status to event log.
Execute the package and you receive the detailed error in DTS Designer. However, the Error file will contain the following line without any detail:
Step 'Copy Data from TextData to [pubs].[dbo].[DTS_Text] Step' failed.
The Windows NT Application Event log will also have the same message without any details.
Keywords: kbbug kbfix kbfaq KB247891