Microsoft KB Archive/904798

= SSIS packages that are currently running may unexpectedly stop responding when you restart the SSIS service in SQL Server 2005 =

Article ID: 904798

Article Last Modified on 3/11/2006

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard Edition

-



SYMPTOMS
In Microsoft SQL Server 2005, when you restart the SQL Server 2005 Integration Services (SSIS) service, the SSIS package that is currently running may unexpectedly stop responding.



CAUSE
This behavior may occur because of an incorrect node setting in the SSIS service configuration file. Every time that the SSIS service starts, the service reads the SSIS configuration file. One of the nodes in the SSIS configuration file determines how the SSIS service will handle packages that may be running if the SSIS service stops responding. If this node is set incorrectly, the service issues a stop request to the SSIS runtime as soon as the SSIS service stops responding. When this behavior occurs, each package that is running is stopped.



RESOLUTION
To resolve this behavior, you must modify the SSIS service configuration file to enable packages to continue to run even if the SSIS service stops responding. The name of the SSIS service configuration file is MsDtsSrvr.ini.xml. By default, the MsDtsSrvr.ini.xml file is located in the Program Files\Microsoft SQL Server\90\DTS\Binn folder.

To modify the SSIS service configuration file, follow these steps.  In Notepad, open the MsDtsSrvr.ini.xml file.  Locate the following node: TRUE   In the node that you located in step 2, change TRUE to FALSE, so that the node appears as follows: FALSE  Save and then close the MsDtsSrvr.ini.xml file.</ol>

Note After you have modified the SSIS service configuration file, restart the SSIS service to apply updated service configuration.

<div class="references_section">