SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Exception deserializing the package


Exception deserializing the package

Author
Message
kyagi.jo
kyagi.jo
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1614 Visits: 532
Hi,

I have an issue where I am using SQL Server Data Tools 14.0.1016.232. i am using encrypt sensitive with password on the package and the project. When I make a sensitive package parameter, then whenever I execute any task in the package, it says the following:

Exception deserializing the package "The package failed to load due to erro 0xC0011008 "error loading from XML. No further information can be specified for this problem because no Events object was passed where detailed error information can be stored.". This occurs when CPackage::LoadFromXML fails.

If I change the parameter from a sensitive parameter to a normal parameter, the package can run again when I execute the package.

Has anyone experienced this before, and do they have any suggestions on fixing it? It seems like it was recently the sensitive dropdown has broken, as packages that I had made in the past that were working with no issue, now only work if I uncheck the sensitive box on the parameters.

Edit: Sensitive project parameters works with no issue, just something odd going on with sensitive package parameters.
Edit 2: This happens on an extremely simplified case. New solution, new project. One dataflow, one package parameter set to sensitive. Execute empty data flow fails when sensitive.
kyagi.jo
kyagi.jo
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1614 Visits: 532
It turns out that I can get the simple package parameter example to work if my targetserverversion is set to SQL Server 2017 (an option that wasn't available before I updated my SQL server data tools). This is a bit annoying as the production server I have to work with is a SQL server 2016, so I'm not sure how well a SQL Server 2017 project will do on there.

Not sure why targetserverversion SQL Server 2016 has stopped working, sensitive project parameters was definitely available in SSDT in SQL server 2016.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search