News

Field Alert – Secure Gateway stops responding after Microsoft July 2018 Monthly Rollup

 

As a result of a bug in the Microsoft Monthly Rollup for July 2018, the Secure Gateway service in 15.1 and 15.2 stops responding.

This issue can also cause repeated 'ServerCommunicationFailure' alarms to be sent out from the system on version 11.1, 15.1 and 15.2.

 

Symptoms

  1. The Secure Gateway service cannot be started after machine reboot. The following error will be reported in the Event Viewer:

Address already in use: make_sock: could not bind to address 0.0.0.0:443 (same for port 80)

  1. When attempting to stop the Secure Gateway service, it will hang, remaining in the “Stopping” state
  2. Repeated alarms on 'ServerCommunicationFailure' when checking system alarm dashboard.

 

Solution

The bug is part of a Microsoft stand-alone security KB, as well as the Monthly Rollup package for July 2018. Fixes are already available, both stand-alone and the complete Rollup.

 

 

Original (faulty) Security only update (stand-alone)

Original (faulty) July 2018 Monthly Rollup

Updated Security only update (stand-alone)

Updated July 2018 Monthly Rollup

Windows 2008 R2

KB4338823

KB4338818

KB4345459

KB4338821

Windows 2012

KB4338820

KB4338830

KB4345425

KB4338816

Windows 2012 R2

KB4338824

KB4338815

KB4345424

KB4338831

 

Affected Product Versions

11.1, 15.1, 15.2 and respective Avaya versions

 

References

https://blogs.msdn.microsoft.com/psssql/2018/07/26/july-10-2018-windows-updates-cause-sql-startup-issues-due-to-tcp-port-is-already-in-use-errors/


Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: