Post reply

Cannot expand MSDB folder

  • February 3, 2012 at 3:13 am

    #252304

    Hi All,

    Having a frustrating problem with SSIS on sql 2008 r2.

    When i try and expand the MSDB folder i get the following error:

    I'm running a single DEFAULT instance

    I'm using the standard NT AUTHORITY\NETWORK SERVICE account

    I've checked the MsDtsSrvr.ini.xml file to make sure the server name is correct (pointing to default instance)

    I've restarted the Integration service/sql agent services

    The only thing that has changed was that I installed a named instance but due to company changes uninstalled it a few weeks ago (but cannot confirm if it stopped working straight after the uninstall).

    Does anyone have any ideas on what to try next?

    Cheers,

    Chris

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 3:34 am

    #1442261

    I take it you're using BIDS? Are you doing so on the same computer that SQL Server is on? What happens if you try to connect using SSMS?

    John

  • February 3, 2012 at 3:43 am

    #1442267

    Hi John,

    I'm using SSMS to connect at this time not BIDS and yes i'm trying to connect from the same server.

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 3:50 am

    #1442270

    I wonder why SSIS is mentioned in the error message, then. Are you trying to expand a folder under Maintenance Plans?

    Check you've got the correct instance name. I know you said it's a default instance, but check anyway. Is the TCP protocol enabled? Is SQL Server listening on the default port of 1433? You can use SQL Server Configuration Manager to check all of those things. Also make sure that the version of SSMS you're using is equal to or higher than the version of SQL Server that you're connecting to.

    John

  • February 3, 2012 at 3:55 am

    #1442274

    Hi John,

    Thanks for the response.

    I can connect to the integration service through SSMS just can't expand the folder. I'm using the name of the server to connect (also tried . and LOCALHOST - also tried these for the server name in the INI file).

    I can confirm that i'm using port 1433 (default for DEFAULT instance) and TCP Protocal is enabled. i can also confirm that SSMS is correct version for the instance i'm connecting to.

    Do you think that installing the named instance and removing it a few weeks back has corrupted it in some way?

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 3:59 am

    #1442279

    Sounds as if it's something to do with the MsDtsSrvr.ini.xml file. Maybe it did get confused by what you did with the named instance. Are you able to post the contents of the file, please?

    John

  • February 3, 2012 at 4:01 am

    #1442280

    Here is the ini.xml file.

    <?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>UKSTG66PCSDB01v</ServerName>

    </Folder>

    <Folder xsi:type="FileSystemFolder">

    <Name>File System</Name>

    <StorePath>..\Packages</StorePath>

    </Folder>

    </TopLevelFolders>

    </DtsServiceConfiguration>

    In the servername element i've tried . localhost servername\.

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 4:14 am

    #1442287

    A few more questions. Can you connect to the database engine through SSMS? You say you're on SQL Server 2008 R2. 32 bit or 64 bit? The instance that you installed and removed - what version was that? 32 bit or 64 bit?

    You might want to work through that topic in Books Online mentioned in the error message just in case we've overlooked anything obvious.

    John

  • February 3, 2012 at 4:19 am

    #1442291

    hi John,

    I can connect to the db engine fine through ssms.

    Were using 64 bit standard edition:

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) Apr 2 2010 15:48:46 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor)

    The instance i installed then uninstalled was the same version 64 bit

    I'll start going though bol 🙂

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 4:22 am

    #1442294

    Does your server name really have a "v" at the end, or is there a type in your config file?

    John

  • February 3, 2012 at 4:25 am

    #1442297

    it really does have a v at the end 🙁

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 4:29 am

    #1442302

    OK, so Integration Services is running under NT AUTHORITY\NETWORK SERVICE? Does that have access to SQL Server, either in its own right or through something like BUILTIN\Administrators?

    John

  • February 3, 2012 at 4:44 am

    #1442317

    i would "assume" so, were using network services for the SQL Server Browser and FT Daemon Launcher and there working ok. Unfortunately I don't have access to system permissions just database

    [font="Times New Roman"]There's no kill switch on awesome![/font]

  • February 3, 2012 at 5:14 am

    #1442333

    In that case, you ought to check with your DBA.

    John

  • February 3, 2012 at 7:24 am

    #1442425

    Our dba's have told me that the account is fine.

    Their suggestions were:

    Restart the server

    Install Sp1

    Restart of the server (its a pre production server so no biggie) didn't fix it

    SP1 it is...

    [font="Times New Roman"]There's no kill switch on awesome![/font]

Viewing 15 posts - 1 through 15 (of 19 total)

You must be logged in to reply to this topic. Login to reply