One of my client was running into the below error running xp_logininfo on some of their users. It was interesting that when they run the script to capture user information it works for the same user in another domain. They asked me if there is anything specific they can look for to find out the difference between the two users in the different domains?
Msg 15404, Level 16, State 4, Server BRSQL3, Procedure xp_logininfo, Line 43
Could not obtain information about Windows NT group/user ‘INDIA\SQLGroup’, error code 0x2147.
Msg 15404, Level 16, State 4, Server VISQL3, Procedure xp_logininfo, Line 43
Could not obtain information about Windows NT group/user ‘EMEA\SQLGroup’, error code 0x2147.
I converted hex code 0x2147 to decimal (using the calculator as below)
And it was error number 8519 which means “A global group cannot have a cross-domain member.” As per the message, it seems like something to do with the type of group they were trying to add.
The error message helped them and they were able to find what was mentioned in the error message.
Below is another flavor of the error which you might see.
Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 62
Could not obtain information about Windows NT group/user ‘ASIA\SQL_svc’, error code 0x5.
The above error is generally reported in SQL Agent job failure. Notice that error code is 0x5 which is in hexadecimal. This is equivalent to decimal 5 = Access is denied.
TIP AND TRICK
You need not remember the message text. If you now any message ID for windows error, you can convert it to text using net helpmsg command.
The above can be fixed by changing the owner in job properties to ‘SA’ and it should fix 0x5 error.
Reference: Pinal Dave (http://blog.SQLAuthority.com)