Results 1 to 3 of 3
  1. #1
    Join Date
    Apr 2004
    Posts
    7

    Unanswered: DTS execute works, Schedule fails

    Hey all,

    I have created a DTS task that i can right click on and execute and it works fine on the server.
    However when i try to schedule the task and run the job from SQL Server Agent, i get the following error.

    Error Source= Microsoft VBScript runtime error Error Description: ActiveX component can't create object: 'CuteFTPPro.TEConnection' Error on Line 31

    the error occurs on the following line
    Set MySite = CreateObject("CuteFTPPro.TEConnection")

    How is it possible that i can execute my package but cannot schedule it? i am executing the package from physically sitting at the server.

    thanks in advance,
    pete

  2. #2
    Join Date
    Nov 2002
    Location
    Jersey
    Posts
    10,322
    I'd say it's gotta be permissions...

    When you run a dts package manually, it runs under the context of the client...

    When scheduled it runs under the context of the sql server service account...

    Also the same thing with the drive mappings

    When you run it, it uses yours...

    when scheduled it sees the servers drive

    screwed up, huh...
    Brett
    8-)

    It's a Great Day for America everybody!

    dbforums Yak CorralRadio 'Rita
    dbForums Member List
    I'm Good Once as I ever was

    The physical order of data in a database has no meaning.

  3. #3
    Join Date
    Apr 2004
    Posts
    7
    when i was running it manually i was sitting at the server so wouldnt it be running in the context of the server???

    the scheduled task is run by the /MYSERVER/SYSTEM user... shouldnt that user have all permissions.

    how do i change permissions for the user /MYSERVER/SYSTEM if it doesnt have all permissions.

    thanks,
    peter

    Originally posted by Brett Kaiser
    I'd say it's gotta be permissions...

    When you run a dts package manually, it runs under the context of the client...

    When scheduled it runs under the context of the sql server service account...

    Also the same thing with the drive mappings

    When you run it, it uses yours...

    when scheduled it sees the servers drive

    screwed up, huh...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •