Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1028
  • Last Modified:

After Domain Migration, SQL Job Failes to authenticate user. SQL state 42000 Error 8198

We migrated a windows 2000 server from an nt4 domain to a full 2003 domain. Afterwards we cannot run jobs under a sql service account. All the sql services are running fine under this account, but we can't run jobs under this account. This account works with other sql servers that were migrated.


The job failed:unable to determine if the owner (blah\blah) of job Test1 has server access(reason:could not obtain information about windows NT group user 'blah\blah')
SQL state 42000 Error 8198


I've seen alot of posts saying to change the user that this job runs under to SA, but why should I have to if this works on other servers. Is there anyway to make this work with the sql service account we created in AD?

Account has log on locally rights and is part of the local admin group.
0
WinPE
Asked:
WinPE
  • 3
  • 3
  • 2
2 Solutions
 
mass2612Commented:
Hi,

As you probably know the SQL agent uses the built in SP xp_logininfo to check the credentials of the account running the SQL job. This error generally means that this check is failing.

Have you tried adding the pre-Windows 2000 access group as described here - http://support.microsoft.com/kb/325363.

You have probably already reviewed these articles: -
http://support.microsoft.com/kb/834124
http://support.microsoft.com/kb/241643/
0
 
WinPEAuthor Commented:
Yeah we already have everyone added plus the user in that group... and unfortunatly I have seen those two posts :(...


This has to be stale due to the migration of computers... Is there anyway I can refresh the xp_logininfo...


I feel like its using credentials from the old nt4 domain account. I just dont understand why some domain accounts can work, and others cant.

0
 
mass2612Commented:
Are you able to view the user running the SP via a query : -
EXEC xp_logininfo
or
EXEC xp_logininfo "BUILTIN\Administrators", @option = 'members'

Can you execute
EXEC xp_logininfo "DOMAIN\USERNAME"
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
WinPEAuthor Commented:
Yah when I run the first query it gives me two domain user accounts, 1 local and these two..
NTDomain\servicesql
DOMAIN\ServiceSQL

now the capital S's don't throw off the authentication by any chance to they? I know that way out there..


when I run the second command (on the actual user), this is what I get...
(1 row(s) affected)

Server: Msg 8198, Level 16, State 34, Procedure xp_logininfo, Line 58
Could not obtain information about Windows NT group/user 'domain\servicesql'.


0
 
mass2612Commented:
I don't think there would be a problem due to the case. I'm stuck for what to try next sorry. I have also placed a reference to this Q in the community Advisor section to try to draw the attention of a true MS SQL expert here to help us out.
0
 
macentrapCommented:
Had this problem while ago, Only think of this right now:
Sloved it by setting the server service to run as the 'Local System' account and the Server Agent service to run as a domain account
0
 
macentrapCommented:
Try Rebooting the ADS, first
0
 
WinPEAuthor Commented:
Thanks Guys, our sql guys just ended up using a dif sql server acct, so much for testing :(
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now