CODEWITHSUNDEEP
ssis
Marius
Marius

Reputation: 208

SSIS 2017 Unexpected Termination when running 64-bit

I have an SSIS solution with about 150 packages. Two of the packages consistently fail with an "Unexpected Termination" error when running in 64-bit. They succeed when running in 32-bit runtime.

The packages that fail writes some rows to the destination before failing.

The source and destination for all data flows is the local SQL Server databases. I use SQL Server Native 11 OLE DB drivers.

Both packages contain DT_NTEXT data types, but so do some of the other packages that succeed.

The are nothing in the ErrirDumps folder (C:\Program Files\Microsoft SQL Server\140\Shared\ErrorDumps). Also nothing in the Windows event log.

Below is an image of the dataflow task. The LKP component only caches 5 rows.

Data Flow Task

Any help or ideas would be much appreciated.

Upvotes: 0

Views: 3577

Answers (2)

gwoo
gwoo

Reputation: 31

I had the same problem with my SSIS package. After upgrading from 2010 32-bit to 2016 64-bit, the package stopped working. SQL Server Job doesn't show errors, and even verbose error logging does not provide useful information.

My packages were importing a few different spreadsheets in parallel. After changing the tasks to serial processing (import the next spreadsheets after the first one is done), the package works again.

Before updating your SSIS package, I suggest you disable tasks in your package and find out the source of the error. But hopefully this helps!

Upvotes: 2

user11355182
user11355182

Reputation: 1

I had a similar problem, or hopefully the same. The package could not be run using 64bit env and there were no logs either.

Just check your dotnet framework installation. There was a problem with file permissions at machine.config file within "Framework64" folder...

Upvotes: 0

Related Questions