DTS Error Message "Execution was canceled by user"
-
HELP!!!To make it short, I have quite a few DTS pacckages to update several databases. Everything works fine.
I created some others that create text files based on the recently update package to be sent via FTP to another location. So far fine.
Then, I add a step in the update package to run the create text files, but it does not run properly. I got an error message stating the following:
"Error Source: Microsfot Data Transformation Services (DTS) package
Error Description: Execution was canceled by user"
Which, of course, I did not
I need to add that step to the main update package to avoid the creation of the text files if the main database is not updated.
PLEASE HELP!!!!
-
Could you post a snippet of your textfile creation step?
Joseph -
This same thing happened with my packages that had been running fine with no problems for well over a year. The only work around I found was don't open up the package using 'Design Package' to try and execute it... just right click the package name in Enterprise Manager and 'Execute Package' without opening it in the designer.
-
have you tried making all tasks/steps execute on main thread (i think it's in the workflow optiosn dialog).
Steve.
-
I have this problem also, and the solution that they give there not to I deal.
Help me please!!!
Auxiliooooooo
-
I'm running into a similar problem and have found nothing useful so far on Google...
In my case, I have a subpackage that has four different paths coming from a Dynamic Properties Task, each with two SQL Tasks to drop and create a table, then a Transform Data Task to move data. If I run this package manually, it works just fine.
However, if I call it from another package, I get the error above. Why?
I'm loathe to take stevefromOZ's suggestion above, since there are a lot of steps in the main DTS, but I tried at least making the transform tasks in the called DTS and the actual DTS Task in the calling DTS have that option on, and there is no change. Would I really need to make every task use the main thread? Or just the ones in the called DTS, or just the ones in the calling DTS?
Can anyone help?
-
This is a known DTS problem that I stumbled across 2+ years ago and I've never seen a fix for it. It occurs if you use an Execute Sub-package task, and the sub-package contains at least 1 datapump.
Workaround in our case was to abandon the Execute Sub-package task and make it an Execute SQL task instead. The Execute SQL task calls a stored procedure that is mostly based on this example code for using the sp_OACreate etc stored procs:
http://www.databasejournal.com/features/mssql/article.php/1459181
-
Another approach to calling a sub-package is to use an ExecuteProcess task and call DTSRUN.EXE
--------------------
Colt 45 - the original point and click interface
-
Another approach that I found courtesy of groups.google.com is to use an ActiveX Script Task. I didn't test this one, but figured I should note it here for posterity.
I thought I'd also note some weirdness... I found another post that suggested that setting the checkbox for "Execute on main thread" only for the affected task and the ones before and after it would work, and it did. But I was curious as to which actually fixed it, and reset the checkbox to unchecked for the task after, then the task before, and then the task itself, and it still worked (?). Then I got the DTSs back out of our source repository and tried again, and it still worked (?!?). I didn't try restarting EnterpriseManager or rebooting, but I suspect I could reintroduce the bug by doing possibly the former or certainly the latter. It's just interesting that the bug stayed away once fixed...
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply