I am hoping that maybe one of you could help me find the culprit with some
oddities I am experiencing with Jobs.

On all other SQL Servers I have ever dealt with, you create a job (could be
manually putting the steps together, or by scheduling a DTS package, or
making and scheduling a new Maintenance Package, etc.) and after it runs, in
the Jobs screen of Ent. Manager you can see what it's last status was,
whether it failed or succeeded, and pull up the History information on it.
This server I have inherited....well, this isn't happening.

First Question:
What, to your knowledge, at the end of a Job run would cause a SQL Server
to:
- Not update the Jobs Screen (last run status, failed/success, etc.)
- Not report errors if a Job fails on any given step
- Not add anything to the History of a job
- Not add the red circle X in the Jobs screen if it does indeed fail
- Not add anything to the SQL Server Logs
- Only place any report of failure is in the Windows Event Log

And more specifically, what can I do to resolve it?



More information about what I am seeing.....

I can create a job, doesn't seem to matter how.... manually, or create a DTS
package and then schedule it, or even create a new Maintenance Package from
the wizard and schedule it. What the steps are seem to be irrelevant as
well, plain text SQL, SQL stored proc, DTS package....doesn't matter. And
it doesn't seem to matter how many steps there are in the job either.

When I manually kick off the job, it will either get through all the steps,
or fail on one of them, after which it will simply quit. When done, there
is no feedback of success or failure as the Last Run Status still states
"Unknown", and right-clicking on View Job History gives the error message
"No history information exists for this job". The only way I know if the
job failed is if I check the Windows Event Logs under Application Logs, and
see a SQLServerAgent Warning about the job failing on a specified step, but
no information about the *why* of failure. Nothing is in the SQL Server
logs either.

I tried running all the steps of a job I made (8 steps, 7 are stored procs,
one is a DTS package) individually and can do so without error or issue.
Yet the afore mentioned "weirdness" happens when I create a Job from these
same steps and then run the job as a whole.

I even tried creating a new Maintenance Package and then ran the
job.....same outcome. No job is updating its status, history, etc. The
last job that did occurred back on 2/7/2006, but the oldest SQL Log only
goes back to 2/20/2006. So I have no idea if 'something' happened back
then, or even what that 'something' may be.

I saw a post in here "INF: How to Run a DTS Package as a Scheduled Job"
(http://support.microsoft.com/?kbid=269074) yet that didn't quite fit the
bill as it also doesn't matter where I run the job from or under what
owner....I still get the same issues.

Any help is greatly appreciated.

-- Andrew

The server info:
Product: SQL Server Standard Edition
Operating System: Microsoft Windows NT - 5.2 (3790)
Product Version: 8.00.2039 (SP4)
Language: English (United States)
OS memory: 2039(MB)
Processors: 2

Andrew,

First line of defence is to see whether MS SQL Server and SQL Server Agent
service account logins are still viable. Try to restart the services and
watch them coming back. Second, see if SQL Server Agent connection to SQL
Server is viable as well. That is Connection tab in agent properties page.
Make sure SQL Server Agent account has dbo rights in msdb database. If that
does not work reboot the server, check for latest service packs.

Ilya

"Andrew" <AndrewR2k1 (AT) hotmail (DOT) com> wrote