Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
mark.innes
Starting Member
7 Posts |
Posted - 2006-03-07 : 08:16:57
|
The following error is genereated on any scheduled jobs that are ran...The job failed. Unable to determine if the owner (domain\username) of job testjob has server access (reason: Could not obtain information about Windows NT group/user 'domain\username'. [SQLSTATE 42000] (Error 8198)). It is SQL Server 2000 on a 2003 Server. The server name has recently been changed but it connects to the new server name okay (called Local), the active directory is on a different server. I have tried changing the job user to sa but the same happens. The job is run a EXEC step for the xp_sqlmaint ext stored procedure.It seems to have to be something to do with the server name change, can anyone help please? |
|
kpsreenath
Yak Posting Veteran
52 Posts |
Posted - 2006-03-07 : 09:34:15
|
The scenario mentioned above is documented and the way to troubleshoot as well.Not sure whether this will be helpful or not.http://support.microsoft.com/?kbid=834124ThanksSree |
 |
|
mark.innes
Starting Member
7 Posts |
Posted - 2006-03-07 : 10:51:02
|
I tried this without any luck.I notice that the server reg name is local rather than the actual name. Would it cause any probs by deleting the registration and then re-registering the server, would this loose any information?thanks |
 |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-07 : 11:08:32
|
check your servername by running:select @@servernamethen verify if it's the same name as your machineif not the same, resolve by changing either sql servername or machine name--------------------keeping it simple... |
 |
|
mark.innes
Starting Member
7 Posts |
Posted - 2006-03-07 : 11:33:46
|
Thanks for that, the server name is different.It is SQL Server 2000 so do I need to reinstall SQL to change this?thanks |
 |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-07 : 21:18:17
|
Dearest NOyou can rename the sql server instead use sp_dropserver to drop the current sql server name, do this in QArestart the sql servicesissue sp_addlinkedserver, also in QA to add the new sql servername (should be the same as your machine name)restart the sql servicesfor more details refere to BOLverify if this has resolved the problem...--------------------keeping it simple... |
 |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-03-07 : 21:24:48
|
wait i just realized!are there live applications connecting to this server?if yes, you'd better check with them, renaming the server will obviously result to connection errorsalso, another option is to rename the machine itself, reverting it back to its old nameunless your network guys are like Stevie's, good luck then... --------------------keeping it simple... |
 |
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
|
|
|
|
|
|