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
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
Very Nice post, Deepak.
My 2 cents: The above registry path is for SSIS 2005, the registry key for SSIS 2008 is:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS\ServiceConfigFile
Thanks... This information was really helpful for me to get to see the packagaes.