SQL Server SSIS Packaage Error Code 1073741819.

Question

Post reply

SQL Server SSIS Packaage Error Code 1073741819.

reachfocus

Old Hand

Points: 379
More actions
August 6, 2013 at 6:33 am

#296475

Dear All,
We have faced the following Error Recently in SSIS Package Scheduling.
Error Code :
The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.
Detailed Error List :
Date06/08/2013 10:02:25
LogWindows NT (Application)
SourceApplication Error
CategoryApplication Crashing Events
Event1000
Computer
Message
Faulting application name: dtexec.exe, version: 2009.100.1600.1, time stamp: 0x4bb679aa
Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
Exception code: 0xc0000374
Fault offset: 0x000da94f
Faulting process id: 0x3a78
Faulting application start time: 0x01ce925df1afd4c7
Faulting application path: D:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exe
Faulting module path: C:\Windows\SYSTEM32tdll.dll
Report Id: 313df978-fe51-11e2-93ff-b4b52f53d6fd
Faulting package full name:
Faulting package-relative application ID:
any one can have a solution pl post
Regards,
Dhanya

Viewing 14 posts - 1 through 13 (of 13 total)

You must be logged in to reply to this topic. Login to reply

RTaylor2208 SSChampion Points: 13298 More actions · Answer 1

Are you running the package from within a SQL Agent Job or interactivly when you get this error?

Looking at the output I would suspect that it is from a SQL Agent Job.

In this case I would add logging to a file to the package, redeploy the package and it will give you the required information in the log file.

MCITP SQL 2005, MCSA SQL 2012

reachfocus Old Hand Points: 379 More actions · Answer 2

reachfocus

Old Hand

Points: 379

August 6, 2013 at 9:42 pm

#1639192

Yes, The job is running on Sql server Agent

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 3

Did you enable logging inside the SSIS package?

Doesn't the job history give more details?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

reachfocus Old Hand Points: 379 More actions · Answer 4

PL find the below Detailed Error List from events log . i have enabled loogging in SSIS Packages

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <EventData>

<Data>dtexec.exe</Data>

<Data>ntdll.dll</Data>

<Data>D:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exe</Data>

<Data>C:\Windows\SYSTEM32tdll.dll</Data>

</EventData>

</Event>

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 5

The event log usually has nothing useful to say.

We either need the job history from the jobstep itself, or the SSIS logging.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Ravi Chhabria Ten Centuries Points: 1020 More actions · Answer 6

Did you get any solution to this? We are facing same issue when executing package containing multiple Execute Package Tasks.

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 7

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?

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Ravi Chhabria Ten Centuries Points: 1020 More actions · Answer 8

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:

---------------------------------------------------------------------

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 9

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).

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Ravi Chhabria Ten Centuries Points: 1020 More actions · Answer 10

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".

Koen Verbeeck SSC Guru Points: 259085 More actions · Answer 11

Ravi Chhabria (7/2/2014)
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".

So you are in no way having the same issue as the OP.

Maybe you start a new thread for this one.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

zeelan6451 Grasshopper Points: 13 More actions · Answer 12

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).

HI All,

I am also having the same issue, any one got soultion?

erinr Newbie Points: 7 More actions · Answer 13

This sounds like the necessary fix: https://support.microsoft.com/en-us/help/2837964/fix-unexpected-termination-when-you-run-ssis-packages-by-using-sql-ser