Sign in
 
Home20122008 R2200820052000LibraryForums
SQL Server >
> 
> 
0xC0010014 errors on SSIS 2005 SSIS packages with KB2729450 update (.net security update)

Unanswered 0xC0010014 errors on SSIS 2005 SSIS packages with KB2729450 update (.net security update)

  • Thursday, January 03, 2013 6:01 PM
     
     
    Sign In to Vote
    0

    Hi

    We've recently had the KB2729450 patch applied to our Win 2003 (R2) Server. Immediately after installation several of our SSIS packages (developed on Win7 machines) started erroring with message 0xC0010014 

    Removing the patch resolves the issue, but obviously since this is flagged as a critical security update we're not keen to be running without it. Is there a workaround that allows us to install the patch without getting this problem?

    Thanks
    Dan

     

All Replies

  • Friday, January 04, 2013 4:26 AM
     
     
    Sign In to Vote
    0

    Check if these are helpful!

    http://www.sqlservercentral.com/Forums/Topic737169-148-1.aspx

    http://support.microsoft.com/kb/919224

    Regards,Eshwar.

    Please use Marked as Answer if my post solved your problem and use Vote As Helpful if a post was useful.

     
  • Wednesday, January 09, 2013 8:51 AM
     
     
    Sign In to Vote
    0

    Thanks, but I'm afraid not.

    Thinking about it I'm not sure whether or not this forum is the place - possibly it's the .Net forum or the Win server 2003 forum?

    I guess the issue isn't specifically the error message. That only arises when patch KB2729450 is installed. Without that on the system we don't get the errors. So I can remove the patch and everything works (and that's what I've done). The problem is we want to install the patch because it's a critical safety update. Really, what I want to know is either

    - How we can apply the patch without getting the error,

    or

    - How we can resolve the error without getting rid of the patch.

    They're both the same question I guess but the first is more Windows Server centric, the second is a more SSIS centric way of putting it.

    What I've gathered from threads like the ones you link to is that it's a problem with different patch levels between computers - and I'd guess that comes down to a question of different .net libraries on the machines that compile and run the package? So a component referenced in the package isn't available (or isn't compatible) on the machine that's executing the package?

    Normally I'd just make sure all the machines had the same patch, but the problem is that the machines we're building the packages on on aren't 2003 server machines, they're Win7 -  and we can't apply the patch in question to those machines. Presumably one way out is to find the Win7 patch that has the same .net libraries in it as the KB2729450 patch? I have no idea how to find which patch that would be though.

    If I sound out of my depth here it's because I am - I'm not a server guy.

    If this seems more appropriate to Win 2003 server or .net framework forums would an admin mind moving the question there?


    • Edited by DTB____ Wednesday, January 09, 2013 8:55 AM
    •