Hi All,

I finally finished my project in DTS running it manually about 9 billion
times through many test scenarios... :-)

Anyway, here's my issue... When I schedule the job it is failing to run on
a creatobject line... permissons???

Any thoughts? Please please please! :-))))

Travis

It depends - failing on create what object? If it's your own
component, maybe it hasn't been registered on the server.

-Sue

On Thu, 18 Sep 2003 14:49:50 -0700, "REM7600"
<rem7600 (AT) hotmail (DOT) com> wrote:

Further to Sue's comments. We would need to know what it cannot
create. If it is an instance of a DTS package then we probably need to
reregister the DTS dlls. Usually when you can use DTS manually and not
when scheduled then this is the problem

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


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

Sue and Allan...

The package runs fine when manually run even on the server or run manually
on my workstation. When run as a job it fails. I agree that it is security
related and am doing my best to sift through the document Allan mentioned.
The object I am creating is an FTP object. I ran the setup program on the
server for the control.

' this is a custom FTP control that gives fairly clean FTP functionality
within VBScript
' setup FTP Wizard object
set FTPWizard1 = CreateObject("FTPWizard.FTPWizardCtrl2")

I really hope to be able to make this work as the package would "come
together" nicely...

Travis


"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote

You can easily prove then the security issues

Go to the server
Log in as the SQL Server Agent Account
Now execute your package



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

Allan is this the account used to start the SQL Server Agent Service? And
by EXECUTE you mean run the job, correct?

Thanks for all the help!

Travis

Correct




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

tested and still failed... This "ain't lookin' good" so to speak...

I'm testing with a VERY basic ActiveX Script example and it fails to
instantiate the object when scheduled. Works fine when run manually at the
server console.

ARRRGGGGHHHHHHHHH! Another $200 down the drain on an ActiveX for FTPing
that won't QUITE get the job done. Perhaps I'll just start staying around
the clock manually running the routine every 2 minutes! Whatdya think? :-(

TR

Maybe there is something stored in the user profile for the
component - you try rerunning setup logging onto the server
using the service account for SQL Server Agent and install
it under that user. You could also try reregistering.
Possibly there may be some info in the event logs on the
server that could have some info. Maybe not...just something
to check.

-Sue

On Fri, 19 Sep 2003 10:06:40 -0700, "REM7600"
<rem7600 (AT) hotmail (DOT) com> wrote:

I would give Sue's idea a go. I once saw this with some AS400 drivers.
They would only work if the person who installed them ran the
package/load.


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