Solved

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

Posted on 2008-10-21
3
429 Views
Last Modified: 2013-11-10
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!
0
Comment
Question by:Daniel Wilson
  • 2
3 Comments
 
LVL 4

Assisted Solution

by:randy_knight
randy_knight earned 300 total points
ID: 22770119
In the failing environment which is active/active/passive, you still only have the instance being loaded to on one node at a time.  So I don't see that the nature of hte cluster would be the issue.  You're still connecting to the virtual name/IP of the instance.  You might check DNS, etc. for the virtual name to make sure you're not getting intermittent issues with that.
0
 
LVL 32

Accepted Solution

by:
Daniel Wilson earned 0 total points
ID: 22778013
Thanks, Randy.

Turns out the DBA didn't properly deploy the package to the DB ... though how that caused an intermittent failure, I don't know.

Anyway, thanks for your help.
0
 
LVL 32

Author Comment

by:Daniel Wilson
ID: 22781126
Randy, my comment was wrong.  we're still having the problem.

New question on it is at http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/Q_23838695.html
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

JSON is being used more and more, besides XML, and you surely wanted to parse the data out into SQL instead of doing it in some Javascript. The below function in SQL Server can do the job for you, returning a quick table with the parsed data.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
This video shows, step by step, how to configure Oracle Heterogeneous Services via the Generic Gateway Agent in order to make a connection from an Oracle session and access a remote SQL Server database table.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question