Scheduled Jobs failing, unknown owner?

The job failed. The owner () of job SetShopperSiteReleaseTimes does not have server access
The majority of our Jobs, run by the SQL agent, return teh above messages when running our scheduled DTS packages. We recently went through a domain migration from one domain name to another
I have changed everything that I can identify as being a problem. The server works normally for normal user, and it is only the scheduled jobs (when run by the agent) that have a problem
The Agent is running under a proper domain trust account, as it needs it to enable replication between a few other servers. Owners of the DTS packages were set to the wrong name, this has since been changed using the sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure
I'm loath to believe it is a domain authentication issue with the new domain, because normal Windows authentication between SQL and other applications works just fine. It is only the agent which seems to be having a problem. The agent also runs replication successfully
I suspect something is not quite right with the DTS packages themselves, but I don't know more than this
Anybody have any ideas? Thanks.Who owns the jobs ? If you set the job owner to sa does the job run ok ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Jerry Haltom" <jhaltom@.feedbackplusinc.com> wrote in message
news:C2372C43-2874-4B6E-9865-5AFB7016962C@.microsoft.com...
The job failed. The owner () of job SetShopperSiteReleaseTimes does not
have server access.
The majority of our Jobs, run by the SQL agent, return teh above messages
when running our scheduled DTS packages. We recently went through a domain
migration from one domain name to another.
I have changed everything that I can identify as being a problem. The server
works normally for normal user, and it is only the scheduled jobs (when run
by the agent) that have a problem.
The Agent is running under a proper domain trust account, as it needs it to
enable replication between a few other servers. Owners of the DTS packages
were set to the wrong name, this has since been changed using the
sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure.
I'm loath to believe it is a domain authentication issue with the new
domain, because normal Windows authentication between SQL and other
applications works just fine. It is only the agent which seems to be having
a problem. The agent also runs replication successfully.
I suspect something is not quite right with the DTS packages themselves, but
I don't know more than this.
Anybody have any ideas? Thanks.|||A job has an owner... You may open a job and see the owner on the first
tab... When a job is scheduled to run from SQL Agent, the first thing that
happens is that the owner is validated ( the owner must exist.)... If the
owner exists, the job runs, if the owner does NOT exist, the error you are
seeing is returned...
After the owner has been successfully validated, the job actually runs under
the permissions that SQL Agent runs with, ( Not the owners permissions.)
Try changing the owner of the job to someone you know exists ( like YOUR
login) and see if it fixes the problem..
--
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Jerry Haltom" <jhaltom@.feedbackplusinc.com> wrote in message
news:C2372C43-2874-4B6E-9865-5AFB7016962C@.microsoft.com...
> The job failed. The owner () of job SetShopperSiteReleaseTimes does not
have server access.
> The majority of our Jobs, run by the SQL agent, return teh above messages
when running our scheduled DTS packages. We recently went through a domain
migration from one domain name to another.
> I have changed everything that I can identify as being a problem. The
server works normally for normal user, and it is only the scheduled jobs
(when run by the agent) that have a problem.
> The Agent is running under a proper domain trust account, as it needs it
to enable replication between a few other servers. Owners of the DTS
packages were set to the wrong name, this has since been changed using the
sp_reassign_dtsowner (or similar, I forgot exact name) stored procedure.
> I'm loath to believe it is a domain authentication issue with the new
domain, because normal Windows authentication between SQL and other
applications works just fine. It is only the agent which seems to be having
a problem. The agent also runs replication successfully.
> I suspect something is not quite right with the DTS packages themselves,
but I don't know more than this.
> Anybody have any ideas? Thanks.