Job has been suspended/MSDB restoration

  • We're migrating a server to a new data center. I just restored the msdb, and was testing the maintenance plans and backup plans we have on there. When I try to execute them, I get an error that says the "Job has been suspended, check the log".

    However, when I check the log, it only goes back to when I actually made the copy of msdb. So the current job history/agent log information isn't tracking. There are no new entries being made.

    Clearly I'm missing a step here, anyone want to help a guy out?:satisfied:

    Thanks!

  • It could be because the jobs are trying to execute on a server where they were not designed and you need to amend the server id properties. you can do that in msdb.sysjobs (i think thats the one). Check the originating server id (links to master..sysservers) properties and update as necessary.

    I do find it odd though that there is nothing in the logs. Do you not get anything in job history or anything?

  • The originating server for all jobs/maint plans is set to 0, so everything is conceptually on the same server.

    The logs show information going up to the date when I backed up and transferred msdb. They will not reflect any current information or attempts at jobs; they do not show any new information.

  • If it is Sql Server 2000 ensure that the name of the new server is reflected in originating_server column in sysjobs system table. If not you can update the same to reflect the new server name.

    [font="Verdana"]- Deepak[/font]

  • I was able to run the following script, which seemed to correct my issues:

    -- Delete the existing rows.

    DELETE FROM msdb.dbo.syssubsystems

    -- Fill the table with new rows pointing to the proper location of the DLLs.

    EXEC msdb.dbo.sp_verify_subsystems 1

    We changed from the C:\ to the D:\ on the .dll and .exe agent files, which apparently required a deletion and verification of these files.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply