8.2 Clearwell Commander action “Copy Tomcat Provider-Signed Certificate to Windows Trust Store” fails with error “Attempt to change Friendly Name of PFX Certificate in Windows Trust Store failed”
Article ID: 100033053
Updated On:
Description
Error Message
From the ADSCrawler_output.log:2016-09-16 14:21:40,042 [7688] INFO ADSCrawler - AD BufferManager queue size: 500
2016-09-16 14:21:43,105 [7688] INFO ADSCrawler - SSL Service started
2016-09-16 14:21:43,131 [7688] ERROR ADSCrawler - System.ArgumentException: No valid certificates found.
or
2016-10-24 13:12:14,981 [5160] INFO ADSCrawler - AD BufferManager queue size: 500
2016-10-24 13:12:18,073 [5160] INFO ADSCrawler - SSL Service started
2016-10-24 13:12:20,051 [5160] ERROR ADSCrawler - System.Security.Authentication.AuthenticationException: A call to SSPI failed, see inner exception. --->
System.ComponentModel.Win32Exception: An unknown error occurred while processing the certificate
From the CMADCrawler_output.log:
2016-09-16 14:21:35,393 [11856] FATAL CMADCrawler - Main: Could not receive messages from Client.
2016-09-16 14:21:35,473 [13932] INFO CMADCrawler - Main: Starting Custodian Manager Active Directory Synchronisation.
2016-09-16 14:21:35,484 [13932] INFO CMADCrawler - SSL Service started
2016-09-16 14:21:35,502 [13932] ERROR CMADCrawler - System.ArgumentException: No valid certificates found.
From the Server.YYYY-MM-DD.log:
2016-09-16 14:21:11,974 [5048] INFO ADSCrawler - SSL Service started
2016-09-16 14:21:12,496 [5048] ERROR ADSCrawler - System.ComponentModel.Win32Exception: The credentials supplied to the package were not recognized
at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
at System.Net.Security.SecureChannel.AcquireServerCredentials(Byte[]& thumbPrint)
at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at SecurityUtilsLib.SSLServerService.getSSLStream(Int32 certFindType, String certFindValue, Boolean findValidCertsOnly) in D:\builds\checkout_ESA-V82_CHF1\src\C#\SecurityUtilsLib\SecurityUtilsLib\SSLServerService.cs:line 143
at ADSCrawler.ADSCrawlerMain.ReceiveMessage(RequestHeader request) in D:\builds\checkout_ESA-V82_CHF1\src\C#\ADSCrawler\ADSCrawler\ADSCrawler.cs:line 320
Cause
Resolution
A hotfix is now available for this issue in the current version(s) of the product(s) mentioned. Refer to the Hotfix link under Related Articles to obtain the hotfix needed to resolve the issue.
Issue/Introduction
Figure 1
Additional Information
