I have CA SDM 14.1 installed in my env. having following OS specification:
OS- Win 2k8 R2
Tomcat version- 7.0.6/7.0.23
After installing following window patches and rebooting the server, Application was working fine.
KB4338823,KB4338818,KB4338612 & KB4338423
Next day, post recycling the SDM service.... the SDM application webpage became inaccessible.
I have tried pdm_configure..but couldn't get luck.
The issue was ...All SDM service was running (confirmed by pdm_status) nut the web URL was not accessible.
when I uninstalled KB4338823,KB4338818,KB4338612 patches one by one..and rebooted the server after every patch uninstallation....I have marked that after uninstalling KB4338612(related to .NET 3.5.1) and rebooting the server when I start SDM service...the webpage was accessible.
Have anyone got this issue ? what could be the reason behind this strange behavior of SDM application?
Even after patching, the .NET 3.5.1 was active, then how could .NET affect SDM or is there any tomcat dependency?
This is a known issue on Microsoft's site for this patch:
Resolution is to install the August Security Only update KB 4345679.
Thanks for your quick response.
Can you elaborate,How this patch(KB4338612) actually affects to SDM?
What changes were preventing Application access?
When KB4338612 installed, the services could not start. Did you have the copy of pdm_tomcat.log? It may have the error message about "Failed to initialize end point associated with ProtocolHandler ["http-bio-443"]java.net.BindException: Address already in use: JVM_Bind <null>:443" or ["http-bio-8080"].
It depends on whether SSL is implemented or not.
More finding about the error "Failed to initialize end point associated with ProtocolHandler ["http-bio-443"]java.net.BindException: Address already in use: JVM_Bind <null>:443" caused by KB4338818 not from KB4338612. You have both installed. Check out the below web site about the error from KB4338818 and the fix.https://stackoverflow.com/questions/51666952/address-bind-exception-in-tomcat/51689982#51689982
Were you able to address this issue based on the information provided by johsc03 and Derek_Li ?
Issue has been identified asDerek_Li has specified the exact error from log files.
We are working on fix and will update once the suggested fix will work.