Post reply

Package deployment error

  • September 25, 2019 at 1:24 pm

    #3683299

    When I try to deploy SSIS package using package deployment, I am getting the error message below:

    TITLE: SQL Server Integration Services

    ------------------------------

    The SELECT permission was denied on the object 'projects', database 'SSISDB', schema 'catalog'. (Microsoft SQL Server, Error: 229)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=13.00.1601&EvtSrc=MSSQLServer&EvtID=229&LinkId=20476

    ------------------------------

    BUTTONS:

    OK

    ------------------------------

     

    But I am able to query the following in SSMS,  "SELECT * FROM SSISDB.CATALOG.projects".

    What is the reason for this package deployment error?

  • September 25, 2019 at 1:52 pm

    #3683310

    Are you sysadmin on the instance?

    Are you logged in using Windows Auth?

    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.

  • September 25, 2019 at 2:18 pm

    #3683323

    I am the Sysadmin in the instance & I am using sa login using SQL Authentication.

    This login also allows me to create a folder under the SSIS catalog, a feature which is restricted to Windows Authentication.

  • September 25, 2019 at 2:22 pm

    #3683326

    I've seen plenty of issues in the past in SSIS when using SQL Authentication.

    Are you able to log in with sysadmin rights using Windows authentication & try again?

    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.

  • September 27, 2019 at 10:35 am

    #3683932

    How to set sysadmin rights for my Windows authentication ?? Kindly guide me on this.

  • September 27, 2019 at 2:06 pm

    #3684044

    1. Create the login:

    CREATE LOGIN [domain\ntuser] FROM WINDOWS

    2. Add the login to the sysadmin server role

    ALTER SERVER ROLE [sysadmin] ADD MEMBER [domain\ntuser]

    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 6 posts - 1 through 5 (of 5 total)

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