Resolution. This problem is fixed in the following cumulative update for BizTalk Server: Cumulative Update 2 for BizTalk Server 2020. References. For information about the service packs and cumulative update list for BizTalk Server, see the following article in the Microsoft Knowledge Base:

High memory usage by the Message Queuing service when you perform a remote transactional read on a Message Queuing 5.0 queue in Windows 7 or in Windows Server 2008 R2 - Microsoft Support.

Message: Watson report about to be sent for process id: 33564, with parameters: E12IIS, c-RTL-AMD64, 15.00.1178.004, msexchangerepl, M.Exchange.Rpc, M.E.R.A.AmRpcClient.IsRunning, System.OutOfMemoryException, da11, 15.00.1178.004.

SQL Server 2019 on Windows. Symptoms. When you perform Data Manipulation Language (DML) operations on an External Table that's using the PolyBase Generic ODBC connector in SQL Server 2019, you may see the following error: Msg 7320, Level 16, State 110, Line LineNumber.

If you are having issues installing or updating Gaming Services on your PC, or if you are noticing that the Xbox app for PC is launching with missing content, you may want to download and run the Gaming Services Repair Tool for PC.

This update introduces an improvement to the Service Broker in SQL Server 2012 and SQL Server 2014. Before you apply this update, the maximum number of threads that the Service Broker uses to send messages to remote servers is double the number of CPUs that run the Service Broker.

From the administrative tools, start Internet Information Services (IIS) Manager. Select Application Pools, right-click each of the following pools, and then click Recycle: MSExchangeServicesAppPool. MSexchangeOWAAppPool. MSExchangeRestAppPool. Fixes an issue in which MSExchangeApplicationLogic Event 3018 is logged in Exchange Server 2013 and 2016.

Symptoms. When you use Queue Veiwer or run the Get-Message cmdlet to view the properties of a poison message in a Microsoft Exchange Server 2016 environment, the Edge Transport service (Edgetransport.exe) crashes. The crash causes messages in process to be moved to the poison queue unexpectedly.

The Exchange RPC Client Access service crashes when you send an email message in an Exchange Server 2010 environment - Microsoft Support. Exchange Server 2010 Enterprise Exchange Server 2010 Standard. Symptoms. Assume that you use a MAPI client such as Outlook 2003 in online mode in a Microsoft Exchange Server 2010 environment.

Status. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Describes a BizTalk Server issue that blocks the processing of a service message that has a type indicator of 21 in the SWIFT Message Pack. Provides a resolution.