My local SQL Server Version is : Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 3) I have a package that use Access database with Microsoft Jet OLEDB 4.0 provider. 1. When I run it in the debugger it is successful. I think the Solution Properties of Run64BitRunTime is ignored as 64bit SSIS is not installed on my local. So the result make sense. 2. When I run it using Execute Package Utility it is successful. This result make sense as well. As DTExecUI.exe is a 32-bit application. Because of this, whenever I execute a package from DTExecUI.exe, it will execute in 32-bit application. 3. When I run it from command file for example run the file of RunMaster.cmd, it is successful. "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTEXEC" /f "C:\SSIS\Master.dtsx" This result make sense as well. As I've invoked my local DTEXEC that is 32 bit executable. 4. When I run it using the below script from SQL Server Management studio, it failed. EXEC xp_cmdshell 'dtexec /FILE "C:\SSIS\Master.dtsx"' The errors like below, abc is the access database connection name. I don't know why this time I failed. The AcquireConnection method call to the connection manager "abc" failed with error code 0xC0202009. The AcquireConnection method call to the connection manager "abc" failed with error code 0xC0202009. component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. component "OLE DB Source" (1) failed validation and returned error code 0xC020801C. One or more component failed validation. One or more component failed validation. 5. When I run it using SQL Agent job and run the below command line in the step. It failed again. I got the same errors list in 4. "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\DTEXEC" /f "C:\SSIS\Master.dtsx" Why? I think 5. is very similar to 3. The only difference is the way to invoke the command. I am not sure it is issue about the 32bit or 64bit or any other reason. As my local machine should be 32bit only, so I should not have any issue about 32bit or 64bit. I also have the other packages that use SQL Server Connection that worked for all the above steps. Any idea? Thanks Helen