SAP Business One certificate error in windows 10 21h2

[former_member789174]

I have a problem where one of our company computers has been updated to Windows 10 21H2 and when starting SAP B1 certificate error occurs: There is a problem with the server’s security certificate. The security certificate is not from a trusted certifying authority. SAP Business One is unable to connect to the server.

SAP B1 version is 9.1 PL:04 I tried this solution but it doesn't work and I cannot risk restarting the server using this solution. I also read that the cause of this error is windows update KB3163018 but I cannot see this update in the computer

Is there any solution to this problem?

[wenli_chen]

Hi lexda,

This is a known issue caused by windows update for old version of SAP Business One, as documented in SAP Note

2334025 - Security Certificate Errors When Logging On to SAP Business One

Please try to test and apply workaround in the SAP Note.

Workaround for SAP Business One 9.1:

1. Check the config.xml file (C:\Program Files (x86)\SAP\SAP Business One Server\B1_SHR\Config) and ensure the License server port is correct, such as 30000.
2. Back up the server.xml file (C:\Program Files (x86)\SAP\SAP Business One ServerTools\System Landscape Directory\tomcat\conf).
   On Linux the server.xml file can be found in the following location: /usr/sap/SAPBusinessOne/Common/tomcat/conf.
3. Open server.xml in <tomcat>\conf.
4. Find the element <Connector> in this xml.
5. Change the attribute sslEnabledProtocols value to "TLSv1,TLSv1.1,TLSv1.2"
6. Add a new attribute:

ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,

TLS_DHE_RSA_WITH_AES_256_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_256_GCM_SHA,TLS_DHE_RSA_WITH_AES_256_CBC_SHA256,TLS_DHE_RSA_WITH_AES_256_CBC_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256,

TLS_RSA_WITH_AES_128_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA384,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384,

TLS_RSA_WITH_AES_256_GCM_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA384,TLS_RSA_WITH_AES_256_CBC_SHA"

1. After updating the xml file, restart the SLD service.
2. Log on to SAP Business One, or try the installation of SAP Business One Server again.

For more information and discussions, please see the SAP Business One Application space on SCN, http://scn.sap.com/community/business-one/content.

Note: For SAP Business One 9.1, update winhttp DefaultSecureProtocols in order to enable TLS 1.0 accordingly to
https://support.microsoft.com/en-sg/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-sec...

If you are still experiencing an issue after using this workaround, please log an incident with SAP Business One Support.

Thanks & regards,

Relle

[christian_aichmair]

Thanks a lot, worked for me too !!!
After this changes, Win10 pro Client with latest Patches as of 2022-12-31 can connect,
and old Win7 Clients still can connect !

Thanks for sharing this !