%1 could not connect securely to server %2 because the certificate presented by the server was not trusted due to validation error 0x%3. The issuing certificate authority (CA) for the server's certificate may not be locally trusted by the client, the certificate may be revoked, or the certificate may have expired. Resolution: A tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit can be used in order to interpret the error code listed above. If you trust the server certificate, the issuing certificate authority (CA) certificate can be placed in the local trusted root certificate authorities certificate store. If you have logged into the server before without issues the network administrator should carefully examine the certificate if no known configuration changes have been made.
Could not automatically save your instant message conversation. To save manually, click Save As on the File menu of the conversation ...
could not be added because your contact list contains the maximum number of groups or contacts. Delete one or more contacts ...
could not connect securely to server %2 because the certificate presented by the server did not match the expected hostname ...
could not connect securely to server %2 because the certificate presented by the server was invalid. The certificate was ...
could not connect securely to server %2 because the certificate presented by the server was not trusted due to validation ...
Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not delete key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not delete value 2 from key 3]. { System error 4].} Verify that you have sufficient access to that key, or contact ...
Could not display a form related to this conversation, which may prevent access to some options. If this problem persists, ...