Hi, I have a package that I have deployed. When I Connect through SSMS to Inegration Services and right click on the package (its in the MSDB) and right click > Run Package, it executes fine. But when I run it through the SQL agent, It reports success, but doesnt actually do anything! I thought this was a permissions thing, so to test I changed the Agent account to run under my Account (the one that I am using to manually execute the package), but I am still getting the same problem. Any ideas what this might be? Zoe

Hi Zoe, Did you have the log generated for the package when executed from SQL Agent job?Please mark my post as an answer if I helped you to resolve the issue or vote up if I helped you.Thanks. Regards and good Wishes, Deepak.

Are you sure you are connected to the correct database(s)?Todd C - MSCTS SQL Server 2005 - Please mark posts as answered where appropriate.

You need to understand that when you connect to your server through SSMS and right-click "execute" the package... you are NOT executing it on the server. You are executing the package on the computer that's running SSMS. SSIS 2005/2008 is NOT as server/service type system. You have taken good steps by setting up a proxy to execute the job. But in order to diagnose the true problem, you'll need to post the history results of the SQL Agent Job. Talk to me now on

Hi there! Deepak - I didnt have the log generated - is this difficult to do? Todd C - Yep, definately Todd McDermot - SSMS is installed on the server, so im executing it directly from there. (I know its bad practice, but hey) There are no history results from the Agent Job - It just says 'succeeded', but when I check the data, nothing has happened. I just cant understand why manually executing it works but running it from an Agent (using the same account) doesnt...

Hi Zoe, Please check http://msdn.microsoft.com/en-us/library/ms141212.aspx to enable SSIS logging. Check the log and concentrate on Onerror, OnWarning, OnINformation.Please mark my post as an answer if I helped you to resolve the issue or vote up if I helped you.Thanks. Regards and good Wishes, Deepak.

What does the package actually do? If we know what it is supposed to do, it might make troubleshooting easier.MCTS, MCITP - Please mark posts as answered where appropriate.

Essentially it imports data into the database. I have 2 empty tables that should be populated, but when the agent executes them, they remain empty. Executed manually, I see the data I expect.

Thats weird, Ive tried to run the package using DTEXEC using the following Command: dtexec /CustomerClaimData /server <Instancename,Portnumber> But I get the error: Option "/CIAO_CustomerClaimData" is not valid This is the same syntax I use on 2005 instances- This is a 2008 instance - Do I need to change thge syntax?

From the sql server , the option is to use /SQL . http://msdn.microsoft.com/en-us/library/ms162810.aspxPlease mark my post as an answer if I helped you to resolve the issue or vote up if I helped you.Thanks. Regards and good Wishes, Deepak.

oh thanks, I used that which executes fine from the cmmand prompt, but not from the SQL Agent.

Doesn't matter if you are running SSMS on the server or your locl machine. Todd's reply was sending you down the correct path. http://blogs.lessthandot.com/index.php/DataMgmt/DBAdmin/ssis-runs-in-bids-but-not-with-sql-agentTed Krueger Blog on lessthandot.com @onpnt on twitter Please click the Mark as Answer button if a post solves your problem!