"Failed to retrieve data for this request" "Error loading type library dll"

Component Registration
To resolve error loading typelibrary error when connecting to SSIS from Management
Studio we did following on both nodes of the cluster

1. Run following commands to make sure 32bit and 64bit versions of
MsDtsSrvrUtil.dll are registered properly.

regsvr32 /u C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvrUtil.dll
regsvr32 /u C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvrUtil.dll
regsvr32 C:\Program Files (x86)\Microsoft SQL
Server\90\DTS\BINN\MsDtsSrvrUtil.dll
regsvr32 C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvrUtil.dll

2. Run following commands to make sure 32bit and 64bit versions of DTS.dll are
registered properly.

regsvr32 /u C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll
regsvr32 /u C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTS.dl
regsvr32 C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTS.dll
regsvr32 C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTS.dll

Enabling Users to Connect SSIS from Remote Computers
By default you cannot connect to SSIS service from a remote computer running
Management Studio. To be able to connect SSIS from remote computer, we did
following:

1. Open Component Services\Computers\My Computer\Properties\Default Properties,
make sure the option “Enable Distributed COM on this
computer” is checked.

2. Open Component Services\Computers\My Computer\DCOM Config\MsDtsServer
Properties. In the security page verify that under “Launch and Activate
Permissions”, Remote Launch and Remote Activation are enabled for all users who
will be connecting SSIS service remotely.

3. Open Computer Management\Local Users and Groups\Groups and make sure all users
who will be connecting SSIS service remotely are added into “Distributed COM users”
group.

4. If there’s a firewall between the client computer where you run Management
Studio and SSIS server you also need to make sure the firewall is configured for
DCOM. Refer to below article for more information on this.

Using Distributed COM with Firewalls
http://msdn.microsoft.com/library/en-us/dndcom/html/msdn_dcomfirewall.asp

Setting the backend SQL Server for SSIS
By default SSIS tries to use the local default instance as backend server. If your
SQL Server has a different name, you need to reconfigure SSIS to connect to your
SQL Server instance. We did following on both nodes of the cluster to configure
same SQL Server instance as the backend database for both SSIS service on both
nodes.

1. Open the configuration file C:\Program Files\Microsoft SQL
Server\90\DTS\Binn\MsDtsSrvr.ini.xml in notepad.

2. Find following piece of information in the file


MSDB
.


3. Change the server name value (between tags) to point to the actual
SQL Server name you will use.

4. Restart SSIS Service.

Clustering SSIS Service
By default SSIS service is installed on individual nodes and runs as a separate
service on both nodes. If you want clustering capabilities (failover etc.) you may
configure SSIS service to be a clustered resource. Please follow steps in the BOL
link below to configure SSIS on a cluster.

Installing SQL Server 2005 Components > Installing SQL Server Components How-to
Topics > Integration Services Installation How-to Topics > How to: Configure
Integration Services on a Cluster
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/223c3a59-84c3-4f60-be98-a8daf69e9473.htm