Server's Security Certificate Windows 7

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

I just had the same issue occur - I have Citrix running and none of my Citrix users could connect. Server is WIndows Server 2012 R2.

Windows update was KB3172614 that caused my issue.

HI,

this worked fine, i do this two times this day.

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.

A majority of my users are connecting through Citrix which is running Server 2012 R2. I had to uninstall Windows update KB3172614. Once I took this out and rebooted server all users were able to connect using Citrix.

My internal users (local to the SAP server) had not been affected only my Citrix users.

Keith H

Hi i do this 2 minutes ago.

I only replace the "cipher" variable in the file.

This is the file from a SAP version 9.0

-----------------------

<?xml version="1.0" encoding="utf-8" standalone="no"?>

<!--

Licensed to the Apache Software Foundation (ASF) under one or more

contributor license agreements. See the NOTICE file distributed with

this work for additional information regarding copyright ownership.

The ASF licenses this file to You under the Apache License, Version 2.0

(the "License"); you may not use this file except in compliance with

the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software

distributed under the License is distributed on an "AS IS" BASIS,

WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

See the License for the specific language governing permissions and

limitations under the License.

-->

<!-- Note: A "Server" is not itself a "Container", so you may not

define subcomponents such as "Valves" at this level.

Documentation at /docs/config/server.html

-->

<!-- Set to -1 to disable the shutdown port. -->

<Server port="-1" shutdown="SHUTDOWN">

<!--APR library loader. Documentation at /docs/apr.html -->

<Listener SSLEngine="off" className="org.apache.catalina.core.AprLifecycleListener"/>

<!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->

<Listener className="org.apache.catalina.core.JasperListener"/>

<!-- Prevent memory leaks due to use of particular java/javax APIs-->

<Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener"/>

<!-- JMX Support for the Tomcat server. Documentation at /docs/non-existent.html -->

<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"/>

<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"/>

<!-- Global JNDI resources

Documentation at /docs/jndi-resources-howto.html

-->

<GlobalNamingResources>

<!-- Editable user database that can also be used by

UserDatabaseRealm to authenticate users

-->

<Resource auth="Container" description="User database that can be updated and saved" factory="org.apache.catalina.users.MemoryUserDatabaseFactory" name="UserDatabase" pathname="conf/tomcat-users.xml" type="org.apache.catalina.UserDatabase"/>

</GlobalNamingResources>

<!-- A "Service" is a collection of one or more "Connectors" that share

a single "Container" Note: A "Service" is not itself a "Container",

so you may not define subcomponents such as "Valves" at this level.

Documentation at /docs/config/service.html

-->

<Service name="Catalina">

<!--The connectors can use a shared executor, you can define one or more named thread pools-->

<!--

<Executor name="tomcatThreadPool" namePrefix="catalina-exec-"

maxThreads="150" minSpareThreads="4"/>

-->

<!-- A "Connector" represents an endpoint by which requests are received

and responses are returned. Documentation at :

Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)

Java AJP Connector: /docs/config/ajp.html

APR (HTTP/AJP) Connector: /docs/apr.html

Define a non-SSL HTTP/1.1 Connector on port 8080

-->

<!--<Connector port="8080" address="0.0.0.0" protocol="org.apache.coyote.http11.Http11Protocol" redirectPort="8443" scheme="http"

secure="false" SSLEnabled="false" clientAuth="false" sslProtocol="TLS"

/>-->

<!-- A "Connector" using the shared thread pool-->

<!--

<Connector executor="tomcatThreadPool"

port="8080" protocol="HTTP/1.1"

connectionTimeout="20000"

redirectPort="8443" />

-->

<!-- Define a SSL HTTP/1.1 Connector on port 8443

This connector uses the JSSE configuration, when using APR, the

connector should be using the OpenSSL style configuration

described in the APR documentation -->

<Connector ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_RC4_128_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA" SSLEnabled="true" clientAuth="false" keystoreFile="C:\Program Files (x86)\SAP\SAP Business One ServerTools\Common\sapjvm_6\jre\bin\keystore.p12" keystorePass="AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAaD4Qly3DMkuhyClMO9GgggQAAAAOAAAASgBEAFAAQQBQAEkAAAADZgAAwAAAABAAAADKx+xtM9O+YLcXzspInt2sAAAAAASAAACgAAAAEAAAAJdQbC7kcNqEPdstLmlYCP8IAAAAASgn0VXrzmgUAAAAl67hr91++O1ITOLlRMD+Sce/Qvo=" keystoreType="PKCS12" maxThreads="150" port="30010" protocol="org.apache.coyote.http11.SLDHttp11Protocol" scheme="https" secure="true" sslProtocol="TLS"/>

<!-- Define an AJP 1.3 Connector on port 8009 -->

<!--

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />

-->

<!-- An Engine represents the entry point (within Catalina) that processes

every request. The Engine implementation for Tomcat stand alone

analyzes the HTTP headers included with the request, and passes them

on to the appropriate Host (virtual host).

Documentation at /docs/config/engine.html -->

<!-- You should set jvmRoute to support load-balancing via AJP ie :

<Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">

-->

<Engine defaultHost="localhost" name="Catalina">

<!--For clustering, please take a look at documentation at:

/docs/cluster-howto.html (simple how to)

/docs/config/cluster.html (reference documentation) -->

<!--

<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>

-->

<!-- The request dumper valve dumps useful debugging information about

the request and response data received and sent by Tomcat.

Documentation at: /docs/config/valve.html -->

<!--

<Valve className="org.apache.catalina.valves.RequestDumperValve"/>

-->

<!-- This Realm uses the UserDatabase configured in the global JNDI

resources under the key "UserDatabase". Any edits

that are performed against this UserDatabase are immediately

available for use by the Realm. -->

<Realm className="org.apache.catalina.realm.UserDatabaseRealm" resourceName="UserDatabase"/>

<!-- Define the default virtual host

Note: XML Schema validation will not work with Xerces 2.2.

-->

<Host appBase="webapps" autoDeploy="false" deployOnStartup="false" name="localhost" unpackWARs="false" xmlNamespaceAware="false" xmlValidation="false">

<Context docBase="sld" path="/sld">

<Resource auth="Container" driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver" factory="org.apache.tomcat.dbcp.dbcp.EncryptDataSourceFactory" maxActive="100" maxIdle="30" maxWait="10000" name="sld" password="AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAaD4Qly3DMkuhyClMO9GgggQAAAAOAAAASgBEAFAAQQBQAEkAAAADZgAAwAAAABAAAAB4fuvy4WnYc53TpZlstyNWAAAAAASAAACgAAAAEAAAAJRnU2XL5IoQrT6e9t1qIlIQAAAAoj8r0mULPWJHAN/Jp114ahQAAAAhbrQ041ZV6ksqLTyhZC/M7VHt7A==" type="javax.sql.DataSource" url="jdbc:sqlserver://SAP2\sapB1; DatabaseName=SLDModel.SLDData" username="AQAAANCMnd8BFdERjHoAwE/Cl+sBAAAAaD4Qly3DMkuhyClMO9GgggQAAAAOAAAASgBEAFAAQQBQAEkAAAADZgAAwAAAABAAAAA6npiREcp+u4L1KhgzViWpAAAAAASAAACgAAAAEAAAADnbmXZyOEQQJxRFiQIKmjAIAAAA1REiLWShpeQUAAAA+xynm6HCg+FwJPFjBbJ+C7cFb08="/>

<Manager pathname=""/>

</Context>

<Context docBase="ControlCenter" path="/ControlCenter"/>

<!-- SingleSignOn valve, share authentication between web applications

Documentation at: /docs/config/valve.html -->

<!--

<Valve className="org.apache.catalina.authenticator.SingleSignOn" />

-->

<!-- Access log processes all example.

Documentation at: /docs/config/valve.html -->

<!--

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"

prefix="localhost_access_log." suffix=".txt" pattern="common" resolveHosts="false"/>

-->

</Host>

</Engine>

</Service>

</Server>

I have done all of the server work adding the ciphers to server.xml and I have ONE workstation that can update and still access B1 but not any others. Is there anything that needs to be done on the clients as well?