After KB 4096417, the maxconnection property is ignored RRS feed

  • Question

  • In April, I had an executable (that I didn't write) that made RESTful calls to a remote web service.  It was only doing up to 2 concurrently and everything else had to wait for a slot to be available.  After I modified the machine.config to add the following:

          <add address="*" maxconnection="30" /> 

    Then it would allow up to 30 at a time.  Great.  But then we loaded KB4096417 and it now throttles all connections to just one at a time (not even the default 2).  If I un-install that KB, it goes back to the expected behavior.

    We're using Dynamics CRM 2016, and this is the CRM Asynchronous Service (CrmAsyncService.exe).  While we're using CRM I believe the problem is not specific to CRM.

    Has anyone else experienced this?  Does anyone know of a fix or workaround?

    Mike Power

    Wednesday, May 23, 2018 4:13 PM

All replies

  • Hi Michael Power,

    Thank you for posting here.

    Since your question is more related to web, please post your question in ASP.NET forum.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions.

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Wednesday, May 30, 2018 12:55 AM