question

FlashGordon-7254 avatar image
0 Votes"
FlashGordon-7254 asked FlashGordon-7254 edited

reporting a bug, switching File System Task Copy to Delete

HI,
I noticed this problem with VS 2017 and was able to replicate it in VS 2019 Community. These are the steps to recreate this bug.

1) create a File System Task with a Copy operation
2) define the input and output connection managers
3) run the job in the foreground or with a dtexec
4) Change the File System Task to a "Delete" operation
5) Delete the output File Connection Manager
6) if you care about it, make a backup of your input file
7) run the job again and you will get error message below, but the job will perform the delete operation

VS 2017 returned a non zero return code for this sequence which job monitoring systems will alarm for, VS 2019 returns a zero return code, which is an improvement. But it's still saying error and failure in the log file for VS 2019 Community. It's looking for the output connection manager from the copy even though the operation has been changed to delete, which requires only one Connection Manager. I was able to fix this by manually removing the "4C5232... " line in the xml from Package.dtsx. So I think this is a bug, it shouldn't go looking for a defunct output Connection Manager on a delete operation. With VS 2017 it also runs all the job tasks even though it gives a failure return code in the log file.

SSIS package "C:\Users\xxxxxx\source\repos\ssis\testBug\testBug\Package.dtsx" starting.
Error: 0xC001000E at Package: The connection "{4C5232D2-B750-432D-BB56-4012BD524033}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Error: 0xC001000E at Package: The connection "{4C5232D2-B750-432D-BB56-4012BD524033}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
Warning: 0x80019002 at Package: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (4) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "C:\Users\xxxxxxx\source\repos\ssis\testBug\testBug\Package.dtsx" finished: Failure.
The program '[8868] DtsDebugHost.exe: DTS' has exited with code 0 (0x0).

sql-server-integration-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Monalv-msft avatar image
0 Votes"
Monalv-msft answered

Hi @FlashGordon-7254 ,

We can drag a new File System Task for a "Delete" operation.
Then we can run the ssis package successfully.

86113-fst1.jpg

86104-fst2.jpg

Best regards,
Mona


If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.




fst1.jpg (279.9 KiB)
fst2.jpg (262.6 KiB)
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FlashGordon-7254 avatar image
0 Votes"
FlashGordon-7254 answered FlashGordon-7254 edited

Mona, I found that references to the defunct TaskDestinationPath existed in only one place in the Package so I felt comfortable in deleting it, obviously being careful to make sure the xml was still formed correctly.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.