Problem with SSIS 2012

[Richard Deeming]

This is an English-language forum. Please post your questions in English. Il s'agit d'un forum de langue anglaise. S'il vous plaît envoyer vos questions en anglais. https://translate.google.com/[^]

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[amioni]

done

[Richard Deeming]

Is your package running as a SQL Agent job? You might need to change the permissions on the TEMP directory: http://support.microsoft.com/kb/933835[^]

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[GuyThiebaut]

amioni wrote:

e.UniqueID e. [Web Id] from Elements

I am not seeing a comma between the two columns you reference, is that correct?

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[amioni]

it s just an example of a query so dont worry it s with comma in my package, and it s not the problem

[amioni]

i run it from VS2012 so i dont know if it s with sql agent or not (beginner ) and where i can find Temp directory

[Richard Deeming]

If you're running it from Visual Studio, then it's not using SQL Agent, so that's probably not the problem. There seem to be lots of potential causes for that error message:

• Having RetainSameConnection set to True on your OLEDB source[^];
• Out-of-date metadata in the package[^];
• Having Persist Security Info=False in your connection string[^].
• Output parameters[^];
• Etc.[^];

---

"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

[amioni]

all of this properties are Ok and as i said this same package works wonders on my colleague's machine with vs 2010 i dont think it s a problem with connection string or else

[GuyThiebaut]

Always read the error message - Syntax Error, permission violation, or nonspecific Reviews another error There is either: An error in the sql - you can check this by running the sql in isolation. A permission issue - harder to track, I would test this by creating a simple SSIS package and try to run it from your code. Non specific error - eliminate the first two possibilities then look into this.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[amioni]

NB : when i make this query in Stored procedure and i call it in the oledb source it work fine but not when i make it directly

[GuyThiebaut]

I don't understand what that means - I will need more information to be able to help you.

“That which can be asserted without evidence, can be dismissed without evidence.”

― Christopher Hitchens

[jschell]

amioni wrote:

NB : when i make this query in Stored procedure and i call it in the oledb source it work fine but not when i make it directly

A user (database) can have different permissions based on direct sql versus stored procs.

[amioni]

i am working with sa user (dev pc)

[amioni]

hi, i answer myself because i found the solution: with sql server native client 10 we can't add param with subquery but this problem is resolved with SQL native client 11 (sql server 2012) thank you ;) ;) ;)