Could not obtain information about Windows NT group/user .......error code 0x534...
-
lundi 10 juillet 2006 18:53
== I asked this question directly to Remus and wanted to share the response to all of those people using this forum ==
We recently moved our database server from SQL Server 2000 to SQL Server 2005. All applications on our intranet development server stay the same [VS.NET 2003], but recently resources in our Dev DB server ran out of space. While doing a thorough investigation, I noticed ERRORLOG file was occupying about 35 Gig of HDD space. I immediately checked SQL Server error log and noticed an entry which says –
===========================================================================================
Date 7/7/2006 4:45:37 PM
Log SQL Server (Current - 7/7/2006 4:45:00 PM)
Source spid77s
Message
The activated proc [dbo].[SqlQueryNotificationStoredProcedure-5eaf8465-d0cb-4be7-93b6-44bb979dd41c] running on queue BW_Content.dbo.SqlQueryNotificationService-5eaf8465-d0cb-4be7-93b6-44bb979dd41c output the following: 'Could not obtain information about Windows NT group/user 'BWCINC\HoffK', error code 0x534.'
===========================================================================================
What is this SqlQueryNotificationService in my database? Is it a SQL Server 2005 thing? Why the same kind of stored procedure does not exist in other databases, but BW_Content? This error is getting repeated most probably every second and is filling up our server.
I believe our corporate IT people removed our domain accounts from BWCINC domain to BWCORP domain and probably some application which is using BWCINC\HoffK credential is getting errored out. I tried to locate this application and was not successful.
Is there anyway that I can stop this ERRORLOG from growing? How can I delete these log entries so that I can make space on our Hard Drive? Is there an easy way in SQL Server 2005 to locate which application is creating this error?
Response from Remus:
The 'SqlQueryNotificationService-...' is the service created by SqlDependency when you call SqlDependency.Start (). The problem you describe appears because the 'dbo' user of the database is mapped to the login that originally created this database. The SqlDependency created queue has an EXECUTE AS OWNER clause, owner is 'dbo' and therefore this is equivalent to an EXECUTE AS USER = 'dbo'. The error you see is reported by the domain controller when asked to give information about the original account 'dbo' mapps to (that is, BWCINC\HoffK'): Error code: (Win32) 0x534 (1332) - No mapping between account names and security IDs was done.To solve the issue, change 'dbo' to match a correct login, using either sp_changedbowner or ALTER AUTHORIZATION ON DATABASE::[dbname] TO [somavalidlogin]To find the databases that have this problem, run this query:select
name, suser_sname(owner_sid) from sys.databasesThe databses that have the problem will show NULL on the second column.A similar problem is described here: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=65711&SiteID=1To remove the entries, use sp_cycle_errorlog to force a new errorlog file, then delete the huge log file.---------------------------------------I executed ALTER AUTHORIZATION ON DATABASE::[BW_Content] TO [sa];I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.===============================================================Date 7/10/2006 1:16:55 PM
Log SQL Server (Current - 7/10/2006 1:17:00 PM)Source spid20sMessage
The query notification dialog on conversation handle '{6BDE95F7-0EFB-DA11-9064-000C2921B41B}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-c15bb868-ed56-47d2-bf91-ce18b320989a' because it does not exist.</Description></Error>'.===============================================================Should I be concerned about this error?Thanks-Binoy
Toutes les réponses
-
lundi 10 juillet 2006 19:53ModérateurThanks for sharing this!
-
lundi 10 juillet 2006 19:56Modérateur
Binoy Sankar wrote: I got this error in SQL Error Log once and the growth of ERRORLOG was stopped.===============================================================Date 7/10/2006 1:16:55 PM
Log SQL Server (Current - 7/10/2006 1:17:00 PM)Source spid20sMessage
The query notification dialog on conversation handle '{6BDE95F7-0EFB-DA11-9064-000C2921B41B}.' closed due to the following error: '<?xml version="1.0"?><Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8490</Code><Description>Cannot find the remote service 'SqlQueryNotificationService-c15bb868-ed56-47d2-bf91-ce18b320989a' because it does not exist.</Description></Error>'.===============================================================Should I be concerned about this error?Don't worry abouyt it. The error means that the client disconnected and the temporary service was dropped before the notification was fired.Thanks,~ Remus
I seem to be having a simliar issue but can't get it resolved by suggestions I have found on the net.
Basically I am running a SQL Server on a Domain that uses windows authentication.
The Instance is started up under "localsystem" and the database owner is "sa".
I still get a large amounts of errors like this one every 5 seconds.
"The activated proc [DOMAIN\user].[SqlQueryNotificationStoredProcedure-d4dcc6af-2241-4bbe-8b17-ac110cd9065a] running on queue MetaDB.DOMAIN\user.SqlQueryNotificationService-d4dcc6af-2241-4bbe-8b17-ac110cd9065a output the following: 'Could not obtain information about Windows NT group/user 'DOMAIN\user', error code 0x5."
Is there anything that I am missing for authentication.
- Proposé comme réponse MarcosLeRosa vendredi 10 août 2012 14:09
Thanks for the info,
In a high security environment, would it then be better to use a Domain User athe the service account and if so what access would be needed to be applied to the account to allow the querying of the Domain?
Normally a domain account wouldn't require anything special in the AD to be able to interogate it.
At the moment I am running it as "LocalSystem", I have also tried as "NetworkService"
I have also tried to run it under my domain userid that is part of "Domain Users" so I am a bit confused as to why I would be getting No access errors.
Other than setting the Owner of the database to "sa" is there anything else needed on the database side that needs to be set.
- Proposé comme réponse Edwin Chan jeudi 12 janvier 2012 03:39
- Non proposé comme réponse Edwin Chan jeudi 12 janvier 2012 03:39
I have noticed that there are about 40 stored procedures named [DOMAIN\user].[SqlQueryNotificationStoredProcedure-(guid)].
Should there be so many, what generates them and when do they get cleaned up. Is there any way of manually cleaning them up.
Remus,
With further investigations it seems that there are a number of these notifications that have been "Orphaned" and have not been removed out of the system.
Is there any way to clear the Procedures, Services and Queues that have been "Orphaned".
Hi all,
We had the same problem, but in our case all problems start when the customer change the server name, several job became broken.
The major problem was found when we run a job that send a server report every day throught email. When started sp_send_dbmail proc we receive the message "Error formatting query, probably invalid parameters", but if the same code is executed in a query window it is executed successful.
To solve the problem I put an "EXECUTE AS LOGIN = 'WindowsLoginName' " before the sp_send_dbmail.
This "WindowsLoginName" is a sysadmin.
Best Regards,
Alexandre Von Mühlen
MCSE/MCT/MCDBA/MCITP:DBAdmin SQL Server 2005 / 2008
Classifiquem as respostas. O Fórum agradece!! This posting is provided "AS IS" with no warranties, and confers no rights.
Hello Binoy and all,
thanks for solution. Changed owner to 'sa', and it works!
Just want to add for googlers that this solution in my case also resolved the error when System Center Essentials 2010 ( SCE 2010 ) and possibly earlier versions hang indefinetily on "Discovery is in progress" when trying to discover computers on the network.
Best regards
Andrzej
Marcos Leandro Rosa
I came across the same problem when I installed SCOM 2012 SP1 and discovery process was running forever. I found the error code in even viewer
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\ScomDa', error code 0x5.
That is the permission issue problem and I resolved it to add user to sysadmin role. You can follow the below steps to do it
1. Run SQL Server Management Studio
2. Connect to server with 'sa' or owner of the server
3. Under Security -> Logins find the user; in my case Domain\ScomDa
4. Select the user, right click and select properties
5. on Login Properties select Server Roles tab
6. Under server roles select sysadmin.
7. Restart SQL service, SQL Agent Service and Reporting and Analysis services if installed.
It will fix SCOM discovery problem as well as eliminate the error message.
Thanks.
- Modifié -IK mercredi 15 mai 2013 00:42

