June 9, 2005 at 4:42 pm
Hi all
I'm using a DTS to Upload, Delete, Insert data to a SQL Server 2000 Database from an Microsoft Access 2000 database.
When use Enterprise Manager to Run the DTS it just do it all with no errors.
When i run the same DTS from a WindowsForm application it always fails on the same Task.
Before each try i set the data on SQL server as it was before running the DTS, so it "finds" the same data each time i run the DTS.
Anyone with same weird conflict?
Any comments will be appreciated...
I know it fails on an Execute SQL Task that runs a Stored Procedure with 2 parameters:
EXEC spThisNameProcHasChanged ?, ?
I set that two parameters as two Global Variables named @user-id, @LogonUser and set its default value to "DTS", "DTS".
I delete the "EXEC" but it fails anyway; my App just displays this:
Error: -2147220421
Description: The task reported failure on execution.
Source: Microsoft Data Transformation Services (DTS) Package
Here's the log entry :
The execution of the following DTS Package failed:
Error Source: Microsoft Data Transformation Services (DTS) Package
Error Description:The task reported failure on execution.
Error code: 8004043B
\Error Help File:sqldts80.hlp
Error Help Context ID:700
Package Name: xDB_MasiveChanges_AllSteps
Package Description: it is runned from y.exe
Package ID: {222F5465-C431-4F65-8652-6493E0AB9099}
Package Version: {06AB6636-3162-4E09-A8B5-4AD0E21581BA}
Package Execution Lineage: {976CC47E-2ACA-4FED-87D6-3C22609F5914}
Executed On: m
Executed By: m
Execution Started: 09/06/2005 05:04:24 p.m.
Execution Completed: 09/06/2005 05:04:26 p.m.
Total Execution Time: 2.125 seconds
Package Steps execution information:
Step 'DTSStep_DTSDataPumpTask_1' succeeded
Step Execution Started: 09/06/2005 05:04:26 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 0.031 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_1' succeeded
Step Execution Started: 09/06/2005 05:04:24 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 2.016 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_2' succeeded
Step Execution Started: 09/06/2005 05:04:26 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 0 seconds
Progress count in Step: 0
Step 'DTSStep_DTSDataPumpTask_2' succeeded
Step Execution Started: 09/06/2005 05:04:26 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 0.016 seconds
Progress count in Step: 0
Step 'DTSStep_DTSDataPumpTask_3' succeeded
Step Execution Started: 09/06/2005 05:04:26 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 0 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_3' was not executed
Step 'DTSStep_DTSExecuteSQLTask_4' failed
Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:The task reported failure on execution.
Step Error code: 8004043B
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:700
Step Execution Started: 09/06/2005 05:04:26 p.m.
Step Execution Completed: 09/06/2005 05:04:26 p.m.
Total Step Execution Time: 0.015 seconds
Progress count in Step: 0
Step 'DTSStep_DTSExecuteSQLTask_5' was not executed
Step 'DTSStep_DTSExecuteSQLTask_6' was not executed
Step 'DTSStep_DTSExecuteSQLTask_7' was not executed
Step 'DTSStep_DTSExecuteSQLTask_8' was not executed
Nemachtiani
June 13, 2005 at 4:28 am
Just a couple of thoughts to throw your way:
- Could this be a permissions issue, i.e. being run as different users?
- In the task that is failing, are any file paths relative to the server itself (or in UNC format), or do they reference from the machine you are running Enterprise Manager on?
The latter one caused me problems once upon a time when trying to run a package from an ASP page and it ran fine in EM.
Also try this and see if it makes any sense to you:
June 13, 2005 at 4:33 am
And just to add to that URL I gave you, here's a quote from BOL that explains why that might be the issue:
Execute on main package thread
Force the task associated with this step to execute on the main package thread rather than on a spawned thread. Choose this option if you are executing a task against a data provider that is not free-threaded and does not support parallel execution of tasks.
Important If parallel execution is attempted on a provider that does not support it, serious errors may result. Some data providers used with DTS Designer that do not support parallel execution are the Microsoft OLE DB Provider for Jet, and the providers for Microsoft Excel, dBase, Paradox, and HTML source files. Use the Execute on main package thread option if more than one operation is used with these providers.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply