none
BizTalk 2010 upgrade - can not install new WCF Adapter Pack RRS feed

  • Question

  • Greetings!

    I have been tasked with upgradng a Biztalk 2009 install on a Win7 box to 2010. 

    Visual Studio 2010 went fine.  So did the inplace upgrade to SQL Server 2008 R2.  The install of BizTal Developer went fine.  The admin consol opens and all looks good.  Existing applications that used file adapters to get to folders worked.  Sounds pretty good so far?

    But the Oracle connections failed.  The OracleDB adapter is not accesible in the properties drop down box.  We are using the WCF Custom adapter.  So - I figured time to put in the new WCF Adapter pack.  I unistalled the old like the instrauctions say and then tried to put in the new.  At this point I get an error saying it can not install as the old one is still there.  Of course - it is not.

    Help?

    Thanx,

    - Ziggy -


    Monday, August 22, 2011 6:29 PM

Answers

  • Hi Ziggy,

    Upgrading from Previous Releases of the BizTalk Adapter Pack

    Before upgrading the BizTalk Adapter Pack ensure:

    • You upgrade the WCF LOB Adapter SDK also. BizTalk Adapter Pack 2010 requires WCF LOB Adapter SDK 2010.
    • No applications that reference the adapter DLLs are running.
    To upgrade BizTalk Adapter Pack
    1. Stop all applications that reference the adapter DLLs.

    2. Uninstall the older release of BizTalk Adapter Pack by clicking Start, and then clicking Control Panel > Programs and Features > Uninstall/Change.

    3. Install BizTalk Adapter Pack 2010.

    Important

    After you have upgraded the BizTalk Adapter Pack, the applications you created with the older version of the BizTalk Adapter Pack can be used with the upgraded version.

    After Removing the BizTalk Adapter Pack

    You might need to perform the following steps after removing the BizTalk Adapter Pack:

    • Remove the adapter bindings or the .NET Framework Data Provider registration, if the setup wizard failed to do so.
      Remove the custom RFCs, if you chose to install the Data Provider for SAP.

    Removing the Bindings or the .NET Framework Data Provider registration

    Perform these steps only if the setup wizard fails to remove the adapter bindings or .NET Framework Data Provider registration from the machine.config file.

    To remove the adapter bindings or .NET Framework Data Provider registration
    1. Navigate to the machine.config file on the computer. For example, on a 32-bit platform, the machine.config is available under <system drive>:\WINDOWS\Microsoft.NET\Framework\<version>\CONFIG.

      In this path, <version> is the version of the .NET Framework. For example, for Microsoft .NET Framework 3.5 SP1, the version will be v2.0.50727.

    2. Open the file using a text editor.

    3. To remove the adapter binding registration:

      1. Search for the element "system.serviceModel" and remove the following from under the element:
        <client>
         <endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
         <endpoint binding="siebelBinding" contract="IMetadataExchange" name="siebel" />
         <endpoint binding="oracleDBBinding" contract="IMetadataExchange" name="oracleDb" />
         <endpoint binding="OracleEBSBinding" contract="IMetadataExchange" name="oracleEBS" />
         <endpoint binding="sqlBinding" contract="IMetadataExchange" name="mssql" />
        </client>
        
      2. Search for the element "bindingElementExtensions" under system.serviceModel\extensions.

      3. Remove the following sections under the "bindingElementExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

        For SAP adapter, remove:
        <add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Siebel adapter, remove:

        <add name="siebelAdapter" type="Microsoft.Adapters.Siebel.SiebelAdapterExtensionElement,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle Database adapter, remove:

        <add name="oracleDBAdapter" type="Microsoft.Adapters.OracleDB.OracleDBAdapterExtensionElement,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle E-Business adapter, remove:

        <add name="OracleEBSAdapter" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingElementExtensionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For SQL adapter, remove:

        <add name="sqlAdapter" type="Microsoft.Adapters.Sql.SqlAdapterBindingElementExtensionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      4. Search for the element "bindingExtensions" under system.serviceModel\extensions.

      5. Remove the following sections under the "bindingExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

        For SAP adapter, remove:

        <add name="sapBinding" type="Microsoft.Adapters.SAP.SAPAdapterBindingSection,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Siebel adapter, remove:

        <add name="siebelBinding" type="Microsoft.Adapters.Siebel.SiebelAdapterBindingSection,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle Database adapter, remove:

        <add name="oracleDBBinding" type="Microsoft.Adapters.OracleDB.OracleDBAdapterBindingSection,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle E-Business adapter, remove:

        <add name="OracleEBSBinding" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingCollectionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For SQL adapter, remove:

        <add name="sqlBinding" type="Microsoft.Adapters.Sql.SqlAdapterBindingCollectionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    4. To remove the .NET Framework Data Provider registration:

      • Search for the element "DbProviderFactories" under the system.data node.

      • Look for the .NET Framework Data Providers that are still registered. Remove the following sections under the DbProviderFactories node, depending on the existing .NET Framework Data Providers. You must remove all the providers if they exist.

        For Data Provider for SAP, remove:

        <add name="SAPClient Data Provider" invariant="Microsoft.Data.SAPClient" 
          description=".NET Framework Data Provider for mySAP Business Suite"  type="Microsoft.Data.SAPClient.SAPClientFactory,Microsoft.Data.SAPClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Data Provider for Siebel, remove:

        <add name="SiebelClient Data Provider" invariant="Microsoft.Data.SiebelClient"
          description=".NET Framework Data Provider for Siebel eBusiness Applications"
          type="Microsoft.Data.SiebelClient.SiebelProviderFactory,Microsoft.Data.SiebelClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    5. Save and close the machine.config file.

    For reference see installation guides of BizTalk Adapter Pack 2.0 and 2010. Information above is taken from those resources.


    BizTalk
    • Proposed as answer by DPS Bali Tuesday, August 23, 2011 11:30 AM
    • Marked as answer by Andrew_ZhuModerator Monday, August 29, 2011 2:49 AM
    Tuesday, August 23, 2011 9:24 AM
    Moderator

All replies

  •  

    Did you install the WCF Line of Business Adapter SDK?  

    http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18530

     

    If you've done that, you may find this link useful.  Its for 2006R2, but everything there I think applies to using the adapter in 2010:

     

    http://sujant.wordpress.com/2008/08/09/biztalk-configuring-wcf-custom-adapter-for-oracle-databases/

     

     


    Down there somewhere, its just ones and zeros.
    Monday, August 22, 2011 7:19 PM
  • Are you on a 64-bit computer, then there is most likely both a 32 and a 64 bit verson of the WCF adapter pack as BizTalk uses the 64 bit and Visual Studio uses the 32-bit. 
    Torben Christiansen http://snatchedmoments.blogspot.com/
    Monday, August 22, 2011 8:31 PM
  • Hi Ziggy,

    Upgrading from Previous Releases of the BizTalk Adapter Pack

    Before upgrading the BizTalk Adapter Pack ensure:

    • You upgrade the WCF LOB Adapter SDK also. BizTalk Adapter Pack 2010 requires WCF LOB Adapter SDK 2010.
    • No applications that reference the adapter DLLs are running.
    To upgrade BizTalk Adapter Pack
    1. Stop all applications that reference the adapter DLLs.

    2. Uninstall the older release of BizTalk Adapter Pack by clicking Start, and then clicking Control Panel > Programs and Features > Uninstall/Change.

    3. Install BizTalk Adapter Pack 2010.

    Important

    After you have upgraded the BizTalk Adapter Pack, the applications you created with the older version of the BizTalk Adapter Pack can be used with the upgraded version.

    After Removing the BizTalk Adapter Pack

    You might need to perform the following steps after removing the BizTalk Adapter Pack:

    • Remove the adapter bindings or the .NET Framework Data Provider registration, if the setup wizard failed to do so.
      Remove the custom RFCs, if you chose to install the Data Provider for SAP.

    Removing the Bindings or the .NET Framework Data Provider registration

    Perform these steps only if the setup wizard fails to remove the adapter bindings or .NET Framework Data Provider registration from the machine.config file.

    To remove the adapter bindings or .NET Framework Data Provider registration
    1. Navigate to the machine.config file on the computer. For example, on a 32-bit platform, the machine.config is available under <system drive>:\WINDOWS\Microsoft.NET\Framework\<version>\CONFIG.

      In this path, <version> is the version of the .NET Framework. For example, for Microsoft .NET Framework 3.5 SP1, the version will be v2.0.50727.

    2. Open the file using a text editor.

    3. To remove the adapter binding registration:

      1. Search for the element "system.serviceModel" and remove the following from under the element:
        <client>
         <endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
         <endpoint binding="siebelBinding" contract="IMetadataExchange" name="siebel" />
         <endpoint binding="oracleDBBinding" contract="IMetadataExchange" name="oracleDb" />
         <endpoint binding="OracleEBSBinding" contract="IMetadataExchange" name="oracleEBS" />
         <endpoint binding="sqlBinding" contract="IMetadataExchange" name="mssql" />
        </client>
        
      2. Search for the element "bindingElementExtensions" under system.serviceModel\extensions.

      3. Remove the following sections under the "bindingElementExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

        For SAP adapter, remove:
        <add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Siebel adapter, remove:

        <add name="siebelAdapter" type="Microsoft.Adapters.Siebel.SiebelAdapterExtensionElement,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle Database adapter, remove:

        <add name="oracleDBAdapter" type="Microsoft.Adapters.OracleDB.OracleDBAdapterExtensionElement,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle E-Business adapter, remove:

        <add name="OracleEBSAdapter" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingElementExtensionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For SQL adapter, remove:

        <add name="sqlAdapter" type="Microsoft.Adapters.Sql.SqlAdapterBindingElementExtensionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
      4. Search for the element "bindingExtensions" under system.serviceModel\extensions.

      5. Remove the following sections under the "bindingExtensions" node, depending on the available adapter binding. You must remove all the bindings if the setup wizard fails to remove any.

        For SAP adapter, remove:

        <add name="sapBinding" type="Microsoft.Adapters.SAP.SAPAdapterBindingSection,Microsoft.Adapters.SAP, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Siebel adapter, remove:

        <add name="siebelBinding" type="Microsoft.Adapters.Siebel.SiebelAdapterBindingSection,Microsoft.Adapters.Siebel, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle Database adapter, remove:

        <add name="oracleDBBinding" type="Microsoft.Adapters.OracleDB.OracleDBAdapterBindingSection,Microsoft.Adapters.OracleDB, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Oracle E-Business adapter, remove:

        <add name="OracleEBSBinding" type="Microsoft.Adapters.OracleEBS.OracleEBSBindingCollectionElement, Microsoft.Adapters.OracleEBS, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For SQL adapter, remove:

        <add name="sqlBinding" type="Microsoft.Adapters.Sql.SqlAdapterBindingCollectionElement,Microsoft.Adapters.Sql, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    4. To remove the .NET Framework Data Provider registration:

      • Search for the element "DbProviderFactories" under the system.data node.

      • Look for the .NET Framework Data Providers that are still registered. Remove the following sections under the DbProviderFactories node, depending on the existing .NET Framework Data Providers. You must remove all the providers if they exist.

        For Data Provider for SAP, remove:

        <add name="SAPClient Data Provider" invariant="Microsoft.Data.SAPClient" 
          description=".NET Framework Data Provider for mySAP Business Suite"  type="Microsoft.Data.SAPClient.SAPClientFactory,Microsoft.Data.SAPClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
        For Data Provider for Siebel, remove:

        <add name="SiebelClient Data Provider" invariant="Microsoft.Data.SiebelClient"
          description=".NET Framework Data Provider for Siebel eBusiness Applications"
          type="Microsoft.Data.SiebelClient.SiebelProviderFactory,Microsoft.Data.SiebelClient, Version=<version>, Culture=neutral, PublicKeyToken=<public key>" />
    5. Save and close the machine.config file.

    For reference see installation guides of BizTalk Adapter Pack 2.0 and 2010. Information above is taken from those resources.


    BizTalk
    • Proposed as answer by DPS Bali Tuesday, August 23, 2011 11:30 AM
    • Marked as answer by Andrew_ZhuModerator Monday, August 29, 2011 2:49 AM
    Tuesday, August 23, 2011 9:24 AM
    Moderator