Hello:

I don't have much information to go on and I am not familiar with SQL jobs
or package files. So, I'm just going to ask.

This client moved locations about ten months ago. And, they got a new server.

Doing so required, of course, a change of DNS name, server name, etc.

Now, despite all of that, most of their SQL Jobs and packages work--both
before the move and after the move.

But, 6 of the jobs no longer run for some reason. Therefore, the packages
that the jobs are based on no longer work.

They have tried every possible thing. They have updated the SQL Server
Authentication for the package file, change the owner of the jobs to "sa",
etc.

And, the SQL code that the jobs are based on have not changed.

So, on a real basic level, what sort of things could have happened to cause
the jobs to not work?

They are each really simple one-step jobs, at that.

AND, FOR THOSE OF YOU WONDERING WHAT ERROR MESSAGE CAME UP, there was none!
Believe it or notm, we checked the Event Log Viewer and SQL logs and there
were no concrete error messages.

Thanks!

childofthe1980s

Hello childothe1980s,

I do not know from the description if you suspect the packages or the jobs
themselves. From what I can understand it does look s though it is the job
that is failing and therefore the package never actually fires.

Is this true?


Things to check.

Remove SQL Server Agent - Go to the server and log on Does the package itself
work by itself?

If it does then recreate a job from scratch and put the DTSRun command in
there and execute that. What happens now?

How did you migrate the jobs? - Script out the jobs that fail and see if
there is anything in the script that looks suspicious like the wrong server
name for the job.

Changing the owner of the job to sa may not be as quick a fix as you think
and this is detailed here

http://support.microsoft.com/?kbid=269074


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com