SSIS Package won't execute when called

I have an 2005 SSIS package that I'm calling in a service created in VS 2005. The package will not run. The purpose of the package is to parse a file and put data into a "Load Table".

The package runs perfectly on its own, but will not run at all when executed programatically - when I'm stepping through the code. The Event Viewer indicates that the package has started but then it indicates that it has failed. I don't get any more information than that.

It's not throwing an exception. It's just returning "Failure". I've tried execut开发者_Go百科ing against different databases - Same result. The file it's parsing is valid becuase it runs fine when run on it's own.

The only other thing that I can think of is that I'm having some problem with user permissions, but I have no idea on how to go about looking into that issue. Does anyone have any ideas?

---

Sounds like a permissions issue. Make sure the process it is running as has the same permissions as the account which you are using to run it interactively.

---

Without more information it's hard to tell, but this sounds like a permissions issue.

When it's running from code, does the person or user account the code is running under have the appropriate permissions?

For example, if you run it manually, you're most likely using your own credentials. As the developer, I'd assume you have admin rights, so you can perform the task.

However, when run from a program you need to know what user account the program runs under. Is it Asp.Net? The default user is Network Service. Is it a Scheduled Task running under the default Local System account? You'd need to change the account it runs under or grant permissions on the DB appropriately.

---

When you loaded it from Studio to Integration Services, what Package Protection Level did you use? I've had the best luck with the last in the list: Rely on Server Storage and roles for access control.

---

Does your package have error logging set up? It could help you to see what the problem is.

Also, does the account for the service running the package have the correct rights to the directory where the file to be picked up is stored not just correct rights in SQL Server? We've had that problem before.

---

Have you attached Events to the execution of the package? Are you calling the package by code? Which Method are you using?

Please check Loading and Running a Remote Package...

Then when debugging, add a break point at the Console.Write Line where gets info of the error.

Hope it helps,

Arturo