Hung SSIS package, catalog.create_execution_dump, how to find Symbols

Question

We have an SSIS package that hangs during execution in the PrimeOutput phase.

The isserverexec process shows open connections to a MySQL DB, the SSISDB and its destination SQL Server.
None of the systems it has connections to show that the connection is doing work or that it is blocked.
Server never ran into memory pressure or anything while loading or executing the package.

Using process explorer (sysinternals) we can see that the isserverexec process is intermittently doing some work on the CPU but the stack traces are not helpful in identifying what it is actually doing (waiting for a response from source / dest / etc)

To identify what the SSIS package is waiting on / blocked doing I used the catalog.create_execution_dump command. I am familiar with analyzing dump files to see where in the stack a SQL Server Database Engine process may have failed but this is my first time trying with an SSIS package.

Unfortunately it appears the SSIS packages do not have any symbols that we can use to find out where in the execution it is failing. Does anyone know how we can generate symbols for our SSIS packages so we can identify where we are getting hung?

Is it possible to connect remotely with the debugger to the running isserverexec process?

Is there a simpler method that I am overlooking to get more details as to where we are hung?

Answer 1

Hi @MJ SQL ,

Integration Services includes features and tools that you can use to troubleshoot packages when you execute them after they have been completed and deployed.

Details you may refer: troubleshooting-tools-for-package-execution

https://www.sqlshack.com/overview-of-ssis-package-logging/

Regards，

Zoe

---

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October