Skip to main content

Hi,

We're currently on FSM 5.7u11 and trying to force the Server and Client to use the TLS1.2 protocols.
Our Infrastructure team has done this via IISCrypto and group policies.

Whilst testing we're seeing some of the MPM's return an exception.

        <severity>ERROR</severity>
        <message>eDBNETLIB][ConnectionOpen (SECCreateCredentials()).]SSL Security error.</message>
        
We have installed and updated a Microsoft OLE DB Driver for SQL Server to use: "Provider=MSOLEDBSQL19" onto the Application server to allow it to communicate with the DB for a specific process.
This resolved one issue, but we're still seeing more exceptions when testing in the client and calling MPM's.
        
The feedback we got back from support was that this line of code 'ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls;' is what is needed to support TLS1.2, and that it is present in FSM5.7u11.

Could this therefore be an issue with the CustomeAssemblies we have, and would they need updating?

Regards

Ady

@AdrianEgley ,

 

Could this therefore be an issue with the CustomeAssemblies we have, and would they need updating?

 

if TLS communication channels are OK and FSM client( smart / web ) is functioning well, you will not get any issue with custom assembilies. 

 

Custm assemblies are customization done for server side. hence, it dynamically bind with server app while apppool is executing. so it doesnt do any effect for custom assemblies. but if you upgrade the FSM version to latest than the version which you build the custom assemblied, you should build custom assemblies agains latest version. if not, you will get runtime issues due to dll versioning. 

 

Thank You

Isuru

Reply


Terms & ConditionsCookie settings