Archived Content: This information is no longer maintained and is provided "as is" for your convenience.
Summary
Sitescope server port getting changed
Question
After daily scheduled restart, it seems SiS is not starting properly and server ports in master.config are getting changed. No other process seems to be consuming those ports on sitescope server. We are getting below alert.SiteScope Server Port ChangedThe server port for SiteScope has changed to 8890The old port (8889) could not be opened. The error message was: java.net.BindException: Address already in use: JVM_BindIn error log , we can see below error when sitescop is trying to start.2018-07-27 09:13:27,741 [localhost-startStop-1] (SiteScopeShutdown.java:51) INFO - Shutting down SiteScope reason Tomcat is going down (destroy of InitSiteScope HttpServlet)...
Answer
This problem is caused by July Windows Update, or KB4338823 for this customer's OS version.
We recomend to involve the Windows admin/support to fix it.
https://community.softwaregrp.com/t5/SiteScope-User-Discussions/SteScope-Port-get-changed-automatically/td-p/1660632
https://comm.support.ca.com/kb/error-javanetbindexception-address-already-in-use-jvmbind-in-tomcat-logs-when-starting-service-desk-services/kb000035805
https://serverfault.com/questions/922066/apache-2-4-is-unkillable-and-cant-be-stopped-on-windows-server
You’ll find additional information on the above links.