Link to home
Start Free TrialLog in
Avatar of Daniel Wilson
Daniel WilsonFlag for United States of America

asked on

SSIS - connection was forcibly closed - worked on active/passive cluster, breaks on active/active

We've got a big SSIS package that imports text files into SQL Server 2005.

The thing ran fine through this massive batch of files on our Dev environment ... then on our next environment up.  

On the Test environment, the same package, working against an identical (made from the same script) DB, loading the same files, breaks with errors about the connection being forcibly closed.  The breaks appear to occur randomly.

The only known difference between the working and non-working environments is the cluster configuration.  The working environments use an Active / Passive cluster configuration.  The failing environment uses an Active / Active / Passive configuration.

Our BI guru suspects that connection pooling in the SSIS doesn't get along w/ this cluster configuration.

Is he right?  Or is there something else we should check?

Thanks!
SOLUTION
Avatar of randy_knight
randy_knight

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Daniel Wilson

ASKER

Randy, my comment was wrong.  we're still having the problem.

New question on it is at https://www.experts-exchange.com/questions/23838695/SSIS-Clusters-and-troubleshooting-DNS.html