Koen Verbeeck (7/2/2014)
Ravi Chhabria (7/2/2014)
Koen Verbeeck (7/2/2014)
Ravi Chhabria (7/2/2014)
Did you get any solution to this? We are facing same issue when executing package containing multiple Execute Package Tasks.What does your package logging say?
Below is the log from Application Logs
---------------------------------------------------------------------
Faulting application name: ISServerExec.exe, version: 11.0.3000.0, time stamp: 0x5081b8ff
Faulting module name: ntdll.dll, version: 6.3.9600.16502, time stamp: 0x52c359e8
Exception code: 0xc0000374
Fault offset: 0x00000000000f387c
Faulting process id: 0x1440
Faulting application start time: 0x01cf953f3e54e74a
Faulting application path: D:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISServerExec.exe
Faulting module path: C:\Windows\SYSTEM32tdll.dll
Report Id: 30b5a0e2-0157-11e4-80d1-000c292c7547
Faulting package full name:
Faulting package-relative application ID:
---------------------------------------------------------------------
Again, such logging is useless.
You need to either enable logging in the SSIS package or look at the logging of the SQL Server Agent job (if applicable).
Logging is enabled in the package but it appears log are incomplete due to the error. This is with SQL Server 2012 and status of package is "Unexpected Termination".