Error Code 0x6ba Sqlstate 42000
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting errorcode 1064 sqlstate 42000 ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join errorcode 942 sqlstate 42000 the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a errorcode 904 sqlstate 42000 minute: Sign up Could not obtain information about Windows NT group user up vote 20 down vote favorite 2 I am creating a SQL Server Replication using a script. When I try to execute The job failed. Unable to determine errorcode 936 sqlstate 42000 if the owner (STAR\moorer7) of job L3BPT2M-Atlas-14 has server access (reason: Could not obtain information about Windows NT group/user 'STAR\moorer7', error code 0x5. [SQLSTATE 42000] (Error 15404)). This is a job created by a script that defines replication. How do I debug this? sql sql-server replication sql-server-agent share|improve this question edited Feb 18 '11 at 1:09 asked Aug 5 '09 at 17:13 Raj More 29.8k1786155 I changed the owner in job properties to 'sa' then the issue solved. –Alex Aug
Error Code 1064 Sql State 42000
13 at 7:25 add a comment| 7 Answers 7 active oldest votes up vote 30 down vote accepted Active Directory is refusing access to your SQL Agent. The Agent should be running under an account that is recognized by STAR domain controller. share|improve this answer edited Mar 24 '14 at 20:20 atticae 5,29263890 answered Aug 5 '09 at 17:30 Remus Rusanu 206k25268405 @Remus Rusanu:The agent is running under a local machine account as MyWorkstation\SqlServerAccount –Raj More Aug 5 '09 at 17:58 8 @Raj: Actually since is the SQL Server itself that is connecting to the AD, you need to change the account under which SQL is running. It has to be an account AD will authenticate, like a domain account or the NETWORK SERVICE account(provided the machine is joined to the domain). SSMS or EM can have an option to change the service account. –Remus Rusanu Aug 5 '09 at 19:09 2 +1 for keeping me from having to talk to my dba (several hours saved) –DancesWithBamboo Sep 30 '11 at 18:02 1 Brent Ozar recommends (with caution of course) that SQL Server Agent Jobs be owned by SA, because the owner doesn't really matter to how the job functions, until it fails due to the owner being dropped or non-authenticated. See here: brentozar.com/blitz/jobs-owned-by-user-accounts . A service account is the next best thing, as long as you have it configured right and it's never at risk of being lock
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login
Sql State 42000 Sql Error Code 8180
Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts translating sqlexception with sql state 42000 error code 1064 Exchange > Questions > Error executing job while sql srvr agent runs under local win account Want to Advertise Here? Solved Error executing could not obtain information about windows nt group/user error code 0x5 job while sql srvr agent runs under local win account Posted on 2010-03-28 MS SQL Server 2008 MS SQL Server 2005 2 Verified Solutions 5 Comments 1,353 Views Last Modified: 2012-05-09 Hi, I'm facing this problem on one of http://stackoverflow.com/questions/1234570/could-not-obtain-information-about-windows-nt-group-user my test box running SQL server 2008. I don't think this is related to SQL version but instead permissions... I created a simple backup job and it fails if it runs under my domain account with following error: The job failed. Unable to determine if the owner (domain\user) of job test_bak has server access (reason: Could not obtain information about Windows NT group/user 'domain\user', error code 0x6ba. [SQLSTATE 42000] (Error 15404)). If I change the owner of the https://www.experts-exchange.com/questions/25573942/Error-executing-job-while-sql-srvr-agent-runs-under-local-win-account.html job to "SA", it runs fine. SQL server agent is running under a local user account on the server and has SA rights on SQL server. I tried making this account member of windows administrators group but still the same error comes. I then changed the sql agent account to run under my domain account and then change the owner of the job back to my domain account this time job runs fine. So what is about this local user account under which sql agent is running causing this issue? 0 Question by:Rainbow002 Facebook Twitter LinkedIn Google LVL 142 Active today Best Solution byGuy Hengel [angelIII / a3] >I then changed the sql agent account to run under my domain account and then change the owner of the job back to my domain account this time job runs fine. exactly. if you just specify the job owner Go to Solution 5 Comments LVL 142 Overall: Level 142 MS SQL Server 2005 60 MS SQL Server 2008 38 Message Active today Accepted Solution by:Guy Hengel [angelIII / a3]2010-03-28 >I then changed the sql agent account to run under my domain account and then change the owner of the job back to my domain account this time job runs fine. exactly. if you just specify the job owner to be the windows account, the job system (sql agent) cannot verify the cred
to be PC to PC doing updates, now WSUS does it all New Practice Build Out Planning, and build out of a new Dental Practice. ClaimX Server Migration Migrate Claimx Server from old terminal server https://community.spiceworks.com/topic/29931-could-not-obtain-information-about-windows-nt-group-user to a new dedicated server. TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Suddenly, and for no apparent reason, our 2005 SQL servers will not run automated jobs. It appears as though we have a domain controller issue yet everyone can login just fine and rights are working correclty. Every automated SQL job, regardless of the machine, gets the following: Sql Message ID: 0 Message: The state 42000 job failed. Unable to determine if the owner (MYDOMAIN\administrator) of job SQL1\dnc-DNCSnapshot-2 has server access (reason: Could not obtain information about Windows NT group/user 'MYDOMAIN\administrator', error code 0x5. [SQLSTATE 42000] (Error 15404)). This occurs no matter which login we use (in the example we tried using the administrator login but we were not before that). I've scoured the internet and Microsoft's sites looking for any info and though I've found a lot of sql state 42000 other folks having similar issues, I have been unable to locate any definitive answer as to what might be wrong. This started about 3 weeks ago but was only sporadic. For the last 3 days it's been constant. Even our 2005 web servers are having authentication issues! I've combed the logs of both domain controllers to no avail. I've tried restarting both domain controllers. Nothing we do will seem to fix this problem. Would greatly appreciate it if anyone has some suggestions, particularly if you've experienced this problem yourself. Thanks in advance! Reply Subscribe View Best Answer RELATED TOPICS: If I was an IT Guy I would..... sigh....... Failed to Renew IP address for Virtual Adapter - Sonicwall VPN client Issues? 2 Replies Datil OP Best Answer Javier Odom Jan 5, 2009 at 11:29 UTC Greetings. I have not seen this particular issue, but some thoughts on the matter... bounce (stop and restart) the SQL services Verify the service account being used. create a low-level AD account, perhaps called SQLService ... just a plain member of the domain, and try using that as the login. Set the password to not expire, and so the user cannot change it. If it does not work, do not forget to remove the low-level (SQLService) account. http://social.msdn.microsoft.com/forums/en-US/sqlreplication/thread/c6c