locked
Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly. RRS feed

  • Question

  • Hi,
    We are facing issue in BizTalk 2010 837 Institutional claim process. The Error is “Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly”.

    We have used Custom Pipeline component to update the promoted property like MessageType. When we drop the XML File in Receive Location it generates the XML file through Pipeline but promoted property MessageType is not updated in Receive Location and throw the error as mentioned.

    We have the schema which is not duplicate as well as different version.

    Could you please help on this issue.
    Thanks in advance.

    Monday, January 5, 2015 7:35 AM

Answers

  • Hi Praveen ,

    The message type promotion should be done at  dissemble stage in your custom Pipeline component .  Have you verified Whether you are getting message with MessageType field is being populated in the context of them message . You can verify this by seeing the context of suspended message instance .

    Now what you can do is to to create a message in Orchestration with type as xmldocument . On first receive shape you can put a filter condition based on promoted message type.

    Thanks

    Abhishek

    • Proposed as answer by Angie Xu Friday, January 16, 2015 2:42 AM
    • Marked as answer by Angie Xu Monday, February 9, 2015 2:19 AM
    Monday, January 5, 2015 3:33 PM

All replies

  • HI Praveen ,

     Can you try debugging your Pipeline component here first , It usually happens when message type is not being properly set on the massage .

    pInMsg.Context.Promote("MessageType", 
      "http://schemas.microsoft.com/BizTalk/2003/system-properties", 
       messageType);

    I do suspect there is something wrong doing on with the Pipeline component you have developed which is not setting your message type .

    Added Pointer here : You could use an XmlDocument as the message type into an orchestration which means that ANY schema matches.  Maybe you could route it to that orch based on something else then.

    Use Seroter blog for this

    http://seroter.wordpress.com/2009/02/27/not-using-httpnamespaceroot-as-biztalk-message-type/

    Thanks

    Abhishek



    Monday, January 5, 2015 7:43 AM
  • Hi Praveen,

    I have seen this error popping up when you promote "Message Type" instead of "MessageType".

    Note that MessageType is one word property.

    the correct statement will be

    pInMsg.Context.Promote("MessageType", systemPropertiesNamespace, messageType);

    instead of

    pInMsg.Context.Promote("Message Type", systemPropertiesNamespace, messageType);

    Also ensure the namespace should be

    string systemPropertiesNamespace = @http://schemas.microsoft.com/BizTalk/2003/system-properties;

    Rachit


    Monday, January 5, 2015 9:16 AM
    Moderator
  • Thanks Abhishek. I will try this
    Monday, January 5, 2015 10:16 AM
  • Thanks Rachit. I will try this
    Monday, January 5, 2015 10:16 AM
  • Praveen,

    There are two issues here.

    Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly” issue is normally due to the deployment issues. This more often occurs when you have same schema with multiple version and this issue is due to the sequence/order in which these two schemas are deployed. If you run the following SQL query in your BizTalk management db replacing it with your target namespace of the schema deployed

    SELECT *
    FROM bt_XMLShare
    WHERE target_namespace like N'http://YourTaggetNameSpace'

    You shall see two version of the same schema listed and both of them should have Activate flag set to 1. If any of the schemas is set to 0, then you will have the above mentioned issues. This is due to the way the different versions of the schemas are deployed. You can undeply both the version, deploy them together or deploy the older version first and the later version later.

    And for another issue of custom property not updating the MessageType property, debug the pipeline component code. This issue has no direct impact to the above issue. If you you’re your Message Type to be updated and if it’s not getting changed, then debug the code and check why its not been updated.


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Monday, January 5, 2015 10:31 AM
  • Hi All,

    Thanks for your suggestions, I tried all the above solutions, but no luck.

    Monday, January 5, 2015 10:51 AM
  • Hi Praveen ,

    The message type promotion should be done at  dissemble stage in your custom Pipeline component .  Have you verified Whether you are getting message with MessageType field is being populated in the context of them message . You can verify this by seeing the context of suspended message instance .

    Now what you can do is to to create a message in Orchestration with type as xmldocument . On first receive shape you can put a filter condition based on promoted message type.

    Thanks

    Abhishek

    • Proposed as answer by Angie Xu Friday, January 16, 2015 2:42 AM
    • Marked as answer by Angie Xu Monday, February 9, 2015 2:19 AM
    Monday, January 5, 2015 3:33 PM