I have changed it at the project level and and debugging working fine in BIDD. but when i execute the package through Agent it fails there . is there any way i can avoid this in agent level

How you are executing package from job ?? use 32 bit version of DTEXEC to execute package as Reza has suggested for this use the Operating System type of job step if you are using 2005 version in case of 2008 use checkbox on the Job Step page to run the package in 32-bit mode . Shailesh , Please mark the post as answered if it answers your question.

I have moved the package alone to other drive of my computer and started running the job from Agent. But this time error is with respect to source and connection managers. When i move the dtsx file from old loc to new location should i copy all other folders as well ie, bin etc?..And will it be easy if i deploy this package in server location than in file system and how to do it

you do not need any folders at deployment time, but if you have those folders path hard coded in the package, then you need to have them in deployment machine as valid path.http://www.rad.pasfu.com My Submitted sessions at sqlbits.com

I have changed the mode to 32 bit mode in job step execution mode and it is working fine. I have configured the package name in the job step and when i trigger the job it is getting excuted. Tell me if this is not the right way of doing it. And how can we trigger this using DTEXEC. I need the best practice in prod environment to execute the package.

I am trying to execute the package through a job from SQL Server Agent . Getting the error" Unable to load the package as XML because of package does not have a valid XML format. Failed to open package file "C:\Users\VaioUser\Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\ExceltoFile.dtsx.My package file location is "C:\Users\VaioUser\Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\ExceltoFile.dtsx. How can i get rid of this

Hello, Maybe Agent don't have permissions to the path you have specified Or you are pointing to wrong path. Make sure you are pointing to correct path. have to developed your package on SERVER at path (C:\Users\VaioUser\Documents\Visual Studio 2008\Projects\Integration Services Project1\Integration Services Project1\ExceltoFile.dtsx) ? or C:\ of your local machine?http://sqlage.blogspot.com/

Thanks it worked when i saved it in other folder than C drive. Job execution is working fine when i am having flatfile source and destination but when i am using excel destination i am getting the following error as i excute this in a 64 bit machine. The workaround i did is i changed the property of the project (changed Run64BitRuntime to false) in BIDS and the execution is fine in BIDS but through agent i am facing the same issue. How we could resolve this. "SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. End Error Error: 2011-08-01 20:09:45.99 Code: 0xC020801C Source: Data Flow Task Excel Destination [82]"

could you deploy your package to the other location than user's documents folder or desktop folder? the permission issues on those folder will cause some errors sometimes. in the other hand check do you have all package dependent files there? I mean configuration files? log providers and any other files you work with it in package. and also check the protection level of package to save sensitive data with EncryptSensitiveWithPassword. http://www.rad.pasfu.com My Submitted sessions at sqlbits.com

If you are selecting Use 32 bit runtime on the Execution options tab of the New Job Step dialog box then job step type of SQL Server Integration Services Package invokes the 32-bit version of the dtexec utility, and the package runs in 32-bit mode. see this article in MSDN http://msdn.microsoft.com/en-us/library/ms141766.aspx and here Todd's post on SSIS in 32 bit and 64 bits http://toddmcdermid.blogspot.com/2009/10/quick-reference-ssis-in-32-and-64-bits.html Shailesh , Please mark the post as answered if it answers your question.

As Aamir mention.. It is probably the PATH problem ... try to deploy you package to some other loaction with different name and then try to run with Agent. a quick check, please check the following thread (who is having same problem) can solve your problem. http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/c93d3e10-8b26-413a-9062-ea54d4d31983 http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/044b49c2-490d-4aa3-a1df-64f708705e9c/ Let us know your observation.. Let us TRY this | Mail me My Blog :: http://quest4gen.blogspot.com/

"SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. End Error Error: 2011-08-01 20:09:45.99 Code: 0xC020801C Source: Data Flow Task Excel Destination [82]" Buddy, Go to Project –> Project Properties –> then Set Run64BitRuntime = False. Let us know your observation Let us TRY this | Mail me My Blog :: http://quest4gen.blogspot.com/

Thanks it worked when i saved it in other folder than C drive. Job execution is working fine when i am having flatfile source and destination but when i am using excel destination i am getting the following error as i excute this in a 64 bit machine. The workaround i did is i changed the property of the project (changed Run64BitRuntime to false) in BIDS and the execution is fine in BIDS but through agent i am facing the same issue. How we could resolve this. "SSIS Error Code DTS_E_OLEDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64-bit version of SSIS, as no OLE DB provider is available. End Error Error: 2011-08-01 20:09:45.99 Code: 0xC020801C Source: Data Flow Task Excel Destination [82]" this is 64bit issue, you should run the package with 32 bit version of DTEXEC, you can find the 32 bit version of DTEXEC here: <system drive>:\program files x86\microsoft sql server\<version>\DTS\Binn\DTExec.exe and run the package with dtexec command, samples of dtexec command can be found here: http://msdn.microsoft.com/en-us/library/ms162810.aspxhttp://www.rad.pasfu.com My Submitted sessions at sqlbits.com

you did it right, one way is change the execution option to "use 32 bit runtime". another way is to set the job step type as CmdExec, and write the DTEXEC command there, just note to use 32 bit dtexec like this: c:\program files x86\microsoft sql server\100\dts\binn\dtexec.exe /f "C:\UpsertData.dtsx" (there is no difference between these two ways, when you check the use 32 bit runtime, the dtexec 32 bit will start the package. http://www.rad.pasfu.com My Submitted sessions at sqlbits.com