?
Solved

SSIS 2005 - Execute Package Task Getting error

Posted on 2012-08-16
9
Medium Priority
?
657 Views
Last Modified: 2013-11-18
Hi and thanks,

I am getting this error:
SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.

this is what is really confusing:
If I run the package by its self it works fine.

But as soon as I try to run this same package using:
Execute Package Task

I get the error.

any ideas why this is happening?

Please help
0
Comment
Question by:Amour22015
  • 6
7 Comments
 
LVL 25

Expert Comment

by:TempDBA
ID: 38302685
0
 

Author Comment

by:Amour22015
ID: 38304669
Hi,

To me it looks like I am not linking to the correct package(even though the names are the same).  I have changed the connection to "windows authentication" and I took away the password option.  Note that everything is on the same server.  If you notice in the attachment not all packages come up to select?  Where does this window "Select Package" look at?  I think it is looking at the old package name not the updated one?

Thanks for any help
0
 

Author Comment

by:Amour22015
ID: 38304766
Forget to attach:
Exepackage.docx
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 

Author Comment

by:Amour22015
ID: 38304783
Hi,

I think I am on the right track?  I just renamed the package yet it did not come up under the "Select Package" option.

So all I need is for someone to tell me (or head me in the correct location) as to where this "Select Package" option is looking?

Thanks for any help
0
 

Author Comment

by:Amour22015
ID: 38311367
Hi,


Well, that wasn't the problem.

I created a connection to the correct package (One project, Package calling another package, and the package being called are all in the same project).  Same problem.

Seems like the problem is in the "Execute Package Task".  What could I be doing wrong?

Thanks for helping
0
 

Accepted Solution

by:
Amour22015 earned 0 total points
ID: 38312529
Hi,

I think I found the problem:

In the "Execute Package Task"

there is an option:
"ExecuteOutOfProcess"
I had this set to True

I changed it to False

Seems to be working

Thanks
0
 

Author Closing Comment

by:Amour22015
ID: 38332110
Great
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
Originally, this post was published on Monitis Blog, you can check it here . In business circles, we sometimes hear that today is the “age of the customer.” And so it is. Thanks to the enormous advances over the past few years in consumer techno…
Using examples as well as descriptions, and references to Books Online, show the documentation available for datatypes, explain the available data types and show how data can be passed into and out of variables.
Viewers will learn how the fundamental information of how to create a table.
Suggested Courses

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question