Last Run Status (Start Date) - Not Updating
-
I have 2 SQL Servers that are not showing the Last Run Status updated for the last occurance of the job. The jobs that are running are backup jobs and are completing successfully, but yet the history is not being logged in the sysjobhistory table. The Next Run Date is accurate though. The only thing that I could find is that both jobs had reached their maximum job history rows per job. I deselected the Limit size of job history log option and still the Last Run Status is not updating.
After the problem continued I stopped and restarted the SQL Agent but still no change...
Any suggestions????
Thanks,
Zach
--------------------------
Zach -
Try re-creating the maintenance plan.
-
Zach,
You could also try running sp_purge_jobhistory on the job to see if that shakes things up for you.
Cheers,
Chris
-
Chris, thanks for the suggestion. I had actually already run the sp_purge_jobhistory before posting and it did not help. Any other ideas?
I would really hate to recreate all the jobs (thanks for the suggestion sa24) but it looks like that is the best option at this point...
-Zach
--------------------------
Zach -
If I was physically there and could poke at your server, and we had the time, and you were in the same puzzle-solving mood that I have been rightly accused of always maintaining, then ... maybe we could trace what was going on in the Profiler and see where things were breaking down.
However, given the difficulty of remote debugging and your need to get this working, I might follow sa24's suggestion. If they are not DB Maintenance Wizard jobs, you might be able to just right-click them to generate a script, and then drop the job and recreate it from the script.
Sorry I can't think of anything better right now. I'm sure it is something that could be figured out, for example something that's going wrong in sp_sqlagent_log_jobhistory, but it could be a long haul fixing it. At some point you need to ask if it's worth it ... is it?
As for me, I probably need to log off the forums pretty soon for a while, and I don't have any better idea for you.
Keep us posted,
Chris
-
Thanks for the reply Chris. If I get it figured out I'll post it.
Thanks again,
Zach
--------------------------
Zach -
There seem to be well known problems with job history and summary information being wrong. A thorough search (google, here, etc.) shows that others have reported the same problem without any solutions. Our staff has tried to recreate jobs, restart the agent, etc., etc. to no avail. Some jobs have proper information and some don't.
It has really caused anxiety since we weren't sure that production jobs would really run on time or if they had run. We just had to monitor and check to see that the effects were there.
We just live with it.
If you find a fix, then please post.
-
My specific problem was that the problem began on the same day that I installed a second instance on 3 seperate servers. The default instance on all 3 boxes stopped reporting history for the jobs. The jobs would run successfully but there was no history for the jobs.
After working with Microsoft for 7 days on the issue the problem was resolved soon after having the call escalated.
My specific problem was resolved by going to the SQL Server Network Client Utility openning the Alias tab and removing my alias and creating a new one for the second instance.
The alias was created as the name of the server and then given specific port. I first deleted the existing alias, then I created the new alias with a server name = (YOUR_SERVER_NAME\NEW_INSTANCE_NAME) and named the alias the same, then specified my port.
This resolved all of my issues and I hope that it helps any one else having this problem. I have not been able to find a solution to this specific problem anywhere on the web.
Hope this helps,
Zach
--------------------------
Zach -
Thanks for posting the fix for this issue! It saved me all kinds of time as I was having the exact same problem as you. Deleting the alias in the Network Client Utility is the key.
-
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply