We were experiencing this same problem on our Windows 7 desktops and Windows Server 2008R2 environments. SAP Note 2334025 - Windows Updates are causing issues in older versions of SAP Business One explains the issue, identifies the Windows Updates that cause the issue (for Windows 7 SP1 it is KB3161608), 2 possible workarounds, and 1 long term solution. Here are the options as described in the note:
1. Upgrade B1 to version 9.2 (long term solution)
2. Uninstall Windows Update KB3151608 (short term workaround)
3. Modify server.xml file on your SLD server by completing the following (also considered a short term fix):
1. Back up the server.xml file (C:\Program Files (x86)\SAP\SAP Business One ServerTools\System
Landscape Directory\tomcat\conf).
2. Open server.xml in <tomcat>\conf
3. Find element <Connector> in this xml.
4. Change attribute sslEnabledProtocols value to "TLSv1,TLSv1.1,TLSv1.2"
5. Add attribute ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_R C4_128_SHA,T
LS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WIT
H_AES_256_CBC_SHA256,
TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA"
6. After update the xml file, please restart SLD service.
7. Then logon to SAP Business One or try the installation of SAP Business One Server again.
Upgrades take a significant amount of time for my company, so I chose to go with option #3 and modified the SLD's server.xml file. All my systems now have the specific Windows Updates installed, but since I changed the server.xml file SAP is running as expected with no issues.
Hope this helps!
Heath Gardner
