SQL Server Performance

Error while executing DTS Package thru Job

Discussion in 'SQL Server DTS-Related Questions' started by amitgujrathi, Apr 16, 2004.

  1. amitgujrathi New Member

    I have a DTS package, I can run this package from my Local Machine by using the Execute DTS package method as well as by using the dtsRUN command from the DOS Prompt. But I'm not able to execute it from a MS SQL Server Agent Job. It gives me the following error

    DTSRun OnError: DTSStep_DTSDataPumpTask_1, Error = -2147024893 (80070003)
    Error string: The system cannot find the path specified.

    Error source: Microsoft Data Transformation Services (DTS) Package
    Help file: sqldts80.hlp
    Help context: 1100

    Even If I try to run it from the actual SQL Server Machine's Command prompt using the dtsRUN /S <ServerName> /E /N <DTSPackageName> command, it gives me the same error.
  2. Karen New Member

    Perhaps the login that the job and/or agent runs under does not have rights to the path the job needs? Just what I would check first....

    Life is one fool thing after another whereas love is two fool things after each other.— Oscar Wilde
  3. satya Moderator

  4. CanadaDBA New Member

    I am sure if you use UNC path it will work. But if you want to use a mapped drive, then you may want to do same as what I did.

    I have a DTS package that uses a mapped drive. I could run the DTS by using execute in Enterprise manage but If I called it from application of Query Analyser, I got the path not found error. I logged in on the server itself and then mapped the path and locked the server's keyboard and monitor. Then left it that way. Now, developers are able to call and run the DTS package from within applications.
  5. satya Moderator

    Concerning drive letters vs. UNC names, I always try to use UNC names whenever possible. This gives me better portability since I don't have to worry about which machine has which drive letters mapped to what.

    I'd check to make sure that your permissions are set correctly. Remember that your scheduled job is running as the user that runs the SQLAgent service. I'd check to make sure this user can access the UNC you are referring to. Try logging into the console as your SQLAgent service account and running the job interactively.

    Satya SKJ
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page