locked
Execution of job 'SSIS-ExcelImporter' failed. RRS feed

  • Question

  • User-717784936 posted

    Hi All ,

    I am getting an Error

    Executed as user: Administrator\sqlservice. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:47:15 AM Error: 2015-06-01 08:47:22.88 Code: 0xC0202009 Source: Data Flow Task Excel Source [474] Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. End Error Error: 2015-06-01 08:47:22.88 Code: 0xC02020E8 Source: Data Flow Task Excel Source [474] Description: Opening a rowset for "Sheet1$" failed. Check that the object exists in the database. End Error Error: 2015-06-01 08:47:22.88 Code: 0xC004701A Source: Data Flow Task SSIS.Pipeline Description: component "Excel Source" (474) failed the pre-execute phase and returned error code 0xC02020E8. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:47:15 AM Finished: 8:47:22 AM Elapsed: 7.8 seconds. The package execution failed. The step failed.

    -I have tried setting delay validation to true

    -This user has  all privileges

    Thanks

    Monday, June 1, 2015 8:59 AM

Answers

  • User1711366110 posted


    I have tried setting delay validation to true
    -This user has  all privileges

        According to your case, The Current user account may not have the required permissions to make connections or to access resources outside the SSIS package
    So you can refer the following method to resolve this case :
       1.Create a SQL Server Agent proxy account. This proxy account must use a credential that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.

    2.This method works to decrypt secrets and satisfies the key requirements by user. However, this method may have limited success because the SSIS package user keys involve the current user and the current computer.

    3.Therefore, if you move the package to another computer, this method may still fail, even if the job step uses the correct proxy account.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, June 11, 2015 5:08 AM

All replies

  • User-2010311731 posted

    Do you have Office installed on the machine that is running this SSIS package?  If not, you will need to either install Office or the MS Access Runtime drivers.

    Matt

    Monday, June 1, 2015 10:25 AM
  • User2053451246 posted

    Do you have Office installed on the machine that is running this SSIS package?  If not, you will need to either install Office or the MS Access Runtime drivers.

    Matt

    I've never had to install Office or any drivers on the server running the SSIS package.

    For the original poster, the error is stating that there is not a worksheet called "Sheet1" in the Excel workbook you are trying to import from.

    Monday, June 1, 2015 4:13 PM
  • User-717784936 posted

    Hi Matt,

    I have  MS Access Runtime drivers installed  on machine  but still gets error

    Wednesday, June 3, 2015 5:00 AM
  • User2053451246 posted

    I have  MS Access Runtime drivers installed  on machine  but still gets error
    That still isn't related to the error you are getting.  It says it's looking for Sheet1 and it can't find it, not that it's having problems opening the file.

    Wednesday, June 3, 2015 8:53 AM
  • User1711366110 posted


    I have tried setting delay validation to true
    -This user has  all privileges

        According to your case, The Current user account may not have the required permissions to make connections or to access resources outside the SSIS package
    So you can refer the following method to resolve this case :
       1.Create a SQL Server Agent proxy account. This proxy account must use a credential that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.

    2.This method works to decrypt secrets and satisfies the key requirements by user. However, this method may have limited success because the SSIS package user keys involve the current user and the current computer.

    3.Therefore, if you move the package to another computer, this method may still fail, even if the job step uses the correct proxy account.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, June 11, 2015 5:08 AM