MSDB and File System doesn't appear under Stored Packages, After connecting to SQL Server Integration Services 2005 from SQL Server Management Studio

Published Jan 15 2019 12:28 PM 121 Views
First published on MSDN on Nov 12, 2009

Cause and Resolution


SSIS uses the value of Registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile" to locate the location of SSIS configuration file on the machine.  If this key doesn’t exist or doesn’t point to the correct path of the file MsDtsSrvr.ini.xml, this issue may occur.  The default path of this file is "%ProgramFiles%\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml".



When the SSIS service is started, it reads the configuration file MsDtsSrvr.ini.xml to load the required settings.  If the path of this file is incorrectly specified in the registry location, below event gets logged in the event logs.


Event Type: Error


Event Source: SQLISService


Event Category: Service Control


Event ID: 272


Date:


Time:


User: N/A


Computer:


Description: Microsoft SSIS Service configuration file does not exist. Loading with default settings.




In this case, SSIS service will still be restarted successfully and SQL Server Integration Service can still be connected successfully from SQL Server Management Studio but the “MSDB” and “File System” nodes won’t appear under “Stored Packages”.


To resolve this problem, specify the correct complete path for file MsDtsSrvr.ini.xml in the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTS\ServiceConfigFile".


We need to restart the SSIS Windows Service for the changes to take effect.



Author : Deepak (MSFT) , SQL Developer Engineer , Microsoft


Reviewed by : Debarchan (MSFT) , SQL Developer Engineer , Microsoft

Version history
Last update:
‎Jan 15 2019 12:28 PM
Updated by: