When you download a customized PGP Encryption Desktop client from the PGP Encryption Server, an error may be logged to the Administration log and the
PGPtrustedcerts.asc file is not included in the *.msi installation file.
Download the PGP Encryption Desktop client by doing the following:
After the download completes, an error may appear in the Administration log. If the error appears, the
PGPtrustedcerts.asc file will not be included in the installation file.
An error similar to the following may appear in the Administration log on the Reporting / Logs page of the administration console. In this example, 54,321 represents any number greater than 30,000:
String too long (string is 54321 limit is 30000)
The PGP Encryption Server administrators can import Root and Intermediate certificates from the Keys / Trusted Keys page of the administration console. All such imported certificates are included in the
PGPtrustedcerts.asc file within the customized Encryption Desktop installer.
During the installation of Encryption Desktop, the
PGPtrustedcerts.asc file is saved to the folder
If the combined Root and Intermediate certificates comprise over 30,000 characters, the
String too long error is generated and the
PGPtrustedcerts.asc file is not included in the MSI file.
This issue can occur after an upgrade of the PGP Server. Check the Trusted Keys list to see if there are any duplicates, this can add to the list.
In order to resolve avoid the
String too long error, or if you click "Customize" and the client will not download, please contact Symantec Technical Support.
There is a fix that Encryption Support can assist with to allow you to download the client properly.
Starting with PGP Server 10.5.1 MP2, this issue will no longer be observed. If you still see this issue even after upgrading to 10.5.1 MP2, please contact Symantec Encryption Support for further guidance.
EPG-28079 - Duplicate Trusted Keys or problematic Trusted Keys may be seen upgrading *to* PGP 10.5.0 MP3 through PGP Server 10.5.1 MP1.
Upgrading from PGP 10.5.1 MP1 to any newer version will not see this issue.
Reach out to Symantec Encryption Support if you see this issue and mention this ticket ID to resolve the problematic Trusted Keys.
For other information relate to certificate pop-ups, see the following articles for assistance and contact Symantec Enterprise support if needed: