In memory of Howard S. Edidin – How to install BizTalk Server 2020 Accelerator for HL7 in a standalone machine

In memory of Howard S. Edidin – How to install BizTalk Server 2020 Accelerator for HL7 in a standalone machine

Recently a friend of mine, Howard S. Edidin, a truly T-Rex, passed away. He was a former BizTalk Server MVP and he dedicated most of his professional life to BizTalk Server and HL7, work that you can find perpetuated in this book: HL7 for BizTalk. I personally couldn’t find a better way to honor him than this way: How to install BizTalk Accelerator for HL7 in a standalone machine.

Install BizTalk Accelerator for HL7

Starting with BizTalk Server 2013 R2 and newer versions, the BTAHL7 installation includes a 32-bit installation package (BizTalk AcceleratorsA4HL7 on the BizTalk Server ISO) and a 64-bit installation package (BizTalk AcceleratorsA4HL7(64) on the BizTalk Server ISO).

On a 32-bit computer, install only the 32-bit package. On a 64-bit computer, install the 32-bit or 64-bit package. The 64-bit package enables the adapter and pipelines to run in both 32-bit and 64-bit mode.

Note: The user installing and configuring BTAHL7 must be a member of the BizTalk Administrators group, and a member of the Administrators group on the SQL Server where the BTAHL7 data is stored.

Note: BizTalk Server should have the basic components installed and configured, including a 32-bit BizTalkServerApplication host with standard out of the box adapters, Enterprise Single Sign-on (SSO), the Group, and Runtime.

To install BizTalk Accelerator for HL7 we need to:

  • Run the BizTalk Accelerator for HL7 (A4HL7) setup.exe as Administrator.
  • On the Welcome to the Wizard for Microsoft BizTalk Accelerator for HL7 page, select Next.
  • On the License Agreement page, accept the terms, and then select Next.
  • On the Customer Information page, enter your user name and organization, and then select Next.
  • On the Setup Type page, select the Typical setup, and then select Next.
  • On the Logging Service Account page, leave the default group names and select Next.
    • The Logging Service Account page automatically gives the following groups the logging permissions:
      • BizTalk Server Administrators
      • BizTalk Application Users
      • BizTalk Server B2B Operators
      • BizTalk Server Operators
  • On the Summary of features being installed page, review the summary, and select Next.
  • On the Destination Folder page, select Next to use the default folder. Or, select Change to choose a different installation folder.
  • On the Logging Database Information page, leave the default configuration, and then select Next.
    • Database Server Name: The default value is the server name (name of the computer that the BizTalkMgmtDb database resides – you cannot change this value.).
    • HL7 Database name: Enter the name of the database that contains the data for your BTAHL7 solution, or accept the default setting, which is BTAHL7
      • You must use the ANSI-ASCII character set per database requirements; BTAHL7 does not support other character sets.
  • On the Ready to Install the Program page, select Install.
  • On the InstallShield Wizard Completed page, select Finish to complete.

RIP Howard!

The post In memory of Howard S. Edidin – How to install BizTalk Server 2020 Accelerator for HL7 in a standalone machine appeared first on SANDRO PEREIRA BIZTALK BLOG.

What do I need to do to start developing stateful or stateless workflows – Azure Logic Apps (Preview)? (Part I)

What do I need to do to start developing stateful or stateless workflows – Azure Logic Apps (Preview)? (Part I)

Microsoft Logic Apps Team recently announced a public preview of the new Logic Apps runtime. This new release adds several new features to Azure Logic Apps, including:

  • Development improvements
    • Full Logic Apps designer support in VS Code;
    • Local project support;
    • New Logic Apps Designer;
  • Hosting Flexibility – ability to run Logic apps workflows where you need to, including on-premises and edge environments
    • Run local (i.e. on my dev box);
    • Deploy to Azure or run containerized in Docker or Kubernetes environments;
  • Performance improvements
    • Stateless mode for low latency – better performance for request/response scenarios;

To create Logic Apps stateful or stateless workflows, you need to use Visual Studio Code and the Azure Logic Apps (Preview) extension – at the moment, there is no other way.

Prerequisites

To be able to use all capabilities of the Azure Logic Apps (Preview) extension for Visual Studio Code, you need:

  • To have Visual Studio Code 1.31.0 (January 2019) or later and you need the following VS Code extensions:
  • An Azure subscription or sign up for a free Azure account.
  • Microsoft Azure Storage Emulator 5.10 tool – This tool is necessary to have the full Logic Apps designer support in VS Code.
  • And finally, you need to install through the Microsoft Installer (MSI) the Azure Functions Core Tools, either version 3.0.2931 or 2.7.2936. These tools include a version of the same runtime that powers the Azure Functions runtime that runs in Visual Studio Code.

Install additional VS Code extensions

To start with, first, you must install the additional VS Code extension from the marketplace. To accomplish that, we need to:

To make sure that all the extensions are correctly installed, reload or restart the VS Code.

Install the Azure Storage Emulator 5.10 tool

To install the Azure Storage Emulator 5.10 tool, follow these steps:

  • Download the tool here: Azure Storage Emulator 5.10 and execute the microsoftazurestorageemulator.msi file.
  • On the Welcome to the Microsoft Azure Storage Emulator – v5.10 Setup Wizard screen, select Next.
  • On the Change, repair, or remove installation screen, select Repair.
  • On the Ready to repair Microsoft Azure Storage Emulator – v5.10 screen, select Repair.
  • On the Completed the Microsoft Azure Storage Emulator – v5.10 Setup Wizard screen, select Finish.

Install the Azure Functions Core Tools

To install the Azure Functions Core Tools, follow these steps:

  • On the End-User License Agreement screen, accept the terms and select Next.
  • On the Destination Folder screen, leave the default, and select Next.
  • On the Ready to install Microsoft Azure Functions Core Tools – 3.0.2931 (x64) screen, select Install.
  • On the Completed the Microsoft Azure Functions Core Tools – 3.0.2931 (x64) Setup Wizard screen, select Finish.

Install Azure Logic Apps extension for Visual Studio Code

To accomplish that, we need to:

  • After installing this extension, you will find the two Azure Logic Apps (Preview) section of the Explore section of the VS Code, but the first thing you need to do is to Sign in to Azure…

Once again, to make sure that this extension is correctly installed, reload or restart the VS Code.

Set up VS Code Azure Logic Apps (preview) extension

For everything to work correctly, you need to make sure that the following two properties are correctly configured:

  • Azure Logic Apps V2: Panel Mode
  • Azure Logic Apps V2: Project Runtime

To do that, you need:

  • Open your VS Code, and on the File menu, go to Preferences, and then Settings.
  • On the User tab, go to > Extensions > Azure Logic Apps (Preview).
  • Check if the Enable panel mode option is selected on Azure Logic Apps V2: Panel Mode property. Otherwise, please enable it.
  • Under Azure Logic Apps V2: Project Runtime, set the version to ~3 or ~2, based on the Azure Functions Core Tools version that you installed earlier.
    • In our case: 3
    • If you want to use the Inline Code action for running JavaScript code, make sure that you use Project Runtime version 3 because the action doesn’t support version 2. Also, this action currently isn’t supported on Linux operating systems.

In the next blog post, we will explain how you can create your first Logic Apps (Preview) project. Stay tuned!

The post What do I need to do to start developing stateful or stateless workflows – Azure Logic Apps (Preview)? (Part I) appeared first on SANDRO PEREIRA BIZTALK BLOG.

What do I need to do to start developing Logic Apps from Visual Studio?

What do I need to do to start developing Logic Apps from Visual Studio?

Azure Logic Apps Tools is available for Visual Studio 2019, 2017, and 2015 Community edition or greater and will allow you to design and deploy your logic apps from within Visual Studio. The Logic App designer integrates with the current Azure Resource Group project so you can seamlessly work with resource deployments that include Logic Apps.

Although this tool is officially supporting three versions of Visual Studio, I will advise you to install it only on Visual Studio 2019 and not in older versions. At some point, they will be officially removed or discontinued.

Prerequisites

  • Visual Studio 2019, 2017, or 2015 – Community edition or greater;
  • Visual Studio Tools for Azure: Azure SDK, tools, and projects for developing cloud apps and creating resources using .NET Core and .NET. Important also to create hybrid solutions without having the need for another development environment.
    • In the Visual Studio installer, install Visual Studio (or modify an existing installation). Make sure the Azure development and ASP.NET and web development workloads are selected.
  • and run the following command:  Install-Module -Name Az

Note: of course, for this or any other approach describe above, you need an Azure subscription or sign up for a free Azure account.

Install Azure Logic Apps Tools for Visual Studio 2019

AftAfter you install the prerequisites, this is a straightforward process. To accomplish that, we need to:

  • Open your Visual Studio, on the entry screen select the option Continue without code ->
  • Then on the menu, navigate to Extensions > Manage Extensions
  • Select Online and search for Logic Apps
  • The add-in will be listed in the search results section. Click Download to download and install the add-in. You need to close your Visual Studio in order to begin installing this extension. 
  • On the VSIX Installer screen
    • Make sure that the correct version of Visual Studio is selected.
    • Click Install or Modify. This will download and install the add-in to your version of Visual Studio.
  • At the end select Close.

Creating a Visual Studio Logic App project

The Logic Apps designer integrates with the current Azure Resource Group project. That saying, you will not find any Logic App template from the list of templates. Instead, we need to create an Azure Resource Group project to get started and to do that, we need:

  • Open Visual Studio and on the Create a new project panel, select C# -> Azure -> Cloud, or select for Azure Resource Group;
    • Select Azure Resource Group from the template list;
  • On the Configure your new project panel, give a proper Project name, Location, Solution name, and leave the Framework as .Net Framework 4.7.2 and select Create.
  • Finally, on the Select Azure Template panel, from the Visual Studio Templates list, select the Logic App template and select OK.

This will create an empty Visual Studio Logic App solution. Now on the Visual Studio solution:

  • Right-click on the LogicApp.json file and select Open With Logic App Designer
  • This will open a Logic App Properties window, where you need to:
    • Define the credentials to authenticate on the Azure subscription;
    • Define the Subscription and Resource Group where you want to create these resources;
    • Define if you want the Location to be in the same Region or in an Integration Service Environment (ISE);
  • And then select OK.

This will embed the Logic App designer inside the Visual Studio.

Now you need to select a common trigger, a template, or use a blank Logic App to start creating your business process.

The post What do I need to do to start developing Logic Apps from Visual Studio? appeared first on SANDRO PEREIRA BIZTALK BLOG.

COLLABDAYS LISBON 2020 | October 10, 2020 | Power Automation: Best practices, tips, and tricks

SharePoint Saturday Lisbon has been rebranded, and it is now Collabdays Lisbon. Don’t worry, it is still organized by the same people and maintains the same spirit as in previous years.

Collabdays Lisbon is a community-driven event dedicated to all that is great about SharePoint and now also: Office 365 and Azure. At the moment, due to the COVID-19 pandemic, this will be a one-day free virtual event and I will be there presenting a session about Power Automation: Best practices, tips, and tricks

Power Automation: Best practices, tips, and tricks

As I mentioned before, my session will be all about best practices and small tips and tricks that we can apply to our Power Automate flows. For those reasons, I would like you to invite you to join me at the Collabdays Lisbon virtual event next Saturday, October 10, 2020.

AbstractPower Automation: Best practices, tips and tricks

In this session, we will do a reflection to your existing Power Automation flow’s and when thru a list of must-have best practices, tips, and tricks that will allow you to build more reliable and effective flows. At the same time, these will allow you to be more productive and document your flow’s from the beginning.

Join us and reserve your presence at the Collabdays Lisbon virtual event, it is free!

The post COLLABDAYS LISBON 2020 | October 10, 2020 | Power Automation: Best practices, tips, and tricks appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Solution Deploy Error: Error saving map. Stored procedure returned non-zero result.

BizTalk Solution Deploy Error: Error saving map. Stored procedure returned non-zero result.

In my infamous crusade to document any BizTalk Server error that I have already come across, here is another error, warnings, cause, and solutions blog post, this time joining another of my favorite topic: Maps.

While trying to deploy a BizTalk Server solution – MSI – into production. While trying to import the BizTalk Application from the .msi file into the BizTalk group by using the BizTalk Server Administration Console by:

  1. Opening the BizTalk Server Administration Console for the instance of BizTalk Server into which you want to import the application. Click Start, click All Programs, click Microsoft BizTalk Server 20xx, and then click BizTalk Server Administration.
  2. In the console tree, expand BizTalk Server Administration, and then expand BizTalk Group.
  3. Right-click Applications, point to Import and then click MSI file.

I came across this error during the progress phase:

Failed to add resource(s). (mscorlib)
– Change requests failed for some resources. (Microsoft.BizTalk.ApplicationDeployment.Engine)
– BizTalkAssemblyResourceManager failed to complete end type change request. (Microsoft.BizTalk.ResourceManagers)
Failed to deploy map “FULLY-QUALIFIED-MAP-NAME”. Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present. (mscorlib)
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present. (Microsoft.BizTalk.Deployment)

Error saving map. Stored procedure returned non-zero result

Cause

In previous versions of BizTalk Server, mainly 2010 and 2009, a bug was reported related to this issue. That problem occurred because BizTalk was trying to deploy the mapper assembly before the schema assembly. The solution for that case was installing the cumulative update 4 (or above) for BizTalk Server 2010 or the cumulative update 7 for BizTalk Server 2010.

Nevertheless, I was using BizTalk Server 2016, so that wasn’t the case. Luckily for us, the error provides a piece of clear evidence where the error is happening: FULLY-QUALIFIED-MAP-NAME.

To understand this issue, I went to my dev environment and opened that solution to analyze that specific map, mainly to know which schemas were being used. I then realize that one of the schemas was from an external assembly, a common schema that could be used by several applications.

The cause of this error was precisely that. I used a reference schema (external DLL) inside my map outside the project I was trying to deploy. But that assembly – DLL containing the map’s schema – was not yet deployed in the environment.

Solution

Make sure to deploy all the reference assemblies, special the ones outside your visual studio solution, are deployed before you deploy your solution. And in this case, make sure that all schemas are deployed before installing the maps.

But once again, the critical point here is to make sure to deploy all schemas outside your solution that are being used. Because, even if we use specific projects for maps and schemas inside our solution, BizTalk Server is smart enough to see the dependencies and deploy it accordingly.

After installing the external assembly that contains the schema used by that map, I was able to deploy the BizTalk project into production successfully.

The post BizTalk Solution Deploy Error: Error saving map. Stored procedure returned non-zero result. appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist

BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist

Following my previous blog post, Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist, and once I was able to solve that last issue, I was surprised by a brand new communication error between BizTalk Server and ORACLE, fortunately for me, this time with a more explicit error message: ORA-00942: table or view does not exist.

The Messaging Engine failed to add a receive location “ORACLE_RECEIVE_LOCATION_NAME” with URL “oracledb://SERVER_ADDRESS:PORT_NUMBER/SERVICE_NAME/Dedicated?PollingId=polling_id” to the adapter “WCF-Custom”. Reason: “Microsoft.ServiceModel.Channels.Common.MetadataException: Metadata resolution failed for OperationId: “http://Microsoft.LobServices.OracleDB/2007/03/POLLINGSTMT“. —> Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist
   at Oracle.DataAccess.Client.OracleException.HandleErrorHelper(Int32 errCode, OracleConnection conn, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, String procedure, Boolean bCheck, Int32 isRecoverable)
   at Oracle.DataAccess.Client.OracleException.HandleError(Int32 errCode, OracleConnection conn, String procedure, IntPtr opsErrCtx, OpoSqlValCtx* pOpoSqlValCtx, Object src, Boolean bCheck)
   at Oracle.DataAccess.Client.OracleCommand.ExecuteReader(Boolean requery, Boolean fillRequest, CommandBehavior behavior)
   at Oracle.DataAccess.Client.OracleCommand.ExecuteReader(CommandBehavior behavior)
   at Microsoft.Adapters.OracleCommon.OracleCommonUtils.ExecuteReader(OracleCommonConnectionWrapper connection, String commandText, IEnumerable`1 parameters, CommandBehavior commandBehavior, IOracleAdapterCommonBindingProperties properties, OracleCommonExecutionHelper executionHelper)
   — End of inner exception stack trace —
   at Microsoft.Adapters.OracleDB.OracleCommonMetadataResolverHandler.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
   at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
   at Microsoft.Adapters.OracleDB.OracleDBInboundContract..ctor(OracleDBConnection connection, IOracleCommonUDTHelper oracleUdtHelper, MetadataLookup metadataLookup)
   at Microsoft.Adapters.OracleDB.OracleDBConnection.Microsoft.ServiceModel.Channels.Common.IConnection.BuildHandler[TConnectionHandler](MetadataLookup metadataDictionary)
   at Microsoft.ServiceModel.Channels.Common.Design.ConnectionPool.GetConnectionHandler[TConnectionHandler](Guid clientId, TimeSpan timeout, MetadataLookup metadataLookup, String& connectionId)
   at Microsoft.ServiceModel.Channels.Common.Channels.AdapterChannelListener`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)”.

Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist

Once again, followed by the following error:

The receive location “ORACLE_RECEIVE_LOCATION_NAME” with URL “oracledb://SERVER_ADDRESS:PORT_NUMBER/SERVICE_NAME/Dedicated?PollingId=polling_id” is shutting down. Details:”The Messaging Engine failed while notifying an adapter of its configuration. “.

The Messaging Engine failed while notifying an adapter of its configuration

Of course, these two errors are related, but the first one is the one that has more precise information regarding what is happening.

Cause

As the error message describes, the table or the view you are trial to communicate doesn’t exist on the ORACLE database you are trying to communicate.

Solution

I wish all problems were that simple!

To solve this issue, you need to contact your ORACLE team and make sure that they properly deploy the missing databases, tables, or views.

The post BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: ORA-00942: table or view does not exist appeared first on SANDRO PEREIRA BIZTALK BLOG.

October 5, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS

October 5, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS

Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?

Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.

Microsoft Announcements and Updates

Community Blog Posts

Videos

Podcasts

How to get started with iPaaS design & development in Azure?

Feedback

Hope this would be helpful. Please feel free to reach out to me with your feedback and questions.

BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client

BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client

I’m back to one of my favorite topics, error, warnings, cause, and solutions blog post – still have plenty of them in my backlog to be published. I recently installed a new BizTalk Server solution in production in one of my clients that integrate with ORACLE. When I try to activate the Oracle Receive ports, I got the following error inside Event Viewer: 

The Messaging Engine failed to add a receive location “ORACLE_RECEIVE_LOCATION_NAME” with URL “oracledb://SERVER_ADDRESS:PORT_NUMBER/SERVICE_NAME/Dedicated?PollingId=polling_id” to the adapter “WCF-Custom”. Reason: “System.TypeInitializationException: The type initializer for ‘Oracle.DataAccess.Client.OracleConnection’ threw an exception. —> Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
 at Oracle.DataAccess.Client.OracleInit.Initialize()
   at Oracle.DataAccess.Client.OracleConnection..cctor()
   — End of inner exception stack trace —
   at Oracle.DataAccess.Client.OracleConnection..ctor()
   at Microsoft.Adapters.OracleDB.OracleDBBinding.Initialize()
   at Microsoft.Adapters.OracleDB.OracleDBBinding.CreateBindingElements()
   at System.ServiceModel.Channels.CustomBinding.SafeCreateBindingElements(Binding binding)
   at System.ServiceModel.Channels.Binding.CanBuildChannelListener[TChannel](BindingParameterCollection parameters)
 at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfUtils.IsQueuedReceive(Binding binding)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.BtsServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnBeginOpen()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint.Enable()
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiveEndpoint..ctor(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)”.

The provider is not compatible with the version of Oracle client

Followed by the following error:

The receive location “ORACLE_RECEIVE_LOCATION_NAME” with URL “oracledb://SERVER_ADDRESS:PORT_NUMBER/SERVICE_NAME/Dedicated?PollingId=polling_id” is shutting down. Details:”The Messaging Engine failed while notifying an adapter of its configuration. “.

The Messaging Engine failed while notifying an adapter of its configuration

Of course, these two errors are related, but the first one is the one that has more precise information regarding what is happening.

Cause

Usually, these types of problems occur when you don’t have the correct versions of the Oracle Data Provider for .NET (ODP.NET) and the Oracle client, which are part of the Oracle Data Access Components (ODAC). Still, it may occur, or similar errors, for other several reasons like for example:

  • The Oracle Data Provider DLLs are not properly registered into GAC.
  • Mistmach installation versions between the components, for example between Oracle Client and ODP.NET.
  • Mistmach installation versions between 32bit or 64bit ODAC components.

Unfortunately, kind of, none of the above reasons were justifying my issues since I already had several ORACLE receive locations, running with success on the environment.

When I investigate the other running ports, I realized that all of them were running the 64-bit Host Instance. And this one that was getting problems was running in 32-bit Receive Host Instance. I then realize that ODAC 32-bit components were not properly installed in production.

Even if you don’t use it, it is essential to have always the 32, and 64-bit of each adapter installed correctly in your environment. If that’s not possible, make sure to associate the 32, and 64-bit Receive Handlers and Send Handlers for each adapter accordingly.

Solution

In my case, the solution was simple, since I had already several ORACLE receive location successfully running in the environment. I have to access the receive location and configure the Receive Handler to be the 64-bit Host Instance.

After this modification, the problem was gone, and I could pull data from the ORACLE database. Otherwise, make sure to install the necessary 32-bit or 64-bit ODAC components correctly.

The post BizTalk WCF-ORACLEDB Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client appeared first on SANDRO PEREIRA BIZTALK BLOG.