Link to home
Start Free TrialLog in
Avatar of WinPE
WinPE

asked on

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.
Avatar of mass2612
mass2612
Flag of Australia image

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/
Avatar of WinPE
WinPE

ASKER

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.

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"
Avatar of WinPE

ASKER

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'.


SOLUTION
Avatar of mass2612
mass2612
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Try Rebooting the ADS, first
Avatar of WinPE

ASKER

Thanks Guys, our sql guys just ended up using a dif sql server acct, so much for testing :(