Scribe Internal Database and TLS 1.2
Article ID: KB0078921
Updated On:
| Products | Versions |
|---|---|
| TIBCO Scribe Insight | 2 |
Description
Users are unable to access certain data in the TIBCO Scribe® Insight Scribe Internal Database where SQL server and the network are enabled for TLS 1.2 only.
A user reported an error while connecting to Dynamics CRM 2015 after they enforced the TLS 1.2 security policy and disabled backwards compatibility to TLS 1.0. The Adapter successfully connects to CRM, then the following error occurs when the Adapter queries the Insight Internal Database:
Error HRESULT E_FAIL has been returned from a call to a COM component.
The error occurs due to issues with the Microsoft OLE DB driver for SQL Server used by TIBCO Scribe® Insight. Specific to this case, the TIBCO Scribe® Insight Internal Database AdapterMetadata table (among others) contains a nvarchar(max) field that is not supported by the driver.
Any Adapter may generate some type of error in this TLS 1.2 configuration in that the problem occurs when the AdapterMetadata table is queried by the Adapter.
There are a number of other scenarios in which a similar error occurs. First, any table that contains the SQL nvarchar(max) datatype generates an error when accessed by TIBCO Scribe® Insight. Secondly, there is a problem using the driver within the VB6 language to access the Internal Database, so the Scribe Internal Database program, among others, fails.
A user reported an error while connecting to Dynamics CRM 2015 after they enforced the TLS 1.2 security policy and disabled backwards compatibility to TLS 1.0. The Adapter successfully connects to CRM, then the following error occurs when the Adapter queries the Insight Internal Database:
Error HRESULT E_FAIL has been returned from a call to a COM component.
The error occurs due to issues with the Microsoft OLE DB driver for SQL Server used by TIBCO Scribe® Insight. Specific to this case, the TIBCO Scribe® Insight Internal Database AdapterMetadata table (among others) contains a nvarchar(max) field that is not supported by the driver.
Any Adapter may generate some type of error in this TLS 1.2 configuration in that the problem occurs when the AdapterMetadata table is queried by the Adapter.
There are a number of other scenarios in which a similar error occurs. First, any table that contains the SQL nvarchar(max) datatype generates an error when accessed by TIBCO Scribe® Insight. Secondly, there is a problem using the driver within the VB6 language to access the Internal Database, so the Scribe Internal Database program, among others, fails.
Issue/Introduction
Users cannot connect to the Scribe Internal Database if the network is enabled for TLS 1.2 only.
Resolution
The connection to the Scribe Internal Database is made with an OLE DB driver which Microsoft has not updated to be compatible with TLS 1.2. They plan to release a new OLE DB driver in Q1 of 2018: https://blogs.msdn.microsoft.com/sqlnativeclient/2017/10/06/announcing-the-new-release-of-ole-db-driver-for-sql-server/
In the meantime, our recommendation is to install the Scribe Internal Database on a server that still has TLS 1.0 enabled.
UPDATE: This has been resolved with TIBCO Scribe® Insight 7.9.4. Review the release notes for instructions on how to properly upgrade and disable TLS 1.0. TIBCO Scribe ® Insight V7.9.4 Release Notes
In the meantime, our recommendation is to install the Scribe Internal Database on a server that still has TLS 1.0 enabled.
UPDATE: This has been resolved with TIBCO Scribe® Insight 7.9.4. Review the release notes for instructions on how to properly upgrade and disable TLS 1.0. TIBCO Scribe ® Insight V7.9.4 Release Notes
Feedback
Yes
No
Powered by
