February 9, 2011 at 1:15 pm
if i have to force each task and the package to succeed irrespective of the error how do i do it?
February 9, 2011 at 1:45 pm
It'll depend on what you're trying to do and what error(s) you're getting.
If, for example, you want the package to "succeed" even if it's unable to connect to any servers or files, that's different than if you want it to "succeed" even if a row of data has a wrong value in it.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
February 9, 2011 at 1:52 pm
I'd question WHY you want to do this.. What is the problem you are trying to solve? There are cases where you want to manage failures yourself but I haven't ever flat out said, I don't want the package to possibly fail..
CEWII
February 9, 2011 at 3:11 pm
i am getting this error on my execute sql task and i was told in this forum to try different driver but unfortunately dba can't do oledb or odbc .
execute sql task is creating table on Teradata. table gets created but i get this message.
The Execute method on the task returned error code 0x80131509 (This type has a ComVisible(false) parent in its hierarchy, therefore QueryInterface calls for IDispatch or class interfaces are disallowed.). The Execute method must succeed, and indicate the result using an "out" parameter
February 9, 2011 at 11:53 pm
Can you try setting the ForceExecutionResult property of the Execute SQL Task to Succeed?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply