Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSIS - Failed to retrieve data for this request.


SSIS - Failed to retrieve data for this request.

Author
Message
kDBAjan
kDBAjan
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 405
I can run SSIS Wizard to do on the fly exports/imports on my production server. I can even tell it to save the package. However, I get the following error when trying to get to the Stored Packages > MSDB on my Integration Services connection.

...

TITLE: Microsoft SQL Server Management Studio
------------------------------

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is
no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration
Services Service" in Server 2005 Books Online.

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)

------------------------------

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

------------------------------
BUTTONS:

OK
------------------------------


...

Our test servers do not have this issue, but they are not clustered. I am finding some reference to the cluster being the issue, and that I need to update the MsDtsSrvr.ini.xml file on the host. The information I have found is not clear, particularly about what I need to put in. I found a mention of making the <ServerName> be “ClusterVirtualName\Instance name” but I don't have an example of this.

This is a new issue for me, so I want to have a clear idea. Being production, I cannot afford guesses at this on my part, plus I have no clear indication of the impact on the prod server when I save this setting. I am probably going to be asked if IS was installed on both nodes. My assumption is 'yes', but I don't have anything conclusive. Learning more each day on find this stuff.

Any help would be greatly appreciated.

An Accidental DBA (but loving it).

KDS
kDBAjan
kDBAjan
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 405
I don't have a solution to this yet. I don't know if silence means I'm the first to encounter this or what. Unsure
John Mitchell-245523
John Mitchell-245523
SSCertifiable
SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)SSCertifiable (7.4K reputation)

Group: General Forum Members
Points: 7367 Visits: 15095
Yes, you do need to check SSIS is installed on both nodes. As you'll have read, it's not cluster aware.

As long as you save an old copy of the configuration file before you make any changes to it, you won't cause too much damage by experimenting.

I searched the web for "MsDtsSrvr.ini.xml cluster" and found this - is it any help?

John
kDBAjan
kDBAjan
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 405
Thanks for the response... I'll be taking a look at that shortly. As for most of us, stuck on something else at the moment. (Have to figure out how to stop replication so Dynamics AX can do some schema changes. Looks like I can't just stop but have to remove and rebuild.). :/
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search