March 25, 2009 at 2:05 pm
If anyone has a valid solution, I am all ears.
Here is the issue....when you run xp_logininfo, for some AD accounts (or run a SQL job as the owner being an AD account) you get the following error message:
Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 62
Could not obtain information about Windows NT group/user 'mydomain\UserA', error code 0x5.
The OS is Server 2003 Enterprise Edition SP1. SQL Server 2005 SP2 Cummulative update package #2
UserA is an admin on the server and has SA rights in SQL Server......exact error message.
UserB is not an admin on the server and has datareader only permissions in a single db, and xp_logininfo will validate UserB just fine.
This is not a case sensitive username issue in this specific isntance, as noted on this website. I have tried every possible combination, and none of them work!
I have tried dropping the login and recreating it..exact same error message.
April 2, 2009 at 2:27 pm
Hi,
Which authentication you are using sql or windows (for you not for usera and userb) and what permissions does ur account have
Thanks
Chandra Mohan N
[font="Verdana"]Thanks
Chandra Mohan[/font]
April 2, 2009 at 4:42 pm
Both windows and SQL login....either way, for some accounts it will work and for others it won't.
April 3, 2009 at 7:49 am
I would have youe AD folks compare the two accounts - my guess is that 0x5 is an access denied message.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 3, 2009 at 6:05 pm
Well, let me throw one more factor in the mix here.....
This is on a SQL active\ passive cluster. For one physical node, it will work for some accounts...on the other node (when it is the active node) it will work for those accounts on the 1st node and on the 2nd node in addition to some accounts that would not work on the 1st node.
Any ideas???
April 3, 2009 at 6:22 pm
Scott - this makes sense only when one is checking accounts that are local server only, and only if both nodes local accounts are not the same. Since it is a cluster and is running on Domain accounts, any account that is a domain account executing xp_logininfo will return the same result whether the clustered instance resides on either physical node node.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
August 20, 2009 at 9:03 pm
I've come across a similar issue which I have found is caused by changes in the security of Windows 2008 (specifically the API calls used to perform domain lookups). Given the time that this was posted I am guessing that you could be using Windows 2008.
The scenario I found is documented in my blog.
http://matticus-au.blogspot.com/2009/08/windows-2008-and-xplogininfo.html
Matt
November 30, 2012 at 1:36 pm
This is what I have found to be true in a similar issue. Yes, this post comes many years after the original post; but I happened across this forum thread today while researching my issue.
I discovered this application event log error message reoccurring on Windows Server 2008 R2 Standard server running SQL Server 2008.
Log Name: Application
Source: MSSQLSERVER
Date: 11/30/2012 2:33:48 PM
Event ID: 28005
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: ServerName.Domain.Company.com
Description:
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\UserAccount', error code 0x5.
From query analyzer I executed the following T-SQL code and received a similar error message.
xp_logininfo 'DOMAIN\UserAccount'
Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 62
Could not obtain information about Windows NT group/user ‘DOMAIN\UserAccount’, error code 0x5.
It is standard practice at my company to run the SQL Server database engine service using a domain service/user account. It is my understanding that when the xp_loginfo command is executed, whatever account is running the database engine service is used to query Active Directory to validate the user account name supplied to the extended stored procedure xp_logininfo.
It is also standard practice at my company to organize various domain user accounts and groups into different Active Directory containers. The issue here was that the service account running the database engine service did not have permissions to read the container in which the end user account resides. An earlier post, “my guess is that 0x5 is an access denied message” is correct (according to my domain admin); but it refers to Active Directory permissions and not SQL Server permissions.
Working with my domain admin, the solution was to grant read permission (in Active Directory) on the end user account to the SQL Server database engine service account.
December 5, 2012 at 12:59 am
I've have faced the similar issue which I have found is caused by SQL service account which was locked. My SQL Service account was running under a domain account and it got locked due to certain reason and we're not informed. While querying using xp_loginfo we're getting this error. After diagnosis we came to know about account locking. Post unlocking the service account on domain issue got resolved.
Regards
Rakesh
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply