Error deploying SSIS 2012 to Catalog DB

Question

Hi,
Am having an intermittent issue that happens when deploying to an SSIS Catalog (in the "Deploying project" step). basically sometimes when deploying an SSIS project to a Catalog that I administer, I receive an error telling me to lookup a particular operation
error message in the [catalog].[operation_messages] VIEW in the SSIS Catalog DB (and gives me an operation ID), the error in the view above is:
The project or operation records do not exist or you have not been granted the appropriate permissions to view them.
Now I am sure there is no rights or permission issues, and if I try deploying the project again (without changing any deployment parameters) there is no issue (albiet it might take a couple of tries). There is no SSIS packages running during the time I am
deploying and all server resources seems to be fine.
Am not entirely sure what's going on here.

Answer 1

Hi,
I have ran the profiler while the deployment issue was happening, and there was no deadlocking at all, in-fact all I can see while the deployment process is running (and leading up to a deployment failure) is the following:
Initially there was a bunch of SET calls to the SPID the deployment process is running under, which are:
-- network protocol: LPC
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed
Then a dynamic SQL query with parameters are called to select the operation_id for the deployment process under status 2 (which is the "Running" status) in the [catalog].[operations] table, this operation text looks like this:
exec sp_executesql N'SELECT [operation_id] FROM [catalog].[operations] WHERE [operation_id] = @operation_id AND [status] = @status',N'@operation_id bigint,@status int',@operation_id=28120,@status=2
When this operation did not find the relevant operation_id against status 2, (proc above) it appended a failure message against that operation, using the proc below:
exec [internal].[append_operation_message] @operation_id=28120,@message_type=120,@message_time='2012-07-31 10:59:33.3041311 +01:00',@message=N'The project or operation records do not exist or you have not been granted the appropriate permissions to view
them.',@message_source=20
A change of status on the operation occurred, the operation status changed to 4 which is "Failure"
exec [internal].[update_operation_status] @process_id=15984,@status=4,@end_time='2012-07-31 10:59:34.0189291 +01:00',@operation_id=28120
The "SSIS ISServerExec Crash Handler" application name then took over and called the function: [internal].[update_project_deployment_status] with status 4 (which is Failure):
exec [internal].[update_project_deployment_status] @status=4,@end_time='2012-07-31 10:59:34.0853311 +01:00',@operation_id=28120,@project_version_lsn=183,@description=N''
If the operation is success, step 1 will find a Status 2 (Running) for the deployment operation ID, and deployment procedures will be run to update each package and the parameters for that package.
Essentially it looks like there is no deadlocks, instead, there is something that is not placing a deployment operation with status 2 (Running) in the [catalog].[operations] table before the first procedure executed, causing this procedure not to find
any result, and then escalating a deployment failure... Why is this happening I have no idea!
I have the detailed profiler trace for both, a successful run and a failed run, which I can post here if that will help.
Cheers