Nope, Connecting to a Sql Server via Integrated Security (AD account)...not Sql Account so no password is being passed...

I did verify the query I had before, returned correct results when I logged into SSMS as that user...

Nope, same thing...

Found issue, Search was passed to C# via ssis variable.

Works if I defined , populated and used variable local to C# but

not if I used variable passed in.

I'm running from my desktop, directory is UNC, there is a LoggingMode in the

Property Expressions Editor, but have found NO documentation on it...

Sorry about the forum post, can it...

Mine is relatively close to this one.

My process deletes files from archive after x days.

I hit the loop and get the same complaint, but I've previously

moved 1 file to the...

Using strictly ssis tasks, for each file enumerator, script task to get file info,

conditionally delete file, done.

Works great if the directory is not empty, barfs a warning, then fails after...

Guess the query works fine if you don't let SSMS do it for you...

We're in 2012 Azure... From SSMS the selection is greyed out..

Found the issue. the agent has this little checkbox "Include step output in history", cured the problem...

So, back to the original question, one console writes to the agent log correctly, one does not, same

methodology to do the output...

Looking for clues...

Thanks

Also, since I'm deploying to MSDB, are the "All Executions" reports available ?

Nope, older package deployment, right now we have no reason to use the package deployment...

Thanks

From Data flow, Flat File source, edit, changing connection manager from one with hardcoded values to one with variables (delayed validation enabled). When I do, it picks up different values...