Your right it would and here it is.

I figured out the issue, even though I had a constrait after each Executed Package to move onto the next step, SSIS viewed...

The task is fired that calls the other package its when the other package is finished it doesn't continue to the next task in the main package, I have a...

That worked perfect, easy and simple.

Thanks!

Ok, I have it set up now similar to that.

Thanks!

This might be a long route but this what I have done and seems to work:

Step 1: Script Task - Read in text file & count the header row if...

That's what I thought.

Can I put the 2 datasources and the controlling logic in the data tab of 1 SSIS package or do I need to have 2 seperate SSIS...

My resolution:

When building the job the

Step 1 was using "Type: Operating System (CmdExec)" then in the command line net use Z: \\10.239.130.170\export password /user:administrator

Step 2 was "Type: SQL Server Integration...

Koen Verbeeck (3/10/2011)

---

Brandie Tarvin (3/10/2011)

---

From what I read on the initial email, it sounded to me like the file is local to the server. Koen, however, keeps mentioning the words...

I think your right, its permissions. I thought about this last night and how early on I read the file off the non-domain server but created the new file local...

Is there a way to simply test whether this is truly a permission issues?

I just think I have tried so many things and changed by package so much can I...

How do I do either of those?

Thanks!

I think I am going to scrap and start over to see if that is the real issue.

I don't know at this point. :w00t:

I changed it to USER1\Users because 1 folder had Adminstrator and a higher folder had Administrators (with an s) didn't know if that made a difference so Users was consistant...

Brandie Tarvin (3/8/2011)

---

Oh, don't give up hope quite yet. This is a stand alone box, then?

EDIT: sorry. Just now caught up with the start of the thread. I followed a...

Brandie Tarvin (3/8/2011)

---

smac (3/8/2011)

---

So our administrator created the Credential

Name: OEM PC Admin

Identity: 10.239.130.111\Administrator (since this pc is not on the domain)

Created.

New Proxy, select credential, failed.

Proxy "10.239.130.111\Administrator" is not a valid...