Troubleshooting
Problem
IBM Content Collector fails to connect to P8 Connector or SharePoint Connector when it uses a .NET API Framework due to Transport Layer Security (TLS) protocols.
Symptom
The following errors are reported in the Content Collector P8 Connector log or CTMS user interface log:
Error 1:
TRANSPORT_WSI_NETWORK_ERROR: A network error occurred when processing a Web service request or response. See the nested exception for specific details.. Reason: A network error occurred when processing a Web service request or response. See the nested exception for specific details.. Reason: Could not establish secure channel for SSL/TLS with authority ‘XXX'.. Reason: The request was aborted: Could not create SSL/TLS secure channel.
Error 2:
The underlying connection was closed: An unexpected error occurred on a send.. Reason: Authentication failed because the remote party has closed the transport stream.
The underlying connection was closed: An unexpected error occurred on a send.. Reason: Authentication failed because the remote party has closed the transport stream.
Error 3:
The attempt to connect to the SharePoint site was unsuccessful.
The attempt to connect to the SharePoint site was unsuccessful.
Cause
The applications that use the .NET Framework 4.5.2 or earlier, fail to connect to Content Collector because the default value of the registry keys: 'SystemDefaultTlsVersions' and 'SchUseStrongCrypto' are set to the value 0.
Action: You need to set the value to 1 as illustrated in the 'Resolving The Problem' section of this document.
Environment
- IBM Content Collector for Sharepoint
- Microsoft Sharepoint as a source system
- IBM Cloud Pak for Business Automation as a repository
- IBM FileNet Content Manager (P8) as a repository
Resolving The Problem
You need to configure the security via Windows Registry.
IMPORTANT: Setting registry keys affects all applications on the system. Use this option only if you are in full control of the machine and can control changes to the registry.
- Open the Windows Registry Editor (Start > Run > regedit).
- Go to the following registry paths and add a new DWORD (32-bit) value:
- <HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727>
- Value name: SystemDefaultTlsVersions
Value data: 00000001 - Value name: SchUseStrongCrypto
Value data: 00000001
- Value name: SystemDefaultTlsVersions
- <HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319>
- Value name: SystemDefaultTlsVersions
Value data: 00000001 - Value name: SchUseStrongCrypto
Value data: 00000001
- Value name: SystemDefaultTlsVersions
- <HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727>
- Value name: SystemDefaultTlsVersions
Value data: 00000001 - Value name: SchUseStrongCrypto
Value data: 00000001
- Value name: SystemDefaultTlsVersions
- <HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319>
- Value name: SystemDefaultTlsVersions
Value data: 00000001 - Value name: SchUseStrongCrypto
Value data: 00000001
- Value name: SystemDefaultTlsVersions
- <HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v2.0.50727>
- Reboot the system.
Related Information
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSAE9L","label":"Content Collector"},"ARM Category":[{"code":"a8m0z000000cxflAAA","label":"Troubleshooting->P8 Connector issues"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.0.1"}]
Was this topic helpful?
Document Information
Modified date:
22 July 2021
UID
ibm16473445