WCF-Custom for Oracle post deployment issues. RRS feed

  • Question

  • Hi,

    We are using BizTalk 2013 CU1 (same issue existed on BizTalk 2009 CU3) and 

    WCF LOB Adaptor SDK SP2 x64 and MS Adaptor pack x64.

    We recently experienced some schemas not refreshing without serious manual intervention following and update of some assemblies for our Oracle feeds.

    After deployment  and a host instance restart, we found the error below on some receive locations where data was available to feed:

    The adapter "WCF_custom" raised an error message. Detail "Microsoft.ServiceModel.Channels.Common.MetadataException: Field "CASE_NBR" is not found in the metadata at Microsoft.Adaptors.OracleCommon.OracleStructuredTypeMetadata.GetMember(String name)

    After restarting the Host Instance again, this then resolved the issue. ?(Another way to resolve this is to stop and restart the receive location.)

    This issue would then repeat as first time data became available for each feed.

     After the stop and start of the receive location in question to problem went away.

    Anyone know why this happened and how we can prevent this in future?


    • Edited by WernerDT Monday, May 19, 2014 1:53 PM
    Tuesday, October 9, 2012 12:37 PM

All replies

  • Did you DB schema change while your BizTalk was running? It appears that the metadata cached did not match the metadata fetched from the server.

    -- Please mark as answered if this answers your question.

    Thursday, November 1, 2012 6:42 PM
  • I see this behaviour still continues in BizTalk 2013.

    On initial go-live of BizTalk 2013 we had no issues, but after first subsequent implementation that familiar issue was back and could be resolved in the same manner.

    All BizTalk receive and send ports are disabled/stopped during implementation.

    Host Instances are restarted as well.

    Once we switch it all back on, the same issues is back as mentioned in original post.

    Monday, May 19, 2014 1:49 PM
  • The only two circumstances I can think of that would cause this are:

    1. The Host restarts before the Deploy is complete

    2. The Receive Locations are in a Host that is not restart

    .Net, not BizTalk specifically, will cache Assemlies and Types so it's normal that just updating the file will not produce immediate changes in the app.

    Monday, May 19, 2014 2:01 PM