Koen Verbeeck - Wednesday, July 2, 2014 3:01 AM

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: 0x5081b8ffFaulting module name: ntdll.dll, version: 6.3.9600.16502, time stamp: 0x52c359e8Exception code: 0xc0000374Fault offset: 0x00000000000f387cFaulting process id: 0x1440Faulting application start time: 0x01cf953f3e54e74aFaulting application path: D:\Program Files\Microsoft SQL Server\110\DTS\Binn\ISServerExec.exeFaulting module path: C:\Windows\SYSTEM32tdll.dllReport Id: 30b5a0e2-0157-11e4-80d1-000c292c7547Faulting 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).