I never did figure out why it would work in one place and then not installed on the server.   I'm still thinking there is potentially a permissions issue.   I did...

Thanks for the recommendation.   I'll see if i can use it temporarily, as it's not something that is just 'available' here, and I don't get to set the environment rules. ...

script task, using Dts.log

            Dts.Log("FileExists: " + Dts.Variables["User::FileExistsResult"].Value.ToString(), 0, emptyBytes);
      ...

thoughts on step or details I could add that will help to help me diagnose this issue?

It's looking like it's going to be a very specific context (which i'm still working on running down), and the current security context won't be used (still not sure why...

interesting. The two open queries using TSQL and openquery now work with a 'forced' security context. The two LDAP dialect queries still do not work.

still... THANK YOU!!!! i'm...

will try that. i do know that i had the where clause on there with same results, so was just trying to simplify the most i could. thanks!

all generated the same error in SSMS. dialect didn't matter.

SELECT * FROM OPENQUERY( ADSI,

'SELECT name

FROM ''LDAP://DC=sfcc,DC=spokane,DC=cc,DC=wa,DC=us''

...

i guess my other option is to create a table to hold the data and then use powershell to pull and push the data in. I'd rather not...

LOL, i'm quite certain that I could as well.

I have found that there are certain times that i'll go one route using the update statement, but will also adjust...

http://jingyangli.wordpress.com/2011/11/22/modify-the-default-setting-edit-top-200-rows-or-select-top-1000-rows-in-sql-server-2008-management-studio-2/

indicates that if you set it to 0 that it returns them all.

i tested it and it seems to work.

this article describes how to change the default.

http://www.websource99.com/2012/07/27/how-to-edit-more-than-200-rows-in-sql-server-2008-management-studio/

is that what you are looking for?

Choose your Edit 200...

Then select the button: 'Show SQL Pane'

then change the 200.

I would either:

A) change the destination table to allow nulls and then put a default value constraint on it so when it encounters nulls, it places a set value in...

this was a simpler fix than i thought. the object that was complaining was a schema bound object. It didn't need to be bound, and once i...