SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server SSIS Packaage Error Code 1073741819.


SQL Server SSIS Packaage Error Code 1073741819.

Author
Message
reachfocus
reachfocus
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 9
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 :


Date 06/08/2013 10:02:25
Log Windows NT (Application)

Source Application Error
Category Application Crashing Events
Event 1000
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
RTaylor2208
RTaylor2208
SSC Eights!
SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)SSC Eights! (988 reputation)

Group: General Forum Members
Points: 988 Visits: 1191
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
reachfocus
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 9
Yes, The job is running on Sql server Agent
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27925 Visits: 13268
Did you enable logging inside the SSIS package?
Doesn't the job history give more details?


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
reachfocus
reachfocus
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 9
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>2009.100.1600.1</Data>
<Data>4bb679aa</Data>
<Data>ntdll.dll</Data>
<Data>6.2.9200.16420</Data>
<Data>505aaa82</Data>
<Data>c0000374</Data>
<Data>000da94f</Data>
<Data>3218</Data>
<Data>01ce94b9707060e7</Data>
<Data>D:\Program Files (x86)\Microsoft SQL Server\100\DTS\binn\dtexec.exe</Data>
<Data>C:\Windows\SYSTEM32tdll.dll</Data>
<Data>b5bb664c-00ac-11e3-93ff-b4b52f53d6fd</Data>
<Data />
<Data />
</EventData>
</Event>
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27925 Visits: 13268
The event log usually has nothing useful to say.
We either need the job history from the jobstep itself, or the SSIS logging.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Ravi Chhabria
Ravi Chhabria
SSC-Enthusiastic
SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)

Group: General Forum Members
Points: 126 Visits: 219
Did you get any solution to this? We are facing same issue when executing package containing multiple Execute Package Tasks.
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27925 Visits: 13268
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?


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Ravi Chhabria
Ravi Chhabria
SSC-Enthusiastic
SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)SSC-Enthusiastic (126 reputation)

Group: General Forum Members
Points: 126 Visits: 219
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
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27925 Visits: 13268
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).


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search