{"id":216,"date":"2015-09-03T14:00:52","date_gmt":"2015-09-03T12:00:52","guid":{"rendered":"http:\/\/sqlkover.com\/?p=216"},"modified":"2015-09-02T14:34:14","modified_gmt":"2015-09-02T12:34:14","slug":"ssis-unexpected-termination","status":"publish","type":"post","link":"https:\/\/sqlkover.com\/ssis-unexpected-termination\/","title":{"rendered":"SSIS – Unexpected Termination"},"content":{"rendered":"

<\/p>\n

I was toying around with the new SQL Server 2016 CTP release<\/a>\u00a0and I wanted to run a few SSIS packages to test out the new logging levels.\u00a0However, everytime I ran a package in the SSIS catalog, it ended with the dreaded \u201cunexpected termination\u201d message. In such a case, nothing is logged to the catalog, so you can start digging for the cause that makes your SSIS packages go dead before they start running.<\/p>\n

There are a lot of reasons why you can get the\u00a0unexpected termination<\/em> message (and for some of those there is a fix for SQL Server 2012 and 2014). But looking at the event log I could quickly track down the root cause:<\/p>\n

\"evenlog\"<\/a><\/p>\n

\n

Cannot find the symmetric key \u2018xxx\u2019, because it does not exist or you do not have permission.<\/p>\n<\/blockquote>\n

Since I\u2019m the admin on the machine, I certainly have permission so it means the key doesn\u2019t exist. Then I realized I had upgraded SQL Server a few times: from SQL Server 2016 CTP 2.0 to 2.1 to 2.2 to 2.3. Apparently somewhere in the upgrade process, the symmetric key of the SSIS catalog was lost. Since this is a simple virtual machine for playing around with SQL Server 2016, the solution was simple: delete the SSIS catalog and create it again. Bingo, all packages ran again without issues. However, if you\u2019re on a production machine, you might want to take precautions for this issue when you upgrade your SQL Server instance.<\/p>\n

<\/p>\n<\/body>","protected":false},"excerpt":{"rendered":"

I was toying around with the new SQL Server 2016 CTP release\u00a0and I wanted to run a few SSIS packages to test out the new logging levels.\u00a0However, everytime I ran a package in the SSIS catalog, it ended with the dreaded \u201cunexpected termination\u201d message. In such a case, nothing is logged to the catalog, so […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[5],"tags":[31,17,16,72],"class_list":["post-216","post","type-post","status-publish","format-standard","hentry","category-ssis","tag-sql-2016","tag-ssis","tag-syndicated","tag-unexpected-termination"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/posts\/216","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/comments?post=216"}],"version-history":[{"count":1,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/posts\/216\/revisions"}],"predecessor-version":[{"id":219,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/posts\/216\/revisions\/219"}],"wp:attachment":[{"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/media?parent=216"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/categories?post=216"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sqlkover.com\/wp-json\/wp\/v2\/tags?post=216"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}