SQLServerAgent Error: Request to run job "jobname" (from User xxxx\aaaa) refused because the job already has a pending request from User XXXX\AAAA

• Pulivarthi Sasidhar

  SSCertifiable

  Points: 6706

  More actions

  December 13, 2010 at 12:47 am

  #141780

  Hi All,

  I am getting following error when my SQL agent starts running job as per schedule.

  SQLServerAgent Error: Request to run job "jobname" (from User xxxx\aaaa) refused because the job already has a pending request from User XXXX\AAAA.

  I am calling the Job in my procedure.

  How to overcome this and exucute succeddfully as per schedule.

  when i check the Job status it showed Idle.

  I used sp_stop_job before running the job -> then it gave the job was in idle state.

  PLease help me how to resolve this one.

  Thanks,

  Sasidhar P

• Adiga

  One Orange Chip

  Points: 27284

  More actions

  December 13, 2010 at 3:47 am

  #1261594

  Hi Sasidhar,

  I was not able to reproduce that issue. Can you please post the code and the job step details?

  Pradeep Adiga
  Blog: sqldbadiaries.com
  Twitter: @pradeepadiga

• Pulivarthi Sasidhar

  SSCertifiable

  Points: 6706

  More actions

  December 13, 2010 at 6:35 am

  #1261661

  Hi,

  The following code has been Used in a script which will run continuosly During day.The SSISPackage is a job which already existing package on SQL server.

  It will stopped by itselef by checking date changed to next day or not, which was first step of the script.

  Main:

  Date Checking Process

  Date was Same

  Goto Continue

  Date Was changed

  GOTO ExitS

  Continue:

  Select @SSISStepID=job_id from msdb..sysjobs where name='SSISPAckage'

  Exec msdb..sp_start_job 'SSISPAckage'

  SSISStepLoop:

  Exec getJobStatus @job_id=@SSISStepID ,@StatusID= @J_SSIS_Status output

  PRINT 'SSISPAckage '

  IF @J_SSIS_Status=1

  BEGIN

  GOTO SSISStepLoop

  END

  ELSE

  BEGIN

  GOTO SKIPSSIS

  END

  SKIPSSIS:

  Insert into XYZ

  EXEC ABD.dbo.testSP

  -----

  ----

  ---

  GOTO MainLoop

  ExitS:

  Print 'End'

• Adiga

  One Orange Chip

  Points: 27284

  More actions

  December 13, 2010 at 7:23 am

  #1261694

  I was able to overcome that by checking the job status before starting it.

  select @J_SSIS_Status=run_status from sysjobhistory where job_id=@SSISStepID

  and run_status=4

  print @J_SSIS_Status

  if @J_SSIS_Status <>4

  begin

  Exec msdb..sp_start_job 'sptest'

  end

  Pradeep Adiga
  Blog: sqldbadiaries.com
  Twitter: @pradeepadiga

• Sam....

  SSChasing Mays

  Points: 656

  More actions

  September 28, 2012 at 10:14 am

  #1543526

  Hi even I am facing similar issues but the job wont start for me. Any workaround

• SQLmountain

  SSCommitted

  Points: 1505

  More actions

  September 28, 2012 at 10:38 am

  #1543538

  You might want to make sure you are writing execution trace history to SQL Server Agent. This can give you some additional logging for troubleshooting purposes. Do this in SQL Agent properties and set it to "include job execution trace history".