locked
Updating CRM 2013 with SSIS RRS feed

  • Question

  • I have SSIS packages that run against CRM 2011. If we want to run these packages against CRM 2013 do we need to update the .dlls that we are referencing? We are using SSIS 2008R2 and updating CRM using the SSIS script componenent. We are referencing microsoft.crm.sdk.dll and microsoft.crm.sdktypeproxy.dll. My packages are still running and connecting to the new CRM 2013 but nothing is updating. I am getting the error:    "0x80040216   An unexpected error occurred.   Platform ". I have no idea what this error is telling me.

    Thanks,

    Kim


    Kim B.

    Monday, June 16, 2014 6:51 PM

All replies

  • SSIS 2008 R2 uses .Net Framework 3.5, and the only CRM assembly dlls that are compatible with .Net Framework 3.5 are the CRM 4 assemblies.

    The CRM 4 assemblies worked with CRM 2011, but CRM 2013 has dropped support for the CRM 4 endpoint, which will cause your errors.

    You have 2 main options:

    1. Use SSIS 2012. This uses .Net Framework 4, so you can use the CRM 2011 or CRM 2013 assemblies
    2. Keep using SSIS 2008 R2, and use web service references, rather than the SDK assemblies. This is a bit harder than using the SDK assemblies if using AD authentication, and a lot harder if using claims authentication


    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Tuesday, June 17, 2014 11:20 AM
    Moderator
  • Thank you David for your help. I have two more questions:

    1. For 2011 we used microsoft.crm.sdk.dll and microsoft.crm.sdktypeproxy.dll for our SDK assemblies. If we decide to upgrade the packages and use SSIS 2012 are Microsoft.Xrm.Sdk.dll and Microsoft.Crm.Sdk.Proxy.dll the replacement dlls to use?

    2. I currently save the packages to the SSIS database and run them by agent job on a 2008R2 database. If we upgrade our existing package to use SSIS 2012 will we still be able to save them to our 2008R2 database or would we need to save them to a 2012 database?


    Kim B.

    Tuesday, June 17, 2014 1:58 PM
    1. Yes, those are the assemblies to use, though you may or may not need Microsoft.Crm.Sdk.Proxy.dll
    2. I think the key point is that the packages will need to be run on a server with SSIS 2012. It may be possible to store them in a 2008R2 database (I've not tried), but the agent job would need to run on a SQL 2012 server. An alternative might be to run the packages with the SSIS 2012 dtexec tool

    Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk

    Tuesday, June 17, 2014 4:01 PM
    Moderator
  • I made a copy of our package and with SQL Server DataTools for VisualStudio2013 upgraded it. I am now getting an error Error: System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Crm.SdkTypeProxy. My main questions are:

    1. Which assemblies do I need to be using to update CRM 2013?

    2. Which location do these .dll's need to be put in and then referenced from in the ssis script task?

    3. Does any of the code in the script have to change?

    Thanks,

    Kim


    Kim B.

    Friday, June 20, 2014 8:35 PM
  • Hi Kim,

    You may consider using a commercial product like the COZYROC SSIS+ library. It supports all SQL Server versions starting from SQL 2005 and also supports all Dynamics CRM deployment types. When you test and develop from Visual Studio (BIDS), no license key is required.


    SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

    Wednesday, June 25, 2014 11:55 AM