we don´t see packages on MSDB chapter SSIS

  • hello all:

    we have a problem with SSIS of sql server 2005 on server with SO windows 2003 SP2, I try to explain the best posible but my english is poor, both remotely and locally we don´t see the packages on chapter MSDB of SSIS, the packages en File System chapter are well, we review on the sysdtspackages90 table and the packages exists, we review this url http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/11/13/ssis-error-failed-to-retrieve-data-for-this-request-reasons-and-resolutions.aspx, and we tested with change the file MsDtsSrvr.ini.xml, add the instance name, review the permissions on MSDTC chapter on Component Services, view that the users are in Disctibuted COM User Group, we restarted the SSIS Server and the Server, but we follow the same error, someone have any idea of which is the solution, thanks. :crazy:

    Microsoft SQL Server 2005 - 9.00.4035.00 (X64) Nov 24 2008 16:17:31 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

    the error that show is

    Failed to retrieve data for this request. (Microsof.SqlServer.SmoEnum)

    Communication link failure

    TCP Provider: The specified network name is no longer available. (Microsoft SQl Native Client)

    Angel Miranda Nieto
    DBA Specialist, BI, MCSA SQL Server

  • Are you saying that you know that there are SSIS packages in MSDB, but that you cannot see them?

    What did you do to receive that error message? Which tool were you using?

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

  • we are using de SSMS, this error happen when we want to expand the msdb chapter of graphics mode, do you have any idea?:-D

    Angel Miranda Nieto
    DBA Specialist, BI, MCSA SQL Server

Viewing 3 posts - 1 through 2 (of 2 total)

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