SOLVED

Problem: Azure DevOps Agent CI Build of BizTalk Flat File Schema Results in Bad Schema in Assembly

%3CLINGO-SUB%20id%3D%22lingo-sub-1507026%22%20slang%3D%22en-US%22%3EProblem%3A%20Azure%20DevOps%20Agent%20CI%20Build%20of%20BizTalk%20Flat%20File%20Schema%20Results%20in%20Bad%20Schema%20in%20Assembly%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1507026%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20running%20a%20self-hosted%20Azure%20DevOps%20Agent%20to%20execute%20source%20compilation%20for%20BizTalk%202020.%20The%20source%20code%20from%20BizTalk%202013%20R2%20has%20been%20upgraded%20to%20Visual%20Studio%202019%20with%20BizTalk%202020%20Development%20Tools%20and%20SDK%20and%20the%20BizTalk%20Server%20Extension.%20When%20several%20positional%20Flat%20File%20schemas%20are%20compiled%20in%20a%20remote%20desktop%20session%20on%20our%20build%20servers%2C%20the%20assembly%20produced%20contains%20a%20correct%20XSD%20of%20the%20schema%20as%20viewed%20through%20the%20BizTalk%20Administration%20console.%20However%2C%20when%20the%20agent%20builds%20the%20assembly%2C%20the%20resulting%20embedded%20XSD%20has%20a%20consistent%20error.%20The%20annotations%20of%20every%20field%20elements%20is%20missing%20its%20%3CSTRONG%3Esequence_number%3C%2FSTRONG%3E%20attribute%20in%20the%26nbsp%3B%3CSTRONG%3E%3CFIELDINFO%3E%3C%2FFIELDINFO%3E%3C%2FSTRONG%3E%20element.%20This%20occurs%20for%20every%20field%20element%20in%20the%20flat%20file%20XSD%20in%20the%20resulting%20assembly%2C%20and%20leads%20to%20errors%20in%20pipeline%20processing%20in%20BizTalk%20Server%202020.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20attachment%20for%20side%20by%20side%20comparison%20of%20missing%20attribute.%20The%20screen%20shots%20come%20from%20the%20Schemas%20dialog%20in%20the%20BizTalk%20admin%20console.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20seen%20such%20behavior%20before%20when%20building%20with%20TFS%20or%20Azure%20DevOps%20agents%3F%20Is%20this%20specific%20to%20BizTalk%20flat%20files%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20an%20attempt%20to%20fix%20we%20logged%20onto%20a%20remote%20desktop%20session%20to%20the%20build%20servers%20with%20the%20service%20account%20under%20which%20the%20agents%20run.%20We%20opened%20VS2019%20and%20built%20the%20solution.%20This%20resulted%20in%20good%20schemas%20in%20the%20assembly.%20That%20proves%20there%20is%20nothing%20wrong%20with%20our%20server%20configuration%20for%20compiling%20BizTalk%20solutions%20and%20project.%20We%20then%20restarted%20the%20agent%20services%20and%20then%20started%20a%20new%20instance%20of%20our%20CI%2FCD%20pipeline.%20The%20compile%20produced%20the%20same%20bad%20XSD%20in%20the%20assembly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20help%20you%20can%20offer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1507026%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20DevOps%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EBizTalk%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVisual%20Studio%202019%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1568685%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%3A%20Azure%20DevOps%20Agent%20CI%20Build%20of%20BizTalk%20Flat%20File%20Schema%20Results%20in%20Bad%20Schema%20in%20Assemb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1568685%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658731%22%20target%3D%22_blank%22%3E%40toddob%3C%2FA%3E%26nbsp%3B%20This%20was%20fixed%20in%20BizTalk%20Server%202020%20CU1.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fzh-cn%2Fhelp%2F4538666%2Fcumulative-update-1-for-microsoft-biztalk-server-2020%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fzh-cn%2Fhelp%2F4538666%2Fcumulative-update-1-for-microsoft-biztalk-server-2020%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1568766%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%3A%20Azure%20DevOps%20Agent%20CI%20Build%20of%20BizTalk%20Flat%20File%20Schema%20Results%20in%20Bad%20Schema%20in%20Assemb%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1568766%22%20slang%3D%22en-US%22%3EYes.%20We%20opened%20a%20support%20incident%20and%20got%20the%20hotfix%20that%20is%20part%20of%20CU1.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

We are running a self-hosted Azure DevOps Agent to execute source compilation for BizTalk 2020. The source code from BizTalk 2013 R2 has been upgraded to Visual Studio 2019 with BizTalk 2020 Development Tools and SDK and the BizTalk Server Extension. When several positional Flat File schemas are compiled in a remote desktop session on our build servers, the assembly produced contains a correct XSD of the schema as viewed through the BizTalk Administration console. However, when the agent builds the assembly, the resulting embedded XSD has a consistent error. The annotations of every field elements is missing its sequence_number attribute in the <fieldinfo /> element. This occurs for every field element in the flat file XSD in the resulting assembly, and leads to errors in pipeline processing in BizTalk Server 2020. 

 

See attachment for side by side comparison of missing attribute. The screen shots come from the Schemas dialog in the BizTalk admin console.

 

Has anyone seen such behavior before when building with TFS or Azure DevOps agents? Is this specific to BizTalk flat files?

 

In an attempt to fix we logged onto a remote desktop session to the build servers with the service account under which the agents run. We opened VS2019 and built the solution. This resulted in good schemas in the assembly. That proves there is nothing wrong with our server configuration for compiling BizTalk solutions and project. We then restarted the agent services and then started a new instance of our CI/CD pipeline. The compile produced the same bad XSD in the assembly.

 

Thanks in advance for any help you can offer.

2 Replies
Highlighted
Best Response confirmed by toddob (New Contributor)
Highlighted
Yes. We opened a support incident and got the hotfix that is part of CU1.