You know that sometimes you find those projects that you feel it doesn’t like you… It’s a nightmare, I know, but I love it because it gives me a lot of content to write! And I’m currently in one of those situations where anything I try to accomplish, Visual Studio and BizTalk Server are trying to annoy me. So last week, while making some changes to an existing BizTalk Server project, I was continuously getting the following error:
Severity Code Description Project File Line Suppression State
Error #error: “Errors exist for one or more children.”
This is a familiar error that I spoke about many years ago: BizTalk Orchestration error: “Errors exist for one or more children.”
The solutions there are still valid, but there is another way! Maybe “This is the way” as my Mandalorian friends say!
Cause
Typically, this problem is usually associated with difficulties in Orchestration Designer “refactoring” or “graphical interpretation”, and in a certain way, it isn’t a “valid error”, ie, it doesn’t describe the real problem.
Usually, this error is followed by a red indicator on the shape. Still, in many situations, there are no visual errors on the Orchestration designer—no red indicator on shapes or any artifacts like ports, messages, correlations, and so on. In fact, this was our situation.
Solution
The easiest way to solve these problems is to:
- Right-click on the orchestration and choose the option Open With… and select XML (Text) Editor option.
- Scroll down, almost to the end of the file, where it starts like C# code, and remove all the lines #error “Errors exist for one or more children.”
- Save it. Optionally, you can reopen the orchestration with the Orchestration design and then try to compile.
You may get different issues/errors that will be a different story but the error in cause will be fixed.
Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son.
