SSIS Package Crashing

Question

SSIS Package Crashing

GonnaCatchIT

SSCrazy

Points: 2797
More actions
August 31, 2019 at 5:02 pm

#3676059

Dear All,
I am migrating SSIS from 2008 to 2016. One of the SSIS package is very large, with about 12-15 dataflow tasks generating various csv/excel files. However only few of them parallelly (based on the day).
When I run this particular package either from my .net code or directly from dtexec commands, it gets crashed. All other SSIS packages seems OK.
From the SQL dump file , I just got this Info:
GetUrlPageData2 (WinHttp) failed: 12007.
Probably caused by : ACEOLEDB.DLL ( aceoledb+36ea4 )
Access DB engine is installed on the server.
Any clues or pointers on this would be useful.
FYI, I am using windows server 2016 + SQL Server 2016 Std Edition (Integration Services)

Viewing 8 posts - 1 through 7 (of 7 total)

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

Phil Parkin SSC Guru Points: 246960 More actions · Answer 1

What does the All Executions report show?

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Jeff Moden SSC Guru Points: 1004339 More actions · Answer 2

According to the following link...

https://docs.microsoft.com/en-us/windows/win32/winhttp/error-messages

... the WinHttp error of 12007 means that "The server name cannot be resolved.". Does the server or user actually have privs to where the spreadsheets are stored?

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

GonnaCatchIT SSCrazy Points: 2797 More actions · Answer 3

I think it's just a misleading error from SQL dump, can it be ?.

More info - Package works fine when running from Visual studio. Only on the server when we run manually or from .net program - it gets crashed.

Phil Parkin SSC Guru Points: 246960 More actions · Answer 4

GonnaCatchIT wrote:

I think it's just a misleading error from SQL dump, can it be ?.
More info - Package works fine when running from Visual studio. Only on the server when we run manually or from .net program - it gets crashed.

It's almost certainly to do with permissions. The All Executions report may provide further detail.

The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin

Thom A SSC Guru Points: 99130 More actions · Answer 5

GonnaCatchIT wrote:

I think it's just a misleading error from SQL dump, can it be ?.
More info - Package works fine when running from Visual studio. Only on the server when we run manually or from .net program - it gets crashed.

Wouldn't be surprised if it's a double hop issue. If you're starting it from another application, or by running SQL in SSMS, then the credentials of the user that started the package are used. I suspect that kerboros isn't configured properly for the double hop, and so credentials are lost; and therefore any permissions with them to access things like file shares.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

GonnaCatchIT SSCrazy Points: 2797 More actions · Answer 6

I did the setup for All execution report.. I am getting 'UnExpected Termination' & there is no OnError events fired...

tim.ffitch 25252 SSCrazy Points: 2055 More actions · Answer 7

You might want to try running the package in 32bit mode. It depends if the ACE drivers installed on the server are 32bit or 64bit.