Fixing ‘A required Privilege is not held by client’ Error

Question

Post reply

Fixing ‘A required Privilege is not held by client’ Error

VishnuGupthanSQLPowershellDBA

Ten Centuries

Points: 1230
More actions
July 16, 2018 at 12:01 am

#366286

Comments posted to this topic are about the item Fixing ‘A required Privilege is not held by client’ Error
Vishnu Gupthan
PowershellAcademy
www.powershellacademy.com

Viewing 9 posts - 1 through 8 (of 8 total)

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

SoHelpMeCodd SSCertifiable Points: 5871 More actions · Answer 1

'A required Privilege is not held by client' is raised in a variety of scenarios.
As a proactive measure you should also use the SQL Server documentation's Configure Windows Service Accounts and Permissions URL (change SQL Server version on that page, if needed) to verify and align your SQL Server system with that URL's "Windows Privileges and Rights" section, for all of your system's installed service accounts (identified in that section). That verification and alignment is especially important when at least one advanced privilege or right is found to be missing. Otherwise it is possible for your SQL Server system to experience additional, unexpected, 'A required Privilege is not held by client' errors in the future.

jasona.work SSC Guru Points: 50117 More actions · Answer 2

I have one question that isn't answered in your article, when were the Windows patches that were installed pushed out to your servers? Were they from the most recent "Patch Tuesday" of 10-July-2018?

VishnuGupthanSQLPowershellDBA Ten Centuries Points: 1230 More actions · Answer 3

Hi Jasona,
Not pretty sure about the exact patch date but it was noticed post May it seems.
Vishnu

Vishnu Gupthan
PowershellAcademy
www.powershellacademy.com

jasona.work SSC Guru Points: 50117 More actions · Answer 4

VishnuGupthanSQLPowershellDBA - Monday, July 16, 2018 8:15 AM
Hi Jasona,
Not pretty sure about the exact patch date but it was noticed post May it seems.
Vishnu

OK, thank you for the info. I was concerned it might've been the most recent updates, in which case I'd need to be cautious (more than usual) this month.

sterling3721 SSChasing Mays Points: 658 More actions · Answer 5

I encountered Scenario #2 last April after GPO rollout by another team and did the same by adding "Replace a Process Level Token" to SQL Server Service Account.

paultormey Mr or Mrs. 500 Points: 573 More actions · Answer 6

Yep...getting the Policy "Replace a process level token" updated with the account that the SQL Server Service is running under definitely fixed the problem.

Now able to deploy SSISDB projects to the server.

gmwmn SSC Journeyman Points: 92 More actions · Answer 7

Took me a couple of days to finally find this article and the fix in Scenario 2 but it worked for me!!

VishnuGupthanSQLPowershellDBA Ten Centuries Points: 1230 More actions · Answer 8

Glad to know that it worked well for you.

Vishnu Gupthan

http://www.powershell4u.com

Vishnu Gupthan
PowershellAcademy
www.powershellacademy.com