Showing posts with label fail. Show all posts
Showing posts with label fail. Show all posts

Sunday, February 19, 2012

Execute Package Task fail with "Access Denied"

Hi all,

I have an error when a package is trying to execute a SubPackage using the "Execute Package Task". I have this problem for all packages that are running sub packages.

The packages are stored in the DTS\Packages folder of the SQL Server installation folder.

The master package is called from an Event Handler on a document library in MOSS 2007.

The account from the Sharepoint Application Pool has Full Control on the DTS\Packages folder.

What am I missing ?

Does it work OK if you run it from BIDS?|||

Yes!

Actually, adding the account of the SPS Process to the Local Admin group on the SSIS server made it work but I don't understand why. This user account already had Read&Execute and Write NTFS permissions on the folder where the SSIS packages are stored and it works for the other packages, only the sub packages returns an "Access Denied" error.

I should have said that I have 2 servers, one SPS server and one SQL/SSIS Server.

I would prefer not to add the SPS User account to the Local Admin group on the SQL/SSIS Server, if anyone has an idea how to avoid this please let me know.

Execute Package Task always Fail When ExecuteOutOfProcess = False

Why does the Execute Package Task in SSIS always fail when set to execute in-process?

Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.

I have also tried it from Command Line using dtexec., same results.

The problem with setting ExecuteOutOfProcess = True all the the time and running from within Bi Studio is that an enourmous amount of processes is created, none of which die because SSIS runs in Debug mode, another problem which is there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.

By Dying I mean, thrashing of the CPU & Memory. Page file to extreme limits.

And yes, the hardware should be able to take much more than what SSIS is supposed to eat. Dual 3GHz Xeon & 4GB of Ram.

Thank you.

My kind regards,

Eng. Ahmad Alkilani

Eng. A. Kilani wrote:

Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.

What error message do you get?

Eng. A. Kilani wrote:

there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.

If you start the package using Ctrl-F5, BIDS starts one dtexec.exe process. When the package ends, just close this console window. I don't see how you can get numerous dtexec.exe processes. Do you mean dtshost.exe processes (these may be left behind for some time if parent dtexec.exe process is forcefully killed)?

|||Problems may already be solved, but for people like me who are looking for a solution to this problem: If ExecuteOutOfProcess is set to True bugs in the childpackage doesn't cause the parent package to stop because of this bug. It will also be possible for a single package to use more then 2GB of memory on it's own.

Execute Package Task always Fail When ExecuteOutOfProcess = False

Why does the Execute Package Task in SSIS always fail when set to execute in-process?

Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.

I have also tried it from Command Line using dtexec., same results.

The problem with setting ExecuteOutOfProcess = True all the the time and running from within Bi Studio is that an enourmous amount of processes is created, none of which die because SSIS runs in Debug mode, another problem which is there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.

By Dying I mean, thrashing of the CPU & Memory. Page file to extreme limits.

And yes, the hardware should be able to take much more than what SSIS is supposed to eat. Dual 3GHz Xeon & 4GB of Ram.

Thank you.

My kind regards,

Eng. Ahmad Alkilani

Eng. A. Kilani wrote:

Having ExecuteOutOfProcess = False always results in that the package fails when run from within BI Studio.

What error message do you get?

Eng. A. Kilani wrote:

there doesn't seem to be a way to run it in Release mode so as not to get so many Dtexec processes, which ultimately results in having the Server die.

If you start the package using Ctrl-F5, BIDS starts one dtexec.exe process. When the package ends, just close this console window. I don't see how you can get numerous dtexec.exe processes. Do you mean dtshost.exe processes (these may be left behind for some time if parent dtexec.exe process is forcefully killed)?

|||Problems may already be solved, but for people like me who are looking for a solution to this problem: If ExecuteOutOfProcess is set to True bugs in the childpackage doesn't cause the parent package to stop because of this bug. It will also be possible for a single package to use more then 2GB of memory on it's own.