Integraton Services not connecting through Management Studio
-
We are on cluster server and found out that we are missing Integration services on the second node. We loaded the Integration Services with no problem and services is up and running. When I open Management Studio and then want to connect to Integration Services, I'm getting the error below. There are blogs saying I should go ahead and load sp2 and this might fix the problem.
Any Ideas?
Thanks!
Javier
TITLE: Connect to Server
------------------------------
Cannot connect to ccsxxxxx.
------------------------------
ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
Connect to SSIS Service on machine "ccsxxxxx" failed:
Error loading type library/DLL.
.
------------------------------
Connect to SSIS Service on machine "ccsxxxxx" failed:
Error loading type library/DLL.
.
------------------------------
BUTTONS:
OK
------------------------------
-
I have had this problem in the past. Connecting from my local machine was fine, however from the server itself was an issue (although this could happen from any client tools install)
Here's what I did
Download the Windows Installer Cleanup utility from http://support.microsoft.com/kb/290301 and install (there are 32bit and 64bit installations). Be very careful using this tool, it can cause serious damage.
Open the Cleanup utility and scroll down until you reach SQL Server 2005.
Select only
- Microsoft SQL Server 2005 Books Online
- Microsoft SQL Server 2005 Tools
Hit the "Remove" button
Then go ahead and reinstall the tools. I recall that you can reinstall directly from Service Pack 1.
Please please do this on a test system first (that you don't care about) to ensure that there are no issues. :ermm:
-
First of all Thanks!
What you are saying that the install from the CD was bad. So I should use the utility to remove the Integration Services and reinstall Integration Services from the CD?
Javier
-
No, Integration Services are fine, try connecting from another machine, you should not see an issue.
Sometimes when performing a service pack update, patch, or even BOL update something can get messed up and require a reinstall (that's what I have found).
Clearing the two items and installing from the service pack download should resolve the issue (at least it did for me).
-
I met this problem before. I just applied Sp2 to Client tools, then every thing is ok.
-
i would re apply SP2 in this case
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
-
From my computer, I try connecting to Integrated Services and go an error trying to open MSDB.
Error Below.
Thanks!
Javier
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:
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
------------------------------
-
Since we are on cluster server this what I have read about Intergrated Services from MSDN.
http://msdn.microsoft.com/en-us/library/ms345193(SQL.90).aspx
Javier
-
Does the MsDtsSrvr.ini.xml file contain the same info on both nodes, this is what management studio read when trying to open integration services?
Andrew
-
Javier, just to be sure, Are you able to connect to Integration Services from the first node?
-
I have no problems opening integrated services from 'A' mode. I can run all my packages with no problems. But the 'B' mode is the problem.
Also I did change the MStsServr.ini.xml file. I put the instance name of the server where '.' resides. Stop Integrated Services service and restart but did not work.
Javier
-
What kind of cluster do you have? active/pasive or active/active. Are you doing a failover when you before you try to connect to the Integration Services?
-
Active/Pasive. We failed over from 'A' to 'B' node. The 'B' node have problems with Integrated Services. 'A' node has no problem connecting to Integrated Services from Managment Console from the server. Is this what you are asking?
Javier
-
Yes! Are there no differences on the nodes?
-
Could you execute "select @@version" on both nodes and send the results. As for the msdb error, on which node was the sql instance running when you got it?
Viewing 15 posts - 1 through 15 (of 16 total)
You must be logged in to reply to this topic. Login to reply