I am trying to run a DTS package via asp.net in a little example
project.

The DTS package contains a activex script.

When I run the web app on a pc with sql server installed, everything
works.

When I run the web app on a pc with msde installed, the dts package
runs, but appears to skip the activex script.

I can't get any error info out. I have tried putting in an "on error
goto" handler which writes errors to a table, but it never gets
called.

On the pc with msde installed, I can run the same exact code in a .net
windows app or vbs script and it all works fine. It only skips the dts
activex script when I run it as a web app.

Here is the really weird part. If instead of executing the package
from asp.net, I make a System.Diagnostics.Process.Start call to the
vbs file, it also fails on the computer with msde, but works on the
computer with sql server.

Is there perhaps an msde limitation on activex scripts in a dts
package? I have not heard of one...

Any help appreciated.
-Alex

I have not heard of a specific problem but you might want to investigate

http://support.microsoft.com/?kbid=207809

What do you do inside the Active Script task ?
Are you sure it "Skips" the task ?

--
--

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

"Alex Brown" <alex (AT) logic-tools (DOT) com> wrote

Hi Allan -

Thanks for your help.

I have boiled the problem down to a very simple case - the activex
script dts task simply creates a text file indicating whether or not
it ran (originally it other things, but I simplified it).

That is an interesting article. Perhaps they found it too difficult to
enforce the data transfer restriction in activex script tasks so they
simply restricted their usage? That seems pretty farfetched...

As far as knowing whether it was skipped or not, I am not really sure
how to get error detail out out of the package since it seems to be a
problem parsing the script itself. hmmn...

-Alex



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

Here is the output from the DTS Error log:

Step 'DTSStep_DTSActiveScriptTask_1' failed

Step Error Source: Microsoft Data Transformation Services (DTS)
Package
Step Error Description:ActiveX Scripting was not able to initialize
the script execution engine.
Step Error code: 800403F9
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:4500

So, I guess it was not skipping.

-Alex

Have you seen

ActiveX Scripting Initialization Error
(http://www.sqldts.com/default.aspx?224)

--
--

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

"Alex Brown" <alex (AT) logic-tools (DOT) com> wrote