I seem to be getting an EXCEPTION_VIOLATION_ERROR
everytime I use a Dynamic task to Edit a Cube Task
Property (Fact, Filter and TreeKey). This error does not
happen if I execute the dynamic task alone. This only
happens when I execute the package as a whole?

This brings up the question does the cube task lock it's
properties for editing whenever the package is processed?
I looked up the BI Accelerator packages and saw some
something exactly similar. How come BI Accelerator can do
this and I cant?

Thank You.

Set the Dynamci Properties Task to execute on main thread. Right click teh
task, select workflow properties, options.

The OLAP task is written IN VB so sufferes from thread issues, and you must
ensure all other tasks that touch it must also match, hence setting the
option.


--
Darren Green
http://www.sqldts.com

"Joseph Ollero" <Jollero21 (AT) wizardsgroup (DOT) com> wrote

I didnt know the dynamic task was created with vb. Thanks
for the help Mr. Darren Green. Much appreciated.

In message <ff9e01c43ee3$6fb83ce0$a301280a (AT) phx (DOT) gbl>, Joseph Ollero
<jollero21 (AT) yahoo (DOT) com> writes
To clarify, The OLAP task is written in VB, not the Dynamic Properties
Task. The designer will automatically set the OLAP Task to run on the
main thread, which is required, but since you wish to "touch" the OLAP
task with the Dynamic Properties it also needs to be on the main thread.
So, because the OLAP task is and must be on the main thread, and VB
means it is not aware of other threads, you cannot reach across to the
main thread from another, hence both tasks must be on the main thread.
That reach across analogy is probably over simplified, but how I
rationalise it to myself.


--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

Hi Joseph.

I've found that if you mark the "Execute on main package thread" workflow property in the Dynamic Task, this error doesn't appear anymore.
I've also removed the task from the main workflow path, and put it as stand alone task in the package.
You can find the check "Execute on main package thread" in the workflow --> workflow properties menu, on "options" tag.
I just edited the "TreeKey" property, but I think that it will work for the rest of them too.

It worked for me, hope that helps you too.

Good luck.

************************************************** ********************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...