BIDS in VS2008 not working for SSIS packages. - cannot load IDTSPackageSigning100......

Answered BIDS in VS2008 not working for SSIS packages. - cannot load IDTSPackageSigning100......

  • Dienstag, 6. Juli 2010 11:13
     
     

    Folks,

    I'm trying to create a new SSIS 2008 package on my dev machine, but I suddenly get:

    Error loading 'Package.dtsx' : Could not load type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackageSigning100' from assembly 'Microsoft.SqlServer.DTSRuntimeWrap , Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.. 

    I had SQL Server 2008 R2 on that machine for a bit, but removed it and re-installed 2008 with SP1. I also ran the "Repair" function of the SQL Server 2008 installation on it, to no avail....

    Any ideas??


    Marc - Berne, Switzerland - May The Source Be With You!

Alle Antworten

  • Dienstag, 6. Juli 2010 12:17
     
     Beantwortet

    Hi Marc,

    There could be some problems with installing both SQL versions within the same box. As far as i know Microsoft also doesnt support this.

    Anyway, what i learned by my existing installation experience is; you can get rid of it by a clean installation. It will took approx. 1 hrs to install, but more than 1 hours to drill into the reason. Your choice.

    (Btw, please restart your computer when uninstallation is complete and whenever your computer requires a restart, and uninstall/reinstall .NET framework 3.5 SP1 if required too.)

    Hope that helps

    Onur


    BI and ERP Senior Consultant @ Nexum Bogazici
    If it is, Please dont forget to mark as answered or at least vote as helpful if the post helps you in any ways.

    Visit: ssisnedir.com/blog

  • Donnerstag, 11. November 2010 19:45
     
     

    Unistalled SQL2008 R2 and SQL2008 SP2 in my case and resolved the issue

  • Dienstag, 8. Februar 2011 20:35
     
     
    I tried to uninstall SQL2008 R2 but there was some things left on the computer. How can I do a complete uninstall of SQL Server 2008 R2? I need to run SQL Server 2008 instead,
  • Dienstag, 2. August 2011 06:05
     
     

    I'm having the same frustrating issue here now.

    I use SQL2008 SP2 for all day-to-day development.  Some time ago, I installed something that brought with it an instance of SQL2008 R2 Express.  I had a horrible suspicion it might cause an issue, but everything appeared to run fine afterwards.  Until today.  I went to open an SSIS package and get the error mentioned at the start of this thread.

    Deciding I could live without R2, I attempted an uninstall - however now it won't completely uninstall, similar to perwi's issue I suspect.  For example, I attempt to uninstall "Microsoft SQL Server 2008 R2 Native Client" but it complains that Microsoft SQL Server 2008 Database Engine Services is dependent on it

    How can my SQL 2008  Database Engine be dependent on an R2 component that didn't exist when I first installed it?  How can I get rid of the R2 components without requiring a complete re-install of SQL2008?  Is there a fix for this specific SSIS issue?

    Help!

    Michael

  • Dienstag, 2. August 2011 23:40
     
     Vorgeschlagene Antwort

    Just a quick update - I may have accidentally stumbled on the fix.  I noticed the folowing setting in BIDS:

    Tools - Options - Business Intelligence Designers - Integration Services Designers - General - Check digital signature when loading a package

    I unchecked the box, and now I can load my package without the error.  My SQL 2008 R2 install is probably still toast, but at least I can get on with this change I need to do.

    Michael

    • Als Antwort vorgeschlagen AfricanPeter Donnerstag, 4. August 2011 06:56
    •  
  • Montag, 22. August 2011 22:36
     
     

    Brilliant!

    My outstanding question lies with why the problem existed to begin with...the EXACT same software built it. This particular SSID was a trimmed down export from SQL's 'import data' routine. It was a quite basic dtsx package, in other words, built on the same machine at an earlier date (just a little over a month ago). I do know that there's been some Window's updates run on the server, but geez...

    Thanks for sharing that tip, Maestro!

  • Mittwoch, 7. September 2011 12:44
     
     
    Thanks Michael. We faced exactly same issue as yours. And your solution worked for us. :)
  • Montag, 2. Januar 2012 19:45
     
     

    Thanks for this!!! It works!!!!

     

  • Freitag, 13. April 2012 18:20
     
     

    I'm so glad I found this!  I had an SSIS package running perfectly, created a new instance on my SQL server which appears to have 'down-graded' my SQL from SQL 2008 R2 to SQL 2008.  The next time I opened the package I got this error.  Turned off the digital signature checking and it worked!  Thanks. 

  • Donnerstag, 26. April 2012 19:51
     
     
    What a wizard, works awesome.  Thanks for the post.
  • Sonntag, 23. Dezember 2012 14:30
     
     
    Thanks Michael. Your tip helped me as well!
  • Montag, 11. Februar 2013 18:46
     
     

    Just a quick update - I may have accidentally stumbled on the fix.  I noticed the folowing setting in BIDS:

    Tools - Options - Business Intelligence Designers - Integration Services Designers - General - Check digital signature when loading a package

    I unchecked the box, and now I can load my package without the error.  My SQL 2008 R2 install is probably still toast, but at least I can get on with this change I need to do.

    Michael


    Worked for me, Thanks