November 17, 2017 at 4:40 am
sqlsniffer - Friday, November 17, 2017 4:37 AMI have set my Run64BitRuntime to False
Could you post the DTExec command you're using? Feel free to obfuscate any data.
Thanks.
Edit: nevermind:
/X86
(Optional). Causes SQL Server Agent to run the package in 32-bit mode on a 64-bit computer. This option is set by SQL Server Agent when the following conditions are true:
The job step type is SQL Server Integration Services package.
The Use 32 bit runtime option on the Execution options tab of the New Job Step dialog box is selected.
You can also set this option for a SQL Server Agent job step by using stored procedures or SQL Server Management Objects (SMO) to programmatically create the job.
This option is only used by SQL Server Agent. This option is ignored if you run the dtexec utility at the command prompt.
https://technet.microsoft.com/en-us/library/ms162810(v=sql.105).aspx
If you're running locally, then you can't run the package in 32bit mode via dtexec's X86 parameter
Does the package run in your run it in designer?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
November 17, 2017 at 5:01 am
Thom A - Friday, November 17, 2017 4:40 AMsqlsniffer - Friday, November 17, 2017 4:37 AMI have set my Run64BitRuntime to False
Could you post the DTExec command you're using? Feel free to obfuscate any data.
Thanks.
Edit: nevermind:
/X86
(Optional). Causes SQL Server Agent to run the package in 32-bit mode on a 64-bit computer. This option is set by SQL Server Agent when the following conditions are true:
The job step type is SQL Server Integration Services package.
The Use 32 bit runtime option on the Execution options tab of the New Job Step dialog box is selected.
You can also set this option for a SQL Server Agent job step by using stored procedures or SQL Server Management Objects (SMO) to programmatically create the job.
This option is only used by SQL Server Agent. This option is ignored if you run the dtexec utility at the command prompt.https://technet.microsoft.com/en-us/library/ms162810(v=sql.105).aspx
If you're running locally, then you can't run the package in 32bit mode via dtexec's X86 parameterDoes the package run in your run it in designer?
I am using designer and not utility and it doesn't work in designer.
November 17, 2017 at 5:40 am
twin.devil - Friday, November 17, 2017 3:47 AMJust want to share few comments might help the OPIf you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
There is a small nuance to be added to this. When you execute a package from SSDT, it spawns a DTExec.exe process to perform the execution.
If you are using a 64-bit OS, by default the 64-bit version of DTExec.exe will be spawned – and it is only by checking the 'use 32-bit runtime' flag that you force SSDT to spawn the 32-bit version of DTExec.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
November 20, 2017 at 5:45 am
November 20, 2017 at 10:40 pm
Phil Parkin - Friday, November 17, 2017 5:40 AMtwin.devil - Friday, November 17, 2017 3:47 AMJust want to share few comments might help the OPIf you are running in your ssis package in the Designer mode i.e. in SSDT then you need to make sure you have 32 bit ACE driver. Doesn't matter if you are using a 64 bit OS.
If you want to run your ssis package using DTEXE Utility and your OS is 64 bit, then you have two option whether to run in 32 bit or you want to run it in 64 bit.For more detail you can refer to Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing
Hope it helps.
There is a small nuance to be added to this. When you execute a package from SSDT, it spawns a DTExec.exe process to perform the execution.
If you are using a 64-bit OS, by default the 64-bit version of DTExec.exe will be spawned – and it is only by checking the 'use 32-bit runtime' flag that you force SSDT to spawn the 32-bit version of DTExec.
Good catch Phil. Excel never have been a good friend of SSIS after all 😛
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply