I find a pair of these in my Application Event Log a little after midnight every night:
The SSIS Execution Process could not write to the IS catalog: MyServerName:SSISDB Error details: Unable to add new messages to the table of operation messages.:Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.; at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ISServerHelper.AppendEventMessage(SqlCommand cmd, Int64 operationId, Int32 message_type, DateTimeOffset message_time, Int16 message_source, String message_text, Nullable
1 extendedInfoId, String packageName, String packageLocationType, String packagePathFull, String eventName, String messageSource, String messageSrcId, String subComponentName, String packagePath, String executionPath, UInt32 threadId, Nullable1 messageCode, Int64& eventMessageId) at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.BasicEventInfo.WriteInternal(SqlCommand sqlCommand) at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.Loggable.Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ILoggable.Write(SqlConnection conn)
Searching the web for various parts of the error message failed to turn up anything useful.
There is an Agent job that runs SSISDB.internal.cleanup_server_retention_window at midnight every night, and Confio Ignite shows me that it blocks for about 6 minutes every time it runs. It blocks a couple of executions from SSIS ISServerExec of SSISDB.internal.append_event_message with LCK_M_IX waits.
I'm not sure which procedure is timing out, or if the timeout is from something unrelated. Is this a known issue (I'm running SQL Server 2012 SP1 Standard Edition (no CU installed)? Is there a good workaround?