January 11, 2011 at 1:15 pm
Where in package properties, do I set run In 64bit = false?
May 11, 2011 at 11:12 am
After going thru the long list of replies I tried to run it thru CMD
I modified the job to use cmdexec step and : C:\Program Files (x86)\Microsoft SQL Server\90 \DTS\Binn\DTExec.exe /f "Package Path" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW
And it executed just like you are having a piece of Cake.
Thanks for the Inputs.
May 27, 2011 at 2:49 am
Hi I am Ramesh from Chennai, India.
I am also facing the same problem but I am using data source as Excel file. Error displayed as below...
FirstLine:
"[Excel Source [17]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009"
SecondLine:
[Connection manager "Excel Connection Manager"] 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".
Can any one help me....?:hehe:
March 19, 2013 at 1:46 pm
Thanks for the info on set 64bit run to false, that fixed my SSIS issues!
March 24, 2014 at 7:26 pm
First of all I hate SSIS2005 ... it has too many bugs ... (preferably use 2008R2 or 2012)
Things you can check are as follows:
1. Make 64bit false
2. Delay validation = False (in the body of package and on all objects)
3. EncreptionMethod = SensitiveWithPassword
4. If you changed number 3 reopen your data connections and re enter username password to be encrypted with the new method.
5. SQL Agent Service account has access to your Excel/Access datafile location
6. Create the SQL Job from SSMS2005 not SSMS2008/2012
7. be patient ... 🙂
Cheers
Amir
April 22, 2014 at 6:53 am
I am able to run the SSIS package just fine by itself, and I am using my sql account. The issue happens when I add it to the SQL server agent to execute, that's when my package fails.
Any thoughts?
amirhh2000 (3/24/2014)
First of all I hate SSIS2005 ... it has too many bugs ... (preferably use 2008R2 or 2012)Things you can check are as follows:
1. Make 64bit false
2. Delay validation = False (in the body of package and on all objects)
3. EncreptionMethod = SensitiveWithPassword
4. If you changed number 3 reopen your data connections and re enter username password to be encrypted with the new method.
5. SQL Agent Service account has access to your Excel/Access datafile location
6. Create the SQL Job from SSMS2005 not SSMS2008/2012
7. be patient ... 🙂
Cheers
Amir
December 8, 2015 at 9:32 am
March 10, 2016 at 8:32 am
It's a two-fold process to over come this error, but both very simple fixes. I used this post to solve the issue. - http://microsoft-ssis.blogspot.co.uk/2012/09/swtich-package-from-64bit-to-32bit.html
April 20, 2016 at 1:18 pm
in the lower left of the validate screen is a Check Box to run 32 Bit.
This worked for me!
Changing the setting under DEBUG to 64Bit False did not work for me.
May 5, 2020 at 9:26 am
Hello, just in case this is helpful, I had exactly the same issue, and upgraded the OLE DB provider on the machine I deployed to, and it finally worked.
https://www.microsoft.com/en-us/download/confirmation.aspx?id=56730
Viewing 10 posts - 46 through 54 (of 54 total)
You must be logged in to reply to this topic. Login to reply