Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SSIS package fails to start application lock timeout in SSISDB.catalog.create_execution

$
0
0

Hi,

I've recently upgraded my SSIS packages from SQL2005 to SQL2012 and I'm using SQL Agent to execute the pacakges. The jobs are failing about 20% of the time with a timeout error. I ran a trace to see what was causing the problem and the error occurs in the SSISDB.catalog.create_execution procedure when it calls sp_getapplock.

EXEC @lock_result = sp_getapplock
@Resource = 'MS_ISServer_Create_Execution',
@LockTimeOut= 5000,
@LockMode = 'Exclusive'

The timeout occurs in sp_getapplock when it calls sys.xp_userlock, the error number is 27195.

exec @result = sys.xp_userlock 0, @dbid, @DbPrincipal, @Resource, @mode, @owner, @LockTimeout

I have 11 packages that are all executed every minute so I suspect that this is 'causing' the problem. I had no issues when I execute 11 packages concurrently in SQL2005 or SQL2008.

Has anyone run into this problem? Do you have any idea how I can prevent this error other than scheduling the packages to run less frequently?

Note to MS - This is a significant blockingissue preventingus from upgrading to SQL2012 - it should be able to handle executing 11 packages per minute!

I'm running SQL2012 SP1 - 11.0.3000.0 (x64)

Thanks,

Tim


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>