September 22, 2011 at 5:12 am
I have created a simple SSIS package which will create a .csv file and then it gets pasted to a ftp . The package executes successfully but when I tried to schedule sql job to run this package, it throws up an error
SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Option "/X86" is not valid. The command line parameters are invalid. The step failed.
In the job execution option I have set the option to use 32 bit runtime and also in SSIS i have set the properties to False for Run64BitRuntime
Any help to resolve this would be really appreciated.
Thanks in advance
September 23, 2011 at 7:09 am
Is the server 32-bit or 64-bit?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 23, 2011 at 11:29 am
thanks for the reply Koen, Server is 32 bit.
September 25, 2011 at 1:11 pm
What happens if you do not select the 32-bit runtime option in SQL Server Agent?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 25, 2011 at 11:02 pm
Thanks for the reply Koen. This one got resolved today. Issue was with the sql server agent's Services login ID and not with the 32-64 bit. previously I was getting an error and when i googled the error code, it literally mislead me and i set the 32 bit run time. Today I created a new SSIS package and then I set the SQL Server Agent Services Login ID to my ID , it just worked fine. I think I need to make the ID trusted or something like that. Im new to SSIS and not good in DBA part ..
Many thanks Koen...
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy