Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

SQL Server SSIS Packaage Error Code 1073741819. Expand / Collapse
Author
Message
Posted Tuesday, August 6, 2013 6:33 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 6:34 AM
Points: 3, 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
Post #1481287
Posted Tuesday, August 6, 2013 8:24 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, August 11, 2014 6:37 AM
Points: 299, Visits: 561
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
Post #1481361
Posted Tuesday, August 6, 2013 9:42 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 6:34 AM
Points: 3, Visits: 9
Yes, The job is running on Sql server Agent
Post #1481638
Posted Wednesday, August 7, 2013 3:23 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 AM
Points: 13,601, Visits: 10,476
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?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1481755
Posted Thursday, August 8, 2013 10:47 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 26, 2013 6:34 AM
Points: 3, 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>
Post #1482638
Posted Thursday, August 8, 2013 11:57 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 AM
Points: 13,601, Visits: 10,476
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?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1482644
Posted Wednesday, July 2, 2014 1:49 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 14, 2014 3:30 AM
Points: 57, Visits: 193
Did you get any solution to this? We are facing same issue when executing package containing multiple Execute Package Tasks.
Post #1588335
Posted Wednesday, July 2, 2014 1:53 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 AM
Points: 13,601, Visits: 10,476
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?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1588336
Posted Wednesday, July 2, 2014 2:56 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 14, 2014 3:30 AM
Points: 57, Visits: 193
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:
---------------------------------------------------------------------
Post #1588353
Posted Wednesday, July 2, 2014 3:01 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:01 AM
Points: 13,601, Visits: 10,476
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?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1588357
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse