none
Not valid path executing JOB

    Question

  • Hello

    I have a problem executing a job that contains an SSIS package, which copies data from SQL SERVER to an existing Excel file. When executing the package I have no problems, the error occurs when it is executed through the JOB. I have already made the following instructions and it still does not work:

    • The JOB is executed with a proxy

    • The Excel file is in a shared folder which has all the permissions of the proxy account

    • The sql agent service is logged on as a local system

    • in SSIS package delayvalidation = true both in the Excel connection and in the data flow

    I have done all the above and the package still does not work

    The errors that appear are the following:

    Package error: SSIS error code DTS_E_OLEDBERROR OLE DB error code 0x80004005 Y:\ test.xlsx is not a valid path.

    SSIS error code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER CODE 0XC0202009

    Please help me

    Regards

    Monday, May 6, 2019 6:26 PM

Answers

  • Hi LoganTRK,

    Ok. Let's explore "...The Excel file is in a shared folder...".

    As Tom Phillips pointed out, UNC is your next thing to check.

    The UNC shared folder has the following naming convention: \\server\share\file

    You can use net use command at the command prompt to see all the file shares:

    Net Use Command

    Monday, May 6, 2019 8:21 PM

All replies

  • Hi LoganTRK,

    The error code 0x80004005 is too generic.

    • Just as a test, you can try to change MS Excel file location to a local drive to see if it is working...
    • Also, it seems that there is a space in the Y:\ test.xlsx between drive Y:\ and a file name test.xslx.
      Please try to remove it.

    Monday, May 6, 2019 7:02 PM
  • You cannot connect to mapped drives.  You need to use the full UNC path.

    Monday, May 6, 2019 7:12 PM
  • Hello Yitzhak

    Yes it works in a local unit
    The path does not have any space

    Monday, May 6, 2019 7:45 PM
  • Hi LoganTRK,

    Ok. Let's explore "...The Excel file is in a shared folder...".

    As Tom Phillips pointed out, UNC is your next thing to check.

    The UNC shared folder has the following naming convention: \\server\share\file

    You can use net use command at the command prompt to see all the file shares:

    Net Use Command

    Monday, May 6, 2019 8:21 PM
  • Hi LoganTRK,

    Ok. Let's explore "...The Excel file is in a shared folder...".

    As Tom Phillips pointed out, UNC is your next thing to check.

    The UNC shared folder has the following naming convention: \\server\share\file

    You can use net use command at the command prompt to see all the file shares:


    Thnks works now! u explain very well

    Again Thnks 

    Monday, May 6, 2019 9:20 PM