Wednesday, September 16, 2009

SQL Server Management Studio to SSIS with 'Error loading type library/DLL'

TITLE: Connect to Server
------------------------------
Cannot connect to xxxx.
------------------------------
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 "xxxx" failed:
Error loading type library/DLL.
-----------------------------
Connect to SSIS Service on machine "xxxx" failed:
Error loading type library/DLL.
------------------------------
BUTTONS:
OK
------------------------------


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:
Library not registered. (Exception from HRESULT: 0x8002801D
(TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
------------------------------
Library not registered. (Exception from HRESULT: 0x8002801D
(TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)
------------------------------
BUTTONS:
OK
------------------------------

Solution:
======================
We Need to Un-Register both 32Bit and 64Bit of Dts.dll and Un-Register both
32Bit and 64Bit of MsDtsSrvrUtil.dll and Re-Register both 32Bit and 64Bit of
Dts.dll and both 32Bit and 64Bit of MsDtsSrvrUtil.dll

==================
In another issue of 32-bit SQL Server installation on a 32-bit windows 2003, we were
getting exactly the same error.

Resolution: Resolution in that issue was also same as the above.

Registering the Dts.dll and MsDtsSrvrUtil.dll from %PROGRAM FILES%\Microsoft SQL
Server\90\DTS\Binn folder.

=================
Cause: During each service pack setup, we unregister the older versions of these
DLLs (along with a lot of others), copy the new ones and re-register them. The
registering phase may have failed on these files. The installation log of the
service pack can confirm us that.

No comments: