Troubleshooting – Encryption & Certificates

772 views 0

The following is a table of possible error messages together with information on cor­recting the errors.

Error message Solution
“The client has rejected the print job. (… Error in function No. 3, Error code: 8006ea6e)“ Client is active and has been detected but can’t print.

• printer off/paper jam/no toner?
• Certificate not found on the client. Possible causes: ThinPrint Client’s certificate is not issued for server authentication, is not signed by the correct issuer certificate (from a root or intermediate certification authority), or contains no key; certificate is not stored in the correct memory (user/machine store) or does not have the appropriate per­missions; typing error in the encryption settings, or in the registry.

The certificate cannot be read or is incorrect. The certificate is present on the client but cannot be read. If necessary, request a new certificate that is appropriate for server authentication and contains a key.
Error while receiving data. • With encryption: You may be using an older ThinPrint Client. Install the latest version.
• When printing via ICA/RDP: The connection may have been (briefly) lost.
“Server or client certificate has not been signed by the selected root certificate. (… Error in function No. 3, Error code: 8325eaf2)” • The ThinPrint Engine can’t determine the validity of the certificate received from the client.
• The certificates of central print server and ThinPrint Client must be signed by the same issuer certificate (from a root or intermediate cer­tification authority). Check the “Issued by” column against the issuer certificate.
• No name was entered for a root certificate in the ThinPrint Engine configuration. Or the root certificate or the intermediate certificate is missing.
• The certificate name (e. g., root) may be too vague. In this case, another certificate with this string has already been found in the cer­tificate store, and the certificate references are then incorrect.
• If the same issuer certificate exists several times in the certificate store, delete all these certificates and import them again. Afterwards restart the central print server.
Error while handshaking for encrypted transfer or

“Error while establishing encrypted connection. (… Error in function No. 3, Error code: 8310eae5)“

Referring to the server certificate on the central print server:

• Server certificate is invalid or has expired.
• Perhaps the server certificate does not contain a private key or the private key was not imported during installation (mark key as export­able).
• No certificate name was entered in the ThinPrint Engine encryption settings.
• The connection partners can‘t agree on a suitable protocol. In the server-side Windows registry, verify whether one of the protocols SSL 3.0, TLS 1.0, 1.1, or 1.2 is disabled (for example, SSL 3.0 is dis­abled if the value hkey_local_machine\system\CurrentControl­Set\Control\SecurityProviders\SChannel\Protocols\SSL 3.0\Server\Enabled is set to zero). Compare the behavior when print­ing to a Windows client with printing to the ThinPrint Hub or to a Linux client.

The server certificate validity starts in the future. The server certificate is not valid yet

• Synchronize date and time on all associated computers
• Depending on the system, a certificate requested from the IIS first becomes valid the day after it was issued. Validity can be checked in the certificate manager.

The server certificate name has not been set. No certificate name was entered in the ThinPrint Engine encryption settings.
Couldn’t find selected server certificate. The name entered in the ThinPrint Engine configuration does not agree with the name of the certificate.
Couldn’t find selected root cer­tificate. The name entered in the ThinPrint Engine configuration does not agree with the name of the certificate.
The root certificate name has not been set. No certificate name was entered in the ThinPrint Engine encryption settings.
Previous Page
Next Page

Was this helpful?