SSIS - connection was forcibly closed - worked on active/passive cluster, breaks on active/active
Posted on 2008-10-21
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?