If a package executes another package, does the child package run with the same credentials as the parent?

I've had my share of frustrations with trying to define vars at runtime. I always seem to end up with this error one way or another:

Date3/9/2010 8:46:20 PM

LogJob History (AwardsExport)

Step...

Using that technique, do you embed the password in the connect string when you define the variable?

Elliot W bailed me out. I don't know if your problem is security related, but this saved me, and I get it now:

If a package is "encrypted with user key"....

Right you are, wow, thanks!! That makes perfect sense. I changed the credential my proxy points to the owner/editor of the package and I'm in business!

SA does no good in...

As you may have noticed, I'm in the same boat. In the past, setting up a proxy to point to valid credential, then setting the job up to use that...

I solved this problem by going into Project Properties, Debugging, and setting Run64BitRuntime to false.

I expect since I'm running 64-bit OS, SSIS thinks it should run 64-bit DTExec, but I...

Hey there CozyRoc, glad I found you!!

I'm in the same boat now. I'm getting this same error message these other folks are. I'm just trying to evaluate the CozyRoc...

Thanks. I searched a forum over on CrazyRoc, but I didn't find what I was looking for. I didn't see the FAQ's. I'll head over there.

I've come to lean...

Got it. Thanks for the explanation.

Yea, VS Starts, but if I try to create a new package, or open any existing package, I get the error.

I just got passed it. I got a System Restore...

Thanks, good to know. Curious though. You chose two separate non-raid drives, yet you are recommending I raid two drives into 1. Is this because of the gobs of memory...

You could let them kinow that you'd like to bring your long lost older brother in to shadow him for a coupple weeks. 🙂

Brian Savoie

How is the rest of...

Id definitely be on the MERGE bandwagon if I could. Problem is, while working through this issue, I discovered I'm going to have to deploy it on SQL 2005, so...

Interesting. Short, sweet, and simple. Avoids the concurrency problems of EXISTS.