InstantForum.NET v4.1.4SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 21 Nov 2009 23:54:07 GMT20http://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxJust something I have found in my own situation.This is more likely to be caused by changes in Windows 2008 rather than any changes to SQL server. My scenario is documented in my blog[url=http://matticus-au.blogspot.com/2009/08/windows-2008-and-xplogininfo.html]http://matticus-au.blogspot.com/2009/08/windows-2008-and-xplogininfo.html[/url]Hope this helps someone else who comes across similar issues in the future.MattThu, 20 Aug 2009 21:05:13 GMTMatt Laveryhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxAwesome. Thanks so much, Simon. Really appreciate the information and the quick response. I'll get my my AD admin and give it a try...Thanks again...- KenTue, 30 Jun 2009 20:25:35 GMTKen.L.Wolffhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxYes we did.I don't remember how :) Give me a few hours to chase up the details. I remember it ended up being a PSS fix which was nice to have them help. Oh I remembered the PSS persons name and found the steps she recommended:I suggest that you try to implement the below changes in AD:1. Add the SQL service account (SVCNS02IS0V001SQL) into the Windows Authorization Access groupTo add the SQL service account into the Windows Authorization Access group, do as follows:- Open ADUC (Active Directory Users and Computers) console on a domain controller which hosts the user account - SVCNS02IS0V001AGT.- Go to the Builtin container. Find Windows Authorization Access Group- Open its properties. Under the Members tab, add the SQL service account into the list.- Apply the changes.- Restart the SQL service to re-logon the SQL service account.- Check if the issue persists. 2. Also, confirm if the SVCNS02IS0V001SQL service account has at least Read permission on the user account object (SVCNS02IS0V001AGT) for this attribute: Read tokenGroupsGlobalAndUniversalTue, 30 Jun 2009 14:50:18 GMTSimon Larsenhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxSimon - were you ever able to resolve this? I'm encountering the same problem and would love to know the solution, if there is one.Thank you.- KenTue, 30 Jun 2009 09:02:36 GMTKen.L.Wolffhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxThe agent is part of the domain (it is a clustered instance).The agent gains access via the domain group SQL_Agent.Note that my account (which works fine) is a member of the DBA domain group (almost identical to the above group).I have tried putting the agent into the DBA group with no success.Wed, 03 Dec 2008 11:25:56 GMTSimon Larsenhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxIs the agent account part of the domain, or is it a local account on the server?Wed, 03 Dec 2008 09:22:53 GMTGSquaredhttp://www.sqlservercentral.com/Forums/Topic612567-149-1.aspxSQL 2005, Windows 2008 clusteredwhen I run xp_logininfo I get the list of all the accounts.when I run xp_logininfo 'domain\agentaccount'I get Could not obtain information about Windows NT group / user error code 0x5I also find in the server security log that the SQL service account has failed to login.SQL and the agent are both running fine.xp_logininfo sql service accountworks fine.The source of the problem was a db_mail which has a query attached. Works fine for my windows account and others but not for the agent.Tue, 02 Dec 2008 22:10:11 GMTSimon Larsen