Hi,

I am working intergration between SQL and sybase from SSIS. Its execute perfectly when i run manually from SSIS.

But if i create a job in SQLAgent and give schedule means  only one row data inserting after that it show error like "Request to run job from user xx refused because the job is already running from a request by user xxx".

Before that i configure job schedule 1 min after this error i change to 10 mins then also same error only prompting.

Note: Both are same  user.

Please do the needful

Thanks

Hi Jafferpg,

I assume you run the code from inside a stored procedure.

You probable issue is in fact a job is run by SQL Agent which is an async process, so the job completion does not necessarily return.

In general your design is not ideal, whatever involves "separation" e.g. a SP calling a job with WAIT is not elegant. Consider revising your approach.

In the meanwhile to prove or dismiss my theory try executing whatever is in the job in the same stored proc. Tell us what do you find.

Check the below link

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/c6b50562-2fc3-4453-98c8-ed7e78cc15a6/sqlserveragent-error-request-to-run-job-topupapprovalstaging-from-user-sa-refused-because-the-job?forum=sqlintegrationservices

Hi Milas,

Thanks a lot for your reply. 

For your information, i am not using store procedure and not write any query inside. 

just using dataflow task in SSIS for get a data from sql server table from OLEDB source and insert the data sybase table to ado.net destination. it perfectly works manually when i execute.

i refer that link, I feel the given solution not suits for my task issue.

Thanks

Hi Jaffer,

As per my understanding, the issue can be caused by the last execution is not yet completed when you run the job again. For example, you normal job execution time to complete is 12 mins, while you try to execute the job every 10 mins.

To troubleshoot this issue, we can find the job execution status with sp_help_job stored procedure or xp_sqlagent_enum_jobs stored procedure. If the issue is still exist, please restart SQL Server Agent Services to test the issue again.

Thanks,
Katherine Xiong