I have a Windows 2012 Server running SharePoint 2010 using an SQL Server Express locally installed. Unfortunately my logs are currently flooding with message "An exception occurred while enqueueing a message in the target queue. Error: 15404, State: 19. Could not obtain information about Windows NT group/user 'DOMAIN\user', error code 0x5." It can be 20 such messages every second!
(...and the 'DOMAIN\user' happens to be my personal account.)
Are there a job running that has missing rights? "Qoute from https://serverfault.com/questions/277551/mssqlserver-exception-occurred-while-enqueueing-a-message-in-the-target-queue-e "Try to changing the owner of the jobs to the sa account, on the properties of the job." If I'm correct the express version of SQL server cannot run jobs? Or is there someone/something that wants access to our AD? Why do that account wants to obtain information about my account 20 times every second?
I do find lot's of blogs and hints about this task, but I just dont understand the solutions. One says "To repair this, login as one of the SA accounts and grant SA access for the account that needs it." But what account needs sa access?
The most likely cause for this is a misconfiguration of the service account settings in SQL Server. To be more specific, it is very likely that SQL Server is configured to run as a local user who has no access to Active Directory at all.
Error 0x5 means access denied. Try to changing the owner of the jobs to the sa account, on the properties of the job. If the above does no help, please change the service account for the SQL Server agent service to account with proper permissions. Hope this helps.
Could not obtain information about Windows NT group/user 'domainuser', error code 0x5. [SQLSTATE 42000] (Error 15404) (ConnIsLoginSysAdmin) The solution to this is to add the SQL Server service account to the 'BUILTINWindows Authorization Access Group' on your DC.
Change the owner to sa
. Here are the steps I took to solve this issue:
Right-Click on the database and select properties
Click on Files under the Select a page
Under the Owner
, but just below the Database Name on the right-hand pane, select sa
as the owner.
In my case, sa
was not the owner of the DB, I was. When I tried to execute CLR configuration that required sa
privileges, I got the error too.
The solution:
USE MyDB GO ALTER DATABASE MyDB set TRUSTWORTHY ON; GO EXEC dbo.sp_changedbowner @loginame = N'sa', @map = false GO sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'clr enabled', 1; GO RECONFIGURE; GO
I used help from the db team at work and this post to find the answer. Hope it helps.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With