....than the domain assigned to the SQL Agent Service account. For example, we
have an account XYZ\SQLServiceAcct that is shown as the owner of the
particular SA job and is also the account running the Agent. It is reflected
in the message text related to several of the job steps, but not all of them.
Particularly, a DTS package step will show ABC\SQLServiceAcct in the error
text and this is not a valid domain account combination any longer.

A little history...
This server giving us fits was once a clustered SQL Server. Due to one
reason or another, it was before my time, the cluster was broken and the
server was returned to and is running as non-clustered. The ABC domain was
the domain in use when the cluster was established.

We can find no reference to the old domain anywhere on the server, including
within the registry. Since ABC is no longer valid, it is not to be found on
the Domain Controller or in the AD (Active Directory).

Does anyone have any idea where this rogue domain reference may be coming
from? It's very disconcerting and I'd very much like to get it cleaned up.

I'm not convinced that this is what is causing our jobs to fail, but
cleaning it up would relieve at least one worry I've inherited.

Thanks in advance for any info that anyone can provide.

Hello Chris.Elliott,

Have you scripted the job steps themselves and looked at the script for the
name of this server?

you can also try the same with the DTS packages by saving to .bas files.


Allan

First, thanks for the quick response Allan. Yes, I did script out the jobs in
question and the only place I found a reference to the domain was in
association with my login, as the person generating the script in a comment
and one time in a @owner_login_name = N'XYZ\notgoingtotellyou' in the EXECUTE
statement for the job. I didn't find any other reference to any domain
elsewhere.

It's been quite a puzzle. We can find no where that the old domain is ever
referenced. And as mentioned in the original thread, I've even searched the
registry for possible remnants since the cluster was broken.

Chris Elliott
Spirit AeroSystems, Inc.
---------------------------------------

"Allan Mitchell" wrote: