IES 10901 Error

[Former Member]

After installing a MS SQL Server Patch, connection to the CMS stopped due to a critical error.

We had to upgrade the ODBC driver to Driver 11 for SQL Server. This allowed us to reconnect to CMS. Reports seem to be running on schedule, but they fail to get sent out.

We receive this error when the report fails:

Database error: [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(SECDoClientHandshake())..(IES 10901)

[Former Member]

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend you to read this overview:

https://community.sap.com/resources/questions-and-answers and to take our Q&A tutorial at: https://developers.sap.com/tutorials/community-qa.html.

With these tips you'll be able to prepare questions that draw responses from our members. The more details you provide, the more likely it is that members will be able to answer your question. Should you wish, you can revise your question by selecting Actions, then Edit. By adding a picture to your profile you encourage readers to respond: https://www.youtube.com/watch?v=46bt1juWUUM

Best,

Your SAP Community moderator

[denis_konovalov]

what product version and SQL versions are you using ?
Are you sure the combiunation of versions is supported ?

[Former Member]

BOXI 41 and SQL Server 2014

[DellSC]

Did you update the ODBC connection for your CMS database after you installed the new driver?

-Dell

[Former Member]

Yes, I stopped SIA and added the new ODBC connection to the CMS Database

Configuration.

[Former Member · Accepted solution]

This issue has been resolved.

We upgraded the ODBC Drivers to use the SQL Native ODBC drivers.

Reports are now running as expected.

Thanks to all who tried to help out.

[denis_konovalov]

4.1 supports SQL 2014 from SP4 only and you have to use SQL native driver 11

The error comes from SQL Server itself, so you can't fix it on BOE side.
See https://social.msdn.microsoft.com/Forums/en-US/8a6a3688-7d49-429d-a68c-05f46c4b33b5/unable-to-connec...

https://www.sqlnethub.com/blog/dbnetlib-connectionopen-secdoclienthandshake-ssl-security-error-resol...

As none of the versions you mentioned are supported by their vendors anymore - your best solution is to upgrade to supported versions of BOE and SQL Server.