Davy's Blog » Integration Services

SQL Server Day 2009 videos now available on Chopsticks

Davy — Wed, 16 Dec 2009 10:10:05 +0000

Microsoft has made the sessions presented on SQL Server Day 2009 available on Chopsticks

Opening Keynote by Wesley Backelant and Ritchie Houtmeyers
Best Practices for SQL Server Consolidation by Tom Van Mulders
Breaking the ETL world record with Integration Services by Henk van der Valk
Designing Effective Aggregations in Analysyis Services 2008 by Chris Webb
High availability for BI DWH by Patrick Tack
How New.NET Development technologies could change the live of the SQL DBA guy/girl by Gill Cleeren & Kurt Claeys
Implementing best practices with Policy Based Management by Nico Jacobs
Introducing to PowerPivot or How I Learned to Stop Worrying and Love Excel by Chris Webb
Tracking Changes and Data movement in SQL Server 2008 by Dirk Gubbels
Handling XML in SQL Server by Nico Jacobs

Have fun!

Connect to SSIS Service failed: Error loading type library/DLL

Davy — Fri, 18 Sep 2009 09:44:08 +0000

After installing SQL Server Integration Services on an existing 64-bit SQL Server, I was unable to connect to SSIS using Management Studio.

The database engine and Analysis Services was already installed on this server. I added the SSIS service without Service Pack and applied SP3 afterwards. When trying to connect, Management Studio returned the following error message:

Connect to SSIS Service on machine “ComputerName” failed:
Error loading type library/DLL.

I found the explanation in the following support article: KB919224

This problem occurs because the installer unregisters the 32-bit Dts.dll file when the installer installs the 64-bit Dts.dll file. The 64-bit Dts.dll file is installed together with SQL Server 2005 SP2. Additionally, the 64-bit Dts.dll file may be installed together with any SSIS hotfix package that contains the 64-bit Dts.dll file.

The solution is to reregister the 32-bit dll’s manually:

%windir%\syswow64\regsvr32 “%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

%windir%\syswow64\regsvr32 “%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\MsDtsSrvrUtil.dll”

For more info and some variations on the same problem, goto KB919224

Import Excel files with SQL Server Integration Services on a 64-bit server

Davy — Tue, 26 Aug 2008 15:22:00 +0000

Today I deployed some SSIS packages to a test environment. These packages needed to import some excel files to a certain database. Testing the packages resulted in the following error:

Error 0xc0202009: {F1B3B35C-FAE3-48F6-A169-4E4D8D99F9B6}: An OLE DB error has occurred. Error code: 0×80004005.
An OLE DB record is available. Source: “Microsoft JET Database Engine” Hresult: 0×80004005 Description: “Unspecified error”.

Error 0xc020801c: Data Flow Task: The AcquireConnection method call to the connection manager “DestinationConnectionExcel” failed with error code 0xC0202009.

It seems there just isn’t an 64-bit version of the JET OleDb driver for Excel and because the test server was a 64-bit, this caused the Excel-import to fail.

To make the package work using BI-studio you need to change your project debugging properties: Set Run64BitRuntime to False
To make the package work when started from a SQL Server Agent Job, you need to execute the package using the 32-bit version of DTExec.
To do this create a Operating System Job Step and type the command to execute the package using DTExec in the 32-bit folder: C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\

An easy trick to retrieve the command to execute the package is copying it from Execute Pacakge Utility:

The complete commmand will be something like this:

C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\dtexec.exe /DTS “\MSDB\Import” /SERVER “.” /MAXCONCURRENT ” -1 ” /CHECKPOINTING OFF /REPORTING V

Good luck!