Error: 'Failed to fetch job request'. (NETIQKB43088)

  • 7743088
  • 02-Feb-2007
  • 16-Aug-2010


NetIQ AppManager Suite 6.x
NetIQ AppManager Suite 7.0.x


Error: 'Failed to fetch job request'.
Error occurs when attempting to restart a stopped job


To address this issue, perform one of the following steps:

If the missing Knowledge Script was simply checked-out after the job was stopped, you can:

  • Check the missing Knowledge Script back into the QDB.
  • Restart the job normally.

If the Knowledge Script was deleted (usually occurs when Knowledge Script was originally copied from a default Knowledge Script, and then saved in a new Knowledge Script tab under a new name):

  • Delete the job itself.
  • Recreate the Knowledge Script.
  • Drop a new job the newly renamed Knowledge Script.

If the Agent was Cold-Started:

  • Start the jobs manually from the AppManager Operator Console or Control Center Console.


The error message may occur if the Knowledge Script (KS) the job was based on has been checked-out and/or deleted, but the job itself was not deleted.

When you attempt to manually restart a job in the Operator Console, the Management Server will query the QDB for script information regarding the Knowledge Script involved in the job.  If the Knowledge Script has been checked-out or deleted, the QDB will have no information regarding the Knowledge Script that the Management Server is asking about.  When the Management Server fails to locate any information about this Knowledge Script in the QDB, a 'Failed to fetch job request' error is returned on the job in the Operator Console.

This error may also be seen if the Agent was recently Cold-Started.  When this activity is performed, it eliminates all job code from the Local Repository.  As a result, it is possible that the Agent may try to re-start jobs before the Management Server has had enough time to provide the code for those jobs back to the Agent.

Additional Information

Formerly known as NETIQKB43088

It is normal for other jobs on the same Agent to continue running without any problems.  As long as these jobs are running from Knowledge Scripts which are still listed in the QDB, you should be able to stop and restart them without error.