Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'. #65

Closed
winzig opened this issue Jan 22, 2019 · 2 comments
Labels

Comments

@winzig
Copy link

winzig commented Jan 22, 2019

Describe the Issue

I updated from 1.9.1 to 2.0.2 and then ran ssc pull, and ssc seems to get stuck after this error appears:

✖ RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'.

I reviewed the CHANGELOG and can see that SQL job info is now being stored by SSC. However, I'm using SQL Server on AWS RDS, and I suspect this is why my user doesn't have permission to access the jobs (AWS RDS handles backups and other things typically done in jobs).

I tried to figure out how to skip jobs during the processing, but failed. I thought maybe this would work in my json config file, but it didn't:

{
  "output": {
    "jobs": false
  }
}

Any recommendations?

@winzig winzig changed the title ✖ RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'. RequestError: The SELECT permission was denied on the object 'sysjobsteps', database 'msdb', schema 'dbo'. Jan 22, 2019
@justinlettau
Copy link
Owner

justinlettau commented Jan 23, 2019

@winzig Good catch! Sorry about that 😊 I just release v2.1.1 which should fix this so the following config will work:

{
  "output": {
    "jobs": false
  }
}

Let me know if you have further issues. Thanks.

@winzig
Copy link
Author

winzig commented Jan 23, 2019

Perfect, works for me now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants