Greetings,

I have a VB6 custom task that calls another process via a custom written C++
Dll who's purpose it is to spawn and control another app by grabbing its std
handles.
The C++ Dll exists as an ActiveX control withinn the VB project and it all
works perfectly until the task is executed by the SQL scheduler.
Does anyone know the rules of execution within the scheduler Vs the
designer?
I have read every post as well as the MS KB articles and understand their
content.
My gut feel is that it lies within the threading model and how DTSRun.exe
does its work.

The result is that both CPU and memory hit max for about 5 secs, then it
terminates with an ACCESS_VIOLATION error. Also, the contents of the spawned
stdio pipe is in the DTS log, very scary.

Any comments appreciated.

Regards,

Greg King
MCSE

Do you execute the Custom task on the main package thread and also any tasks
that touch it ?

--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Greg" <gpmk (AT) yahoo (DOT) com> wrote

Thanks for the reply.

The package has just one task (the custom task) and it is set to execute on
the main package thread.
Is there another place to change that setting? I have done it by right
clicking the task choosing workflow properties.

Greg.



"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Nope that's the one

--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Greg" <gpmk (AT) yahoo (DOT) com> wrote