Exporting to Excel from 64bit SQL Server

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SSIS and Import/Export (2005)

Exporting to Excel from 64bit SQL Server

Author

Topic

SHardy
Starting Member

35 Posts

Posted - 2007-11-15 : 11:04:32

Hi,

I am currently in the process of migrating a BIS DB rom SQL 2000 to SQL 2005. This has involved migrating a whole load of DTS to SSIS. This gone, on the whole, pretty well.

However, I still have one package that doesn't work. This package exports some data to text files AND a to a couple of Excel files. However, the Excel part is not working. I get the following errors:

[Excel Destination [130]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "xls_DirectMail_CampaignFile2" failed with error code 0xC0202009.

[Connection manager "xls_DirectMail_CampaignFile2"] Error: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".

Now, I am guessing that this is because there is no MS Office installation on the server. Would this be correct?

What would be the minimum software requirement to get this working?
Would simply installing Excel be enough?

Thanks,
Simon

SHardy
Starting Member

35 Posts

Posted - 2007-11-15 : 12:04:01

Hmmm. Excel now installed, but still the same errors.

HELP!!!! :)

SHardy
Starting Member

35 Posts

Posted - 2007-11-16 : 10:38:00

Ok, looks like be that the problem is because this is on a 64bit OS running 64bit SQL Server.

However, from what I can understand Visual Studio is only 32bit. So should this not work when debugging?

How should I best go about exporting this data to Excel, bearing in mind the 64bit issue?

Thanks,
Simon

P.s. topic title changed to reflect this change of approach.

SHardy
Starting Member

35 Posts

Posted - 2007-11-16 : 11:58:44

Ok, got it. So there is an property at the project level called "Run64BitRuntime" which needs to be set to FALSE. All seems to be ok.

Why would this be at a wide a scope as project rather than at package level?

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources