(execute slot single)500000 re-throw in Procedure errors in system journal

Who did you run the commands with to reset the queue as per the KB you mentioned? Basically the error means that when the SQL agents got recreated it was with an account that is not the owner of the Identity Manager database.

Good catch, when we have a chance we'll re-run it with the appropriate service account. Thanks!

Hi Aszeto

We are facing the same problem. Can you please tell me if you were able to handle it and, in case, how?

Thanks in advance

Alberto

Hi,

If you run the exec commands to recycle the DBQ slots (SQL Agent jobs) you must run those commands as the same account that is the owner of the One Identity database.

If you have the issue then check who is the owner of the database and check who is the owner of the SQL Server Agent jobs - if they don't match then you need to fix it.

HTH, Barry.

Hi Barry

I did it with the owner of the db and yes, the owner of the db is the owner of the Server Agent Job. Just checked.

But the problem is still there.

Any more advices, please?

Thank you

A

Are you sure having the same error message or just a similar one?

I copy-paste:

(execute slot single)50000 0 re-throw in Procedure QBM_ZUpdateStatistics, Line 415247 0 detected in (SRV=XXXXXXXX, DB=YYYYYY) Procedure sp_updatestats, Line 1515247 0 User does not have permission to perform this action.

So then, as Barry said, you must check that the user, the SQL Agent Jobs are using, are the owner of the OneIM database. in addition, check the permissions of the owner itself. If you are using the granular permission model of OneIM, the user needs to have the permission of the Installation User type.

Also, have you tried running 'exec sp_updatestats' in Server Studio as the db owner account?  Do you get the same error - or a more informative error?  As Markus Weiss-Ehlers suggests ..... it feels like your account does not have the correct permissions.

Markus, Barry

Thank you for your support.

Let me answer your suggestions:

1. I checked ALL the SQL Server Agent – Jobs. All of them have the same owner that is the owner of the OIM database
2. I run the ‘exec sp_updatestats' and it seems everything is ok (I had no errors back)

I didn’t specify in the previous comms, but the logon user is “QBM_PDBQueueRunner”

Markus, there are a couple of thinks I cannot understand:

1. “check the permissions of the owner itself.” à You want me to check the permission of the db owner?  Where – which permissions?
2. If you are using the granular permission model of OneIM, the user needs to have the permission of the Installation User type. à I don’t think we are using the granular permission model of OneIM. How can I verify it?

Thank you both

A

The owner of the SQL Agent task is "QBM_PDBQueueRunner"? This is no user we are creating during the setup.

And according to Microsoft (https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-updatestats-transact-sql?f1url=https%3A%2F%2Fmsdn.microsoft.com%2Fquery%2Fdev15.query%3FappId%3DDev15IDEF1%26l%3DEN-US%26k%3Dk(sp_updatestats_TSQL)%3Bk(sql13.swb.tsqlresults.f1)%3Bk(sql13.swb.tsqlquery.f1)%3Bk(MiscellaneousFilesProject)%3Bk(DevLang-TSQL)%26rd%3Dtrue&view=sql-server-2017#permissions )

To run sp_updatestats, the user must be the owner of the database (the dbo, not just member of the role db_owner) or to be member of the sysadmin fixed server role.

Markus,

of course the owner of DB is not QBM_PDBQueueRunner.

QBM_PDBQueueRunner is the value of the column DialogJournal.LogonUser ( I did not specified in previous replies, so I thought it could be interesting to know for you)

The owner of the DB is, let’s say, xxxxxxxx, that is also the owner of the SQL Server Agent Jobs.

When I log in with that user, I can run the  'exec sp_updatestats’ without having problems.

Markus,

of course the owner of DB is not QBM_PDBQueueRunner.

QBM_PDBQueueRunner is the value of the column DialogJournal.LogonUser ( I did not specified in previous replies, so I thought it could be interesting to know for you)

The owner of the DB is, let’s say, xxxxxxxx, that is also the owner of the SQL Server Agent Jobs.

When I log in with that user, I can run the  'exec sp_updatestats’ without having problems.

This is all I can do in this community. I think it is time to contact support then.