An Automated Tool for Collecting PSSDiag BizTalk Traces Using Event Logs
Often, users encounter intermittent event log errors from BizTalk that require further investigation using a BizTalk PSSDiag trace. However, since the timing of the next occurrence is unpredictable, troubleshooting becomes challenging. In such scenarios, a tool is needed to continuously collect PSSDiag traces until the error reoccurs, at which point the tool can automatically stop tracing and save the output. To address this need, I’ve developed a tool that automates this process based on user requirements. PSSDiag for BizTalk is a specialized diagnostic data collection tool tailored for troubleshooting BizTalk Server environments. Built as an extension of PSSDiag (Product Support Services Diagnostics), a widely used tool for diagnosing Microsoft SQL Server issues, it collects a comprehensive set of logs and diagnostic data specific to BizTalk. This includes information crucial for identifying and resolving performance, connectivity, or configuration issues. The tool runs from a console interface, and data collection can be stopped manually by pressing Ctrl+C. I have developed a console application PSSDiagCollector that launches PSSDiag to monitor the event log and automatically stops the PSSDiag collection once a specific event is detected. You can download the tool from this GitHub repository: https://github.com/huidongl/PSSDiagCollector The PSSDiagCollector.exe must be saved in the same folder as PSSDiagForBizTalk. Users can open a command prompt, navigate to the PSSDiagForBizTalk directory, and run PSSDiagCollector from there. The command can specify the Event ID, Event Source, or Event Type to capture, as well as the number of events required to stop the collection. Additionally, users can set a delay (in seconds) before stopping the trace. Detailed instructions for using the tool to collect PSSDiag BizTalk traces can be found in the repository. Run the following command to begin the collection: PSSDiagCollector.exe -eid <EventID> -c <EventCount> -p <PauseDuration> -es "<EventSource>" -lc "<LogCategory>" For example: PSSDiagCollector.exe -eid 7195 -c 3 -p 30 -es "BizTalk Server" -lc "Application" Please make sure to configure the Trace Type, Keep the last _ trace files in the Initialize.exe before running this tool to avoid the trace file being filled up.
BizTalk Server 2020 CU2 is available for download
CU2 for BizTalk Server 2020 is now available for download. For details on fixes and download link, please follow the master KB: https://support.microsoft.com/help/5003151 You may want to bookmark this index page for updates related to BizTalk Server: https://support.microsoft.com/help/2555976 As with CU1, the EN download is available by default. All other language packages will be made available on need basis. If a download is not available for the supported BizTalk language that you need, please contact us for the same. As a quick reminder, for BizTalk Developer Tools please also update/install version 3.13.2.0 of the BizTalk Server Visual Studio extension in addition to installing the CU package. The extension can be installed from https://marketplace.visualstudio.com/items?itemName=ms-biztalk.BizTalk or from within Visual Studio - Manage Extensions. Please note that we have not updated the extension since CU1 so you can skip this step if you have already installed it previously.
Recovering SAP BAPI Transactions with Custom Pipelines
We wrap up the series of articles on SAP BAPI transactions by presenting, step by step, another implementation of BAPI sales orders received in batches and created in SAP. The design is a combination of the previous concepts into a solution that leverages BizTalk pipeline features such as batch processing, XML disassembly, XML validation, and recoverable interchange processing (RIP).
BizTalk projects build is available in Azure Pipelines Agent pool
BizTalk Server 2020 provide the new feature of automatic deployment using Azure DevOps, one heavy step for setting up the pipelines is setup build agent pool - Configure automatic deployment with Visual Studio Team Services - BizTalk Server | Microsoft Docs, which now can be simplified to use "Azure Pipelines" as Agent pool and "windows-2019" agents.
