Post reply

Unable to execute JOB (SSIS package)

  • December 3, 2016 at 10:37 am

    #315563

    Hi,

    I'm trying to run a JOB which should execute an SSIS package. Unfortunately, I landed up on multiple errors stating "Dimension Processing: Error: Either the user. NT SERVICE \SQLSERVERAGENT. does not have access to the OLAP database. or the database does not exist." Also, I've attached the two different error screenshots. Need your help lads.

  • December 3, 2016 at 11:35 am

    #1915903

    badalkataria (12/3/2016)

    Hi,

    I'm trying to run a JOB which should execute an SSIS package. Unfortunately, I landed up on multiple errors stating "Dimension Processing: Error: Either the user. NT SERVICE \SQLSERVERAGENT. does not have access to the OLAP database. or the database does not exist." Also, I've attached the two different error screenshots. Need your help lads.

    I'm thinking that the error describes the exact problem correctly. Does the login for the SQL Agent actually have any privs to wherever the SSIS package is?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • December 3, 2016 at 11:40 am

    #1915904

    How would I able to figure out that if it is or not?

  • December 3, 2016 at 2:49 pm

    #1915907

    badalkataria (12/3/2016)

    How would I able to figure out that if it is or not?

    You have more than one problem going on here. One is regarding access to an Excel spreadsheet ... perhaps someone has it open for editing and that is blocking access from SSIS.

    Secondly, it seems that the package is trying to access a SSAS cube as user NT SERVICE \SQLSERVERAGENT, and that this is failing. Presumably because that user does not have access to the cube ... you may need to speak to your DBA about that.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply