MsDtsSrvr.ini.xml
Jan 25, 2007Does anyone have a copy of this file from a clustered SQL2005 box with SSIS running? I would to see what you have. I cannot seem to get mine to work.
Thanks David
ADVERTISEMENT
Msdtssrvr.exe - Sql 2005 Sp2
Jun 21, 2007Installed sp2 for sql 2005
cannot start msdtssrvr.exe
event viewer returns:
The SQL Server Integration Services service failed to start due to the following error:
The system cannot find the file specified.
I tried to locate the msdtssrvr.exe in C:Program FilesMicrosoft SQL Server90DTSBinn
I cannot locate the file .
Ron
MsDtsSrvr.exe Memory Leak?
Aug 1, 2006In our current environment, we are running about 10,000 packages per day on a given 64 bit SSIS server.
The MSDtsSrvr.exe (SSIS service) process' memory working set size continues to grow until it consumes the memory on the machine.
Some of the packages do use a custom component. Could this be responsible for leaking memory in the MSDtsSrvr.exe process? Has a memory leak been confirmed in this process for the "first-party" components anyway?
MsDtsSrvr.ini.xml File Configration
May 12, 2006Hi All,
How to configure MsDtsSrvr.ini.xml file in a activeactive cluster.
Regards, Balaji Thiruvenkataraju
Problem With MsDtsSrvr.ini.xml Config
May 13, 2006All,
I have changed the location of the MsDtsSrvr.ini.xml file and the same updated the changed location in registry key SOFTWAREMicrosoftMSDTSServiceConfigFile.
After making the changes I restarted SSIS. When I tried viewing stored packages using SQL Server Management studio, I was not able to see File System folder or MSDB folder
When I checked error log, the below message was recorded.
"Microsoft SSIS Service configuration file does not exist.
Loading with default settings."
Does any body know why it happens.
Regards, Balaji Thiruvenkataraju
Updating MsDtsSrvr.ini.xml For Named Instance
Dec 20, 2007I've read how I need to update MsDtsSrvr.ini.xml to replace "." with the name of my named instance. For example, in the script below I replaced "." with "MYSERVERNAMEMYINSTANCENAME". When I connect to Integration Services do I specify the named instance in the connection string or the default instance? I'm unable to connect specifying the named instance.
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>MYSERVERNAMEMYINSTANCENAME</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>
Thanks, Dave
Need An Explanation Of Msdtssrvr.ini.xml And Named Instances
Apr 30, 2008We've read about a single installation of SSIS applies to all SQL instances on a server. We've also read how by default SQL Server stores SSIS packages in the MSDB database on the default instance and if you want to have packages stored on a named instance you must modify msdtssrvr.ini.xml. Here are our questions.
1 - If msdtssrvr is modified to reference a named instance, such as <ServerName>SQLTESTINST1<ServerName>, when I connect to Integration Services through Management Studio do I still specify the default instance name in the login window? That's the only way we have been able to connect and despite specifying the default instance name, the packages displayed are those of the named instance.
2 - If I am correct that you must always specify the default instance name when connecting to Integration Services, then in order to eliminate confusion regarding what SQL instance's SSIS packages I am viewing under the folder structure I can create SQL Server folders by modifying msdtssrvr.ini.xml. For example:
<?xml version="1.0" encoding="utf-8"?>
<DtsServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>
<TopLevelFolders>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB</Name>
<ServerName>.</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB-INST1</Name>
<ServerName>SQLTESTINST1</ServerName>
</Folder>
<Folder xsi:type="SqlServerFolder">
<Name>MSDB-INST2</Name>
<ServerName>SQLTESTINST2</ServerName>
</Folder>
<Folder xsi:type="FileSystemFolder">
<Name>File System</Name>
<StorePath>..Packages</StorePath>
</Folder>
</TopLevelFolders>
</DtsServiceConfiguration>
I then restart the SSIS service and can now see the following folder structure.
Running Packages
Stored Packages
+ File System
+ MSDB
+ MSDB-INST1
+ MSDB-INST2
If I expand MSDB-INST1 I will only see packages saved on the instance named INST1. The same is true for INST2. If I expand MSDB I will only see packages saved on the default instance.
Does this sound like I am doing things correctly?
Thanks, Dave
Modification Of MsDTSSrvr.ini.xml Does Not Work In June CTP
Jul 21, 2005Hi,
View 4 Replies View RelatedMsdtssrvr.ini.xml FileSystemFolder Type - ConfiguraStorePath And StorePath On A SAN
Aug 31, 2006Hi,
We have configured the ServiceConfigFile registry entry to point to an additional SSIS configuration file, which is stored on a SAN, our packages are also stored on this SAN (Storage Area Network).
When I restart the SSIS Service, MSDB and any FileSystemFolder are totally gone...
Does the location of the configuration and / or the FileSystemFolder Folder's need to be on the local machine? or can you use file share's?
If so, How would you reccommend deploying to the file system where SSIS is configured as a clustered service?
We have attempted using the SAN as well as creating file shares on the SAN with no success.
Thanks in advance,
Garnet