1

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, Nullable1 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?

  • What's your patch level? Have you seen Phil's post on the matter? – billinkc Jun 19 '14 at 12:04
  • I'm running SQL Server 2012 SP1 Standard Edition (no CU installed). I haven't seen Phil's post, so thanks for the pointer. The KB is confusing - it says that the new indexes are part of CU4 and CU7, which implies that they aren't in CU5 and CU6. That doesn't fit with how I understood the CUs to work (each contains everything in the previous ones). – Mark Freeman Jun 19 '14 at 13:14
  • It looks like the recently released SP2 replaces everything up through SP1 CU9, so I'll just upgrade to that. – Mark Freeman Jun 19 '14 at 13:27
  • Sing out once you've applied SP2 and let us know if it fixes things. – billinkc Jun 20 '14 at 15:22
  • 1
    Did you found any resolution to above issue? Our job is failing and we also see similar message in logs. – user53451 Dec 4 '14 at 19:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.