October 3, 2013 at 3:58 pm
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
November 7, 2013 at 9:12 am
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:
November 7, 2013 at 9:25 am
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
November 7, 2013 at 1:52 pm
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.). :/
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply