In my case, the solution was simple, since I had already several ORACLE receive location successfully running in the environment.
If that’s not possible, make sure to a ssociate the 32, and 64-bit Receive Handlers and Send Handlers for each adapter accordingly. I then realize that ODAC 32-bit components were not properly installed in production.Įven 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. And this one that was getting problems was running in 32-bit Receive Host Instance. When I investigate the other running ports, I realized that all of them were running the 64-bit Host Instance. 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. 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. Mistmach installation versions between 32bit or 64bit ODAC components.Mistmach installation versions between the components, for example between Oracle Client and ODP.NET.The Oracle Data Provider DLLs are not properly registered into GAC.Still, it may occur, or similar errors, for other several reasons like for example: NET (ODP.NET) and the Oracle client, which are part of the Oracle Data Access Components (ODAC). Usually, these types of problems occur when you don’t have the correct versions of the Oracle Data Provider for. Of course, these two errors are related, but the first one is the one that has more precise information regarding what is happening. > : The provider is not compatible with the version of Oracle clientĪt .Initialize()Īt .cctor()Īt .ctor()Īt .Initialize()Īt .CreateBindingElements()Īt .SafeCreateBindingElements(Binding binding)Īt .CanBuildChannelListener(BindingParameterCollection parameters)Īt .(Binding binding)Īt .()Īt ()Īt (TimeSpan timeout)Īt .Open(TimeSpan timeout)Īt .()Īt .(BizTalkEndpointContext endpointContext, IBTTransportProxy transportProxy, ControlledTermination control)Īt .Runtime.WcfReceiver`2.AddReceiveEndpoint(String url, IPropertyBag adapterConfig, IPropertyBag bizTalkConfig)”. Reason: “System.TypeInitializationException: The type initializer for ‘’ threw an exception. 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”. When I try to activate the Oracle Receive ports, I got the following error inside Event Viewer: I recently installed a new BizTalk Server solution in production in one of my clients that integrate with ORACLE. 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.