Unable to open MSDB node

I'm sure there is a simple answer to this but it eludes me at the moment.
I’m using the Developer Edition of SQL Server 2005.

The MSDB node under Integration Services->Stored Packages refuses to open.
It always fails with a login timeout message and that the connection was
actively refused.

I’ve run the SQL Server Surface Area Configuration tool and allowed remote
and local access, even though it’s all installed on the local machine. This
didn’t help.

The next thing I did was to turn off all my firewalls and internet access
control software and it’s still not working.

I’m using integrated authentication and the user is part of the
administrators group,
any ideas how I can try and rectify this

Thanks
Paul

Answer this question

Unable to open MSDB node

Steve_B

The MSDB folder in the Integration Services is configured to point to the default
instance of the localhost, if you don't have a default instance, and want to
use it for the named instance, you need to change the configuration file.
Here is what you need to do:

Find the file
MsDtsSrvr.ini.xml
It should be in the folder:
%Program Files%\Microsoft SQL Server\90\DTS\Binn

By default the file says something like:

< 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="FileSystemFolder">
      <Name>File System</Name>
      <StorePath>..\Packages</StorePath>
    </Folder>
</TopLevelFolders>
</DtsServiceConfiguration>

You can change the line <ServerName>.</ServerName>
to something like <ServerName>machineName\instanceName</ServerName>, save
the file, and then restart your Service, and now the MSDB will point to
the packages stored in your named instance.

Hope that helps.
CRYOS
Thanks for that, I had the same issue & it solved it. Once question: what if I have multiple named instances on the same server...can I only configure one at a time, or can I have multiple <ServerName> lines

Thanks again.
Rusty Deschenes
Thank you, as always a simple solution. :)
Puangpetch

This is a helpful post. I was having trouble with this and edited the file but typed the wrong name for the server\instance. After I typed in the correct servername\instance and then restarted the ssis server via SQL Server Configuration Manager all was good. Just as a side note I also installed the Integration Services Development tools on the server.

Chad E. Downey

Senior Data Analyst || MSSQLS DBA

IOT || Pension Systems

cdowney@iot.in.gov
IAN1903
It's a named instance.
flosee
Are you sure you installed the SSIS components on the server
DeanRIowa
This solution is not working for me

i have following in the file

<Name>MSDB</Name>
<ServerName>.</ServerName>

when I open SQL Server M.Stuudio- Integrartion Services Server Name = PC1

If I use PC1 instead "." as server name in MsDTSSrvr.ini.xml (no quotes) it does not work.

Then I go and add change PC1 to PC1\SQL2K5LOCAL (my database engine name ) and does not work again.

This makes me quite unhappy as I am trying to figure out how is deployment working and I came to the point where I am suppose to test my deploymenet package and am stuck on trying to open MSDB folder.

I am using

Microsoft SQL Server Management Studio 9.00.2047.00
Microsoft Analysis Services Client Tools 2005.090.2047.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

thanks!
Vagolon

You can configure the file to show packages from multiple named instances.

You can add more nodes to your config file with different names and pointing to different instances. for example:

<Folder xsi:type="SqlServerFolder">
      <Name>MSDBInstance</Name>
      <ServerName>server\instance</ServerName>
    </Folder>
Dockboy

After you changed the file MsDTSSrvr.ini.xml

from:

<Name>MSDB</Name>
<ServerName>.</ServerName>

to:

<Name>MSDB</Name>

<ServerName>PC1\SQL2K5LOCAL</ServerName>,

Please make sure you go to Services, and stop "SQL Server Integration Services", and restart the service.

While connecting to Integration services from SQL Server Management studio, you should still provide server name as only PC1, as Integration Services is not instance aware.

Hope that helps.
ShyamN MS
What if I dont have this file in this location
Buboi Peng
Ranjeeta -

You saved me. Thank you from the bottom of my heart.

m
Jon Irish
The SQL server instance on your machine, is it a named instance or default instance
Unable to open MSDB node

Answer this question