July 3, 2014 at 12:50 pm
I have an SSIS process that is misbehaving. Here is the edited error code:
Selected row details:
Date7/3/2014 1:39:49 PM
LogJob History (XXXXXXX_Daily_Files_Import)
Step ID2
ServerXXXXXXXXX\XXXX
Job NameXXXXXXXX_Daily_Files_Import
Step NameImport Files Via SSIS - File System
Duration00:00:03
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
Executed as user: XXXXXXX\sqlserver. Process is terminated due to StackOverflowException. The return value was unknown. The process exit code was -1073741571. The step failed.
Does anyone have any information on this exit code?
[font="Arial"]“Any fool can know. The point is to understand.”
- Albert Einstein
"DOH!"
- Homer Simpson[/font]
July 5, 2014 at 1:56 am
First thought would be looking at any looping (i.e. ForEach) iteration's configuration. Next would be a file system problem where a parent folder is mounted in a child folder, could cause uncontrolled recursion. Third would be looking for a folder with tens of thousands of files.
😎
July 8, 2014 at 12:38 pm
Some of the runtime symptoms of the below suggested causes could be: 1.) sudden CPU usage spikes for however long this runs before it fails, or even 2.) a long steady increase in RAM usage before failure.
Eirikur Eiriksson (7/5/2014)
First thought would be looking at any looping (i.e. ForEach) iteration's configuration. Next would be a file system problem where a parent folder is mounted in a child folder, could cause uncontrolled recursion. Third would be looking for a folder with tens of thousands of files.😎
Steve (aka sgmunson) 🙂 🙂 🙂
Rent Servers for Income (picks and shovels strategy)
July 8, 2014 at 12:45 pm
sgmunson (7/8/2014)
Some of the runtime symptoms of the below suggested causes could be: 1.) sudden CPU usage spikes for however long this runs before it fails, or even 2.) a long steady increase in RAM usage before failure.Eirikur Eiriksson (7/5/2014)
First thought would be looking at any looping (i.e. ForEach) iteration's configuration. Next would be a file system problem where a parent folder is mounted in a child folder, could cause uncontrolled recursion. Third would be looking for a folder with tens of thousands of files.😎
Absolutely right, a tell tail sign. I've seen this even on beefy a application server when iterating through less than 100K files.
😎
July 8, 2014 at 12:47 pm
I should have already posted my "solution". The issue was another job was running that used many of the same packages stored in the SSIS Catalog. They hit the same resources, and the server didn't know how to handle that. The issue resolved itself once the other job finished, and the ultimate fix for others researching this error was to change the schedule to keep the jobs from running at the same time.
[font="Arial"]“Any fool can know. The point is to understand.”
- Albert Einstein
"DOH!"
- Homer Simpson[/font]
July 8, 2014 at 12:53 pm
jarid.lawson (7/8/2014)
I should have already posted my "solution". The issue was another job was running that used many of the same packages stored in the SSIS Catalog. They hit the same resources, and the server didn't know how to handle that. The issue resolved itself once the other job finished, and the ultimate fix for others researching this error was to change the schedule to keep the jobs from running at the same time.
🙂
Thank you for the update!
I would argue that designing for concurrency would be a better approach because otherwise one runs out of available time sooner or later.
😎
July 8, 2014 at 1:04 pm
I would argue that designing for concurrency would be a better approach because otherwise one runs out of available time sooner or later.
I agree. I am new to the company, and they want me to complete a phased major redesign. This is going to end up being a from-the-ground-up redesign, and I am going to make each SSIS package run for only 1 job. They are currently being called with Package / Project level parameters to decide which facility to process for a given client. Each facility is run slightly differently, but they use a trunk to branch approach. During the initial design I can see why this was a good idea, but as time goes on and changes have to be made it makes the upkeep a great deal more difficult. It is better to spend the extra time up front to save time later...just my opinion.
[font="Arial"]“Any fool can know. The point is to understand.”
- Albert Einstein
"DOH!"
- Homer Simpson[/font]
July 8, 2014 at 1:12 pm
Simple things like snapshot isolation could do wonders in this kind of situation:-D
😎
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply