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.
| Author |
Topic |
|
shebert
Yak Posting Veteran
85 Posts |
 Posted - 2012-11-21 : 11:59:49
|
| So I am trying to migrate sql 2005 to a new server from win2003 32bit to win 2008 R2 64 bit.i found out that my SSIS packages that have been dumping data from my DB into excel and emailing reports wont run in 64 bit OS.here is what i have done so far to try and get them to work.I installed sql 2008 SSIS recreated the package and set Run64BitRunTime to false. package test O.K.deployed to the sql server set job ne job to run the package.under execution options on the job i check the use 32bit run time.Still getting this error below, What did I miss?MessageExecuted as user: LUMINUSDEVICES\ld_admin. Microsoft (R) SQL Server Execute Package Utility Version 10.50.1600.1 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 11:44:59 AM Error: 2012-11-21 11:45:00.63 Code: 0xC0202009 Source: MonthlyShipped Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80040E4D Description: "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.". End Error Error: 2012-11-21 11:45:00.63 Code: 0xC020801C Source: Data Flow Task Excel Destination [61] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2012-11-21 11:45:00.63 Code: 0xC0047017 Source: Data Flow Task SSIS.Pipeline Description: component "Excel Destination" (61) failed validation and returned error code 0xC020801C. End Error Error: 2012-11-21 11:45:00.63 Code: 0xC004700C Source: Data Flow Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2012-11-21 11:45:00.63 Code: 0xC0024107 Source: Data Flow Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:44:59 AM Finished: 11:45:00 AM Elapsed: 1.482 seconds. The package execution failed. The step failed. |
|
|
sunitabeck
Master Smack Fu Yak Hacker
5155 Posts |
Posted - 2012-11-21 : 13:26:22
|
quote:
The workgroup information file is missing or opened exclusively by another user
That sounds like some file or other is locked by another process. This can certainly happen if you have the xlsx file opened in Excel. If that is not the case, try to import a brand new file that you know is not the subject of anyone else's attention. |
 |
|
|
shebert
Yak Posting Veteran
85 Posts |
Posted - 2012-11-26 : 15:32:05
|
| no the file is not opened, the excel connector just refuses to work in a win 2008 r2 64 bit enviroment.anything else you can think of trying? |
|
|
|
shebert
Yak Posting Veteran
85 Posts |
Posted - 2012-11-26 : 16:06:05
|
| if i install 64 bit office can i run the package 64 bit? |
|
|
|
mandm
Posting Yak Master
120 Posts |
Posted - 2012-11-26 : 18:10:06
|
| Have you tried changing the "Run64BitRunTime" setting to False in Project\Properties\Debugging? |
|
|
|
shebert
Yak Posting Veteran
85 Posts |
Posted - 2012-11-26 : 22:17:56
|
| yes and the package will run in visual studio just not as a sql agent job |
|
|
|
mandm
Posting Yak Master
120 Posts |
Posted - 2012-11-27 : 14:21:27
|
| Then you need to set up the agent job to run the 32 bit DTEXEC. See the link below.http://support.microsoft.com/kb/934653 |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
|
|
|
|
|
using excel connector on 64 bit windows 2008 R2