From within a DTS pacakge ActiveX script I'm building a
command with a .cmd extension and then trying to execute
the command via shell.run. I've installed this successfully
on 10 servers so far without a problem. On server 11 the
process is hanging after the command file is created. When
I execute the task from within the DTS package I get the
following message in a popup: Some files can harm your
computer. If the file information below looks suspicious,
or you do not trust the source, do not open or save this
file. It then lists the file information and a warning
about malicious code. We have the option to save or open
the file. I've tried running this with domain admin
credentials.

Question 1: Is there a secure way to allow .cmd files to be
run?

Question 2: Is there a way to turn off the prompting and
make it default to 'open'?

Question 3: Is there something I can do via user/group
credentials?

I resolved the issue with the popup by changing some
security setting in IE. My script now runs until the .cmd
file is created but hangs at that point. It never executes.
This only happens when I'm running the dts via a job. If I
execute the script from within the package it works fine.

Any help or suggestions would be appreciated.
Thanks...
MA

Check the log history to see if it points to anything, also check the event
logs to see if popups were encountered. it will hang on popups if run
through a job. Also, what context is the job being run in - I mean to say,
what user is the job being executed under. Changing IE settings may only be
for you, not the context of the job user running the job.

--
Simon Worth


"MA" <anonymous (AT) discussions (DOT) microsoft.com> wrote