Map contains a reference to a schema node that is not valid

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Map contains a reference to a schema node that is not valid

Viewing 1 reply thread
  • Author
    Posts
    • May 16, 2006 at 6:49 AM #13600
      community-content

        Hi,

        Exception Caught: The map contains a reference to a schema node that is not valid. Perhaps the schema has changed. Try reloading the map in the BizTalk Mapper. The XSD XPath of the node is: <local path>

        Why is this happening?

        Please help me.

        Many Thanks,
        Fred

      • May 16, 2006 at 9:50 AM #13601
        community-content

          Hi,

          Addition information.

          The schemas are located in another project (let’s say project A) while the Biztalk Map is located at another project (let’s say project B).

          Project B adds Project A for its reference.

          I tried some testing and I got this situation…

          When I create a Biztalk mapper in Project A, it was able to successfully validate the map, however when I try to create the same Biztalk mapper in Project B. It gives me the error.

          Why is this happening? Please help me out.

          Thanks in advance,
          Fred

          • May 17, 2006 at 3:44 AM #13602
            community-content

              Hi,

              I’ve already tried removing the reference to the project and re- adding it as a reference on the project. I’ve also re-compiled it before re-referencing it. Also my current situation is only 2 projects A and B.

              Why is this happening? Please help me.

              Thanks,
              Fred

              • May 26, 2006 at 2:21 AM #13603
                community-content

                  Hi NISHIL,

                  What do you mean by try adding a new Map in Project B… and then refer it to A? I don’t seem to understand this?

                  do you mean I just create a map and map it to Project A again and again until it doesn’t create an error?

                  Regards,
                  Fred

                  • May 26, 2006 at 5:34 AM #13604
                    community-content

                      Hi,

                      Here is what I found out but I still don’t have the solution for this one…

                      When I created a map from Biztalk Project A where the schema resides, the target tree rootnode would be like this…
                      <TrgTree RootNode_Name=\”Response\”><Reference Location=\”..\\..\\response.xsd\”/></TrgTree>

                      When I created a map from Biztalk Project B and include Biztalk Project A (where the schema resides), the target tree rootnode would be like this…
                      <TrgTree RootNode_Name=\”Response\”><Reference Location=\”A.Response\”/></TrgTree>

                      *Additional info that maybe helpful (A.Response contains other references from Biztalk Project A)

                      It seems okay eventhough the schema can be visually seen in the Biztalk Mapper but I think some parts of \”Schema Response\” from Biztalk Project A was not recognize in Biztalk Project B.

                      Is there any fixes that I need to include aside from Biztalk SP1? or are there any alternatives to solve this problem?

                      Thanks,
                      Fred

                      • May 16, 2006 at 4:27 PM #13605
                        community-content

                          Make sure project B is really referencing project A and not some prior test version of the same or similar map. Or just remove and reference the ProjectA in Project B – some times I have problems with the references (mostly likely user error). Also, I have had problems with nested schemas, for example A references B references C.
                          When you compile A, it puts B’s and C’s schemas in A’s \\bin.
                          But when you reference in D, you should reference B and C directly, not the B and C in A’s \\bin. Because if you recompile for example C and forget to recomiple A it can cause problems if you are reference the now out of date C in A’s \\bin.

                          Did that make any sense what-so-ever?

                          Neal

                          • May 26, 2006 at 2:38 PM #13606
                            community-content

                              Try just editing your .btm with a text editor. It’s a pain, but this seems to be needed in the following cases:
                              1) Change root element (or other elements not at bottom level)
                              2) Change target namespace
                              3) Move schema from one project to another

                              • May 19, 2006 at 9:21 AM #13607
                                community-content

                                  Just delete the Map and try adding a new Map in Project B… and then refer it to A.At times Maps dont refresh the XSLT when you refer it to the same Project again and again.

                  • Author
                    Posts
                  Viewing 1 reply thread
                  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.