Home Dashboard Directory Help
Search

SSIS packages abort with ‘Unexpected Termination’ message by jbone1313


Status: 

Closed
 as Fixed Help for as Fixed


18
0
Sign in
to vote
Type: Bug
ID: 774370
Opened: 12/14/2012 8:28:27 AM
Access Restriction: Public
3
Workaround(s)
view
8
User(s) can reproduce this bug

Description

There is a similar Connect ticket open here (http://connect.microsoft.com/SQLServer/feedback/details/694165/ssis-packages-abort-with-unexpected-termination-message). But, that ticket is marked closed because the original poster did not respond. Since I am having this issue, and since I do not see a way to reopen that ticket, I am creating a new one.

As the title states, SSIS packages intermittently and randomly abort with an 'Unexpected Termination' message. There is no error listed anywhere in the SSIS logs. The "All Executions" report simply shows an 'Unexpected Termination', and there is no other pertinent info it provides. I logged into the SSIS server, and I checked the Windows application logs. There, I see an application error with a time that comports to the time of the aforementioned error message. The text of that error is below. I attached a dump file (from a previous occurrence of this error) referenced in the second message below. We are on SQL Server 2012 SP1.

This error seems similar to this problem that was fixed in SP1. http://support.microsoft.com/kb/2735763?wa=wsignin1.0

Application error text:

Faulting application name: ISServerExec.exe, version: 11.0.3000.0, time stamp: 0x5081b8ff
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x219ec
Faulting application start time: 0x01cdd9a446a8ac68
Faulting application path: C:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISServerExec.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 89217ecd-4597-11e2-87fb-6431504de1ac

Further up the application log, there is an information entry with this text.

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ISServerExec.exe
P2: 11.0.3000.0
P3: 5081b8ff
P4: StackHash_7c96
P5: 6.1.7601.17725
P6: 4ec4aa8e
P7: c0000374
P8: 00000000000c40f2
P9:
P10:

Attached files:
C:\Users\srv_OasisDev\AppData\Local\Temp\WERA86F.tmp.appcompat.txt
C:\Users\srv_OasisDev\AppData\Local\Temp\WERA8DD.tmp.WERInternalMetadata.xml
C:\Users\srv_OasisDev\AppData\Local\Temp\WERA8DE.tmp.hdmp
C:\Users\srv_OasisDev\AppData\Local\Temp\WERBAD9.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ISServerExec.exe_7e3281cee6ab13e21121d34ec9292675da549cb_cab_5988bd94

Analysis symbol:
Rechecking for solution: 0
Report Id: 89217ecd-4597-11e2-87fb-6431504de1ac
Report Status: 0
Details
Sign in to post a comment.
Posted by theycallmerog on 7/29/2013 at 5:56 PM
We have implemented all fixes and are current on our Service Packs and are still experiencing this problem. We have tried every workaround we could find and are still failing for no apparent reason. Is there an ETA on the fix mentioned in the MS post on 6/21?
Posted by Microsoft on 6/21/2013 at 9:11 AM
Hello Jbone. Thanks for bringing this to our attention. This has been fixed. The change will be included in a future release or servicing release for SQL Server.

-Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by rickli1984 on 6/17/2013 at 9:27 AM
yes , i have same experience as piers7 , even though i have installed the hotfix , this error is very painfull, we don't know why that happend and when that happened because unexpected termination can not fire the email notification , coz my company ETL run every night , we can monitor it and restarted it manually on that time, business users always complained that
Posted by piers7 on 6/6/2013 at 1:25 AM
Reviewing our logs this week the hotfix associated with KB 2837964 has definitely *NOT* fixed the issue for us. I still occasionally see the issue locally on my desktop (when executing packages via PowerShell via the Catalog API) and in the log for the servers (which are running the packages via SQL agent jobs)

My impression is that it appears to be happening less frequently however.
Posted by Microsoft on 6/3/2013 at 9:06 AM
Thank you, Jbone. We will be resolving the issue as fixed, as per your comment. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by jbone1313 on 6/1/2013 at 2:25 PM
I'm no longer working on the team where we were having this issue. However, right before I left, we were testing a hotfix, which I'm assuming is the one in http://support.microsoft.com/kb/2837964. And, it did seem to resolve the issue. Therefore, I think the issue is resolved with that hotfix.
Posted by piers7 on 5/30/2013 at 8:27 PM
For us this doesn't _just_ seem to happen when we run packages from an agent job. Our deployment process is scripted, and as part of that process we explicitly validate (and subsequently execute) an entry point package in each deployed SSIS project in turn (this via the catalog API).

At that point no other packages are running, and no jobs are running, but we still sporadically get the fault above. Am currently applying the hotfix to see if this remediates.
Posted by Microsoft on 5/28/2013 at 10:03 AM
Hello jbone. Please refer to http://support.microsoft.com/kb/2837964 and let us know if this resolves your issue, as suggested by Vendoran. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Microsoft on 5/28/2013 at 10:02 AM
Hello jbone. Please refer to http://support.microsoft.com/kb/2837964 and let us know if this resolves your issue, as suggested by Vendoran. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Santosh Chandavaram on 4/23/2013 at 9:50 AM
We encountered the same error. However, I do not have a recipe to reproduce. Seems like an intermittent error. Nothing helpful from Windows Logs beyond a log of the error which does not provide any source/cause of error.

Proposed workaround (Retain Same Connection = False) not applicable because, we are already running on the same setting.

Windows Server 2008 R2 Enterprise SP1;
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Enterprise Edition (Build 7601: Service Pack 1)
Posted by Mike Dobing on 4/8/2013 at 2:57 PM
We are seeing exactly the same issue.sql server 2012 sp1, child packages running in parallel,random failures with "unexpected termination" in ssis logs. RetainSameConnection=False on all connection managers.

Don't understand why this occurs so randomly?
Posted by Dakota242 on 4/1/2013 at 11:33 AM
We are experiencing the same issue in about 1 in every 100 executions. I have checked and RetainSameConnection = FALSE on the connection managers being used. It is happeneing with multiple packages running in parallel. Would having the packages not execute in parallel completely resolve this?
Posted by mlowery35 on 2/21/2013 at 10:22 AM
We are experiencing this problem too. We just moved from a physical to virtual SQL 2012 instance. Both versions of SQL Server are the same (11.0.3000). We are now seeing these error appear sporadically, when we did not see it on the old server at all. Any ideas?
Posted by JoJe on 2/6/2013 at 5:09 AM
We are also experiencing this. Running SQL Server 2012 SP1 CU1. The error happens when we call many packages in parallel from a master package. The master package is started from SQL Agent.
Posted by LittleRascal on 1/1/2013 at 3:30 PM
We are experiencing this too. We get this about once in every 15 executions
Posted by DebarchanS - MSFT on 12/18/2012 at 2:02 PM
Thanks for reporting the issue. We have a couple of similar symptoms reported with the CSS team. Just wanted to confirm: Is this happening in a scenario where you run multiple packages in parallel?
Posted by Dustin Ryan on 12/18/2012 at 6:33 AM
I am also able to reproduce this error. It does appear to be random.
Posted by Mike Dobing on 12/16/2012 at 1:28 AM
We can also produce this error, and it occurs at seemingly random times in our ETL build.
Sign in to post a workaround.
Posted by Vendoran on 5/9/2013 at 8:15 AM
It appears that a hotfix has been released to address this - http://support.microsoft.com/kb/2837964
Posted by Santosh Chandavaram on 5/5/2013 at 4:22 PM
Did not see this issue again after we changed the MaxConcurrentExecutables value from -1 (unrestricted) to 8 (matched our MAXDOP).
Posted by DebarchanS - MSFT on 2/25/2013 at 4:13 PM
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/079205f5-f8ab-4280-a241-bab522336acb

RetainSameConnection = FALSE on the connection managers
File Name Submitted By Submitted On File Size  
AppCrash_ISServerExec.exe_92e554a69170312a7371c15b4af584983dcd8_cab_0fff873e.zip (restricted) 12/14/2012 -