September 27, 2010 at 4:02 am
Got a fun SSIS issue.
I have a fairly complex package, executed from a .net application, that is occasionally terminating in the middle of execution without logging any errors and without logging package ending.
The package is configured with "SSIS log provider for SQL Server", with the OnTaskFailure and OnError events selected for logging (for all tasks)
So typically what I see in the log destination (table called sysdtslog90) is a PackageStart event, 0 or more OnTaskFailure events and then a PackageEnd event.
What's happening occasionally (unpredictable, at random it seems) is that a package gets just the PackageStart event logged and nothing else. When I check with the SSIS manager, the package is not still running and there are no open connections in SQL (so it's not waiting on locks or anything)
It's not that a task is failing. The control flow is set up with failure work flows that will result in emails being sent if any individual task fails. Additionally there's no task failure or on error events being written anywhere (SQL or windows event log)
What can cause SSIS to terminate a package without logging any failure or error events nor any PackageEnd events, not in the SQL table, not in the event log?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 27, 2010 at 6:49 am
I did a small test, and manually cancelling the package execution in BIDS doesn't generate any logging.
I guess that nobody is logging into your server and manually killing SSIS packages, so maybe there is a process that terminates other processes? (some sort of resource manager perhaps?)
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 27, 2010 at 6:58 am
da-zero (9/27/2010)
I did a small test, and manually cancelling the package execution in BIDS doesn't generate any logging.I guess that nobody is logging into your server and manually killing SSIS packages, so maybe there is a process that terminates other processes? (some sort of resource manager perhaps?)
"nobody" or somebody 🙂
Raunak J
September 27, 2010 at 7:17 am
Think I may have gotten to the bottom of this.
The cluster that SSIS sits on has been throwing some rather nasty disk-related errors and has been failing over multiple times in the last few days. At least one of the failovers corresponded in time to a package start without associated end.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply