ok, so you have new solution and drop the file there and cannot use it.

If you, from solution explorer, copy and past the file, what happens?

re full path to cmd - not at all. I use the path to the bat file.

Have you got the Widow Style to hidden. Might be a conflict with lack...

Are you opening the dtsx file in bids or in a solution in bids?

Right clicking on the file and opening in bids will not allow you to run anything (The...

Yup. It will event ually timeout with a deadlock error.

You are reading from the variable while trying to write to it.

Do it in two steps.

Ummm, seeing as you have tried everything, I am rather stumped. The path to the file, it is fully qulified?

From agent, can you setup a step which a OS commend...

yup, makes sense. Is weird though that other processes can create files.

Think option of one column at a time is the best (last?) option now.

Curious to see what the problem...

I am the same 🙁 I still have many scripts floating around that use the "bad" stuff. Truth be told (noobs block your ears) I have never had a problem...

There's the gem. "When I put a where clause it hangs"

No it's not - it's SQL sh1tting itself to find the data because you do not have an index.

Here is...

Much better option.

Is rather weird...

Some comments though:

Don't select a table as a source. Rather use a query. (and not * either)

Two reasons:

1: Good practice.

2: Are you going to use all the...

Handy script (even if I don't agree with the approch) but handy non the less...

Instead of sysobjects and syscolumns etc, rather use the catalog views sys.objects and sys.columns.

If you change the property, it will run 32bit in bids.

The full path to 32bit dtexec in agent will force a 32bit execution as well.

Keep us posted.

Yes - JET does not function under 64 bit. You have to use 32.

@ lke2v - The vital bit of the message is gone. The last bit where it says...

Situations like this are normally due to "back pressure" where the destination is telling SSIS to "hold on a sec while I catch up". This is often seen with SQL...

noooooooooo that's hardley a solution. You just scrwed up the destination to match the source.

Rather fix the problem.

Does it happen with a different spreadsheet?