Geek Answers Handbook

SQL Server 2012 CU7 Invokes an SSIS XML Task - Converting XSLT to a Variable Error

I currently have an SSIS package that makes a webservice call, returning an xml variable. The XML-Task then performs the XSLT to xml conversion and moves on to the data flow tasks. This worked before installing SQL Server 2012 CU7. Now that the package is running, errors in the XSLT Transform with this error in sysssislog:

An error has occurred with the following error message: "Unable to access closed stream."

If the result of the XML task is changed to a file, it succeeds.

Looking for updates in CU7, I found KB3063438 . It seems to me that they corrected one question, that I did not encounter, and caused another. It should also be noted that the package ran successfully on my local machine in SQL Server Data Tools. For testing, I installed CU7 since I was on CU6 and now I get the same error on my local machine.

Does anyone else have this problem? Or did anyone find a job or fix other than modifying the package to output to a file? I, too, was unsuccessful, and I would prefer not to output the data to a file first or roll back CU7.

** Update. I returned CU7 to my local machine and the package succeeds successfully.

+4
source share
2 answers

I ended up opening a support ticket with Microsoft. The result was an error detection in CU7 for SQL Server 2012 SP2 with an XML task when performing XSLT conversion and saving the variable output. Prior to patch / patch / CU8, they proposed two workarounds.

  • Change the output parameter of the XML task to go to the connection to the file, not to the variable.
  • Rollback CU7 to a production server that will run the SSIS package.

As soon as they get back to me with fix / fix / CU8, I will update or comment on this answer.

Update: I confirmed with MS that the patch is not in CU8. I will update again as soon as they tell me which patch / CU / SP it ultimately gets.

Update 2: When SP3 came out, I confirmed to MS that the hotfix is ​​not included. The only real feedback so far is that they have confirmed that this is a mistake, and it is on their list of projects. No ETA. I was tired of waiting for the fix, as he held on to our ability to fix one of our servers and eventually wrote a C # script task to perform the xml conversion. Alternatively, you can still use the XML task and set the output to a file. It works. Only when you set the output to a variable is this an error.

Final update: I have not yet personally verified this, but it looks like Microsoft has fixed it in the following SP / CU packages:

  • SQL Server 2012 SP3 CU5
  • SQL Server 2014 CU13
  • SQL Server 2014 SP1 CU9
  • SQL Server 2014 SP2 CU3
  • SQL Server 2014 SP3 CU5
  • SQL Server 2016 CU4
  • SQL Server 2016 SP1 CU2

https://support.microsoft.com/en-us/help/3115741

+4
source

I had the same problem. However, after working with Microsoft, we found that this problem could be resolved by upgrading to SQL Server 2012 SP3 with CU5.

https://support.microsoft.com/en-us/kb/3180915

+1
source

More articles:


All Articles