- Error message 1There is a problem with the proxy server's security certificate, %s. Outlook is unable to connect to this server. (%s)
- Error message 2There is a problem with the proxy server's security certificate, %s. The name on the security certificate is invalid or does not match the name of the site. Outlook is unable to connect to this server. (%s)
- Error message 3There is a problem with the proxy server's security certificate, %s. The security certificate is not from a trusted certifying authority. Outlook is unabletoconnect tothis server.(%s)"
- Error message 4There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site outlook.office365.com. Outlook is unable to connect to the proxy server (Error Code 0)
- The %s placeholder is the Outlook profile property 001f6622. This is the Microsoft Exchange Server RPC proxy server name.
- The (%s) placeholder is the error code.
For error message 1 and error message 2, the error code that is returned is the sum of all the bitmask certificate problem codes. See the "More Information" section for information about the bitmask certificate problem codes.
For error message 3, the error code is expected to always be 0x00000008.
- The connection to the server requires a certification authority (CA).
- You have not trusted the certification authority at the root.
- The certificate may be invalid or revoked.
- The certificate does not match the name of the site.
- A third-party add-in or a third-party browser add-in is preventing access.
Method 1: Examine the certificateUse this method if you receive either error message 1 or error message 2. Examine the certificate. Then, contact your system administrator to resolve this issue.
To examine the certificate, follow these steps:
- In Microsoft Internet Explorer, connect to the RPC server or to the secure server. For example, type https://www.server_name.com/rpc in the Address bar of the Web browser, and then press ENTER.
Note The server_name placeholder references the RPC server name or the secure server name.
- Double-click the padlock icon that is located in the lower-right corner of the Web browser.
- Click the Details tab.
- Note the information in the following fields:
- Valid to
The Valid to field indicates the date until which the certificate is valid.
The data in the Subject field should match the site name.
- Valid to
Method 2: Install the trusted root certificateUse this method if you receive error message 3. To install the trusted root certificate, follow these steps:
- Click Install Certificate when you are prompted with the Certificate dialog box.
- Click Next.
- Click to select the Place all certificate in the following store check box.
- Click Browse.
- Click Trusted Root Certification Authorities, and then click OK.
- Click Next.
- Click Finish.
- Click OK.
Method 3: Disable the third-party add-in or the third-party browser add-inUse this method to disable the third-party add-in or third-party browser add-in if you receive error message 4.
Disable third-party add-ins
- Start Outlook in safe mode to help isolate the issue. To do this, click Start, click Run, type outlook.exe /safe, and then click OK.
If Outlook successfully starts in safe mode, the issue that you're experiencing may be caused by a third-party add-in.
- Check for third-party COM add-ins and disable them. To do this, follow these steps:
2632425 How to troubleshoot crashes in Outlook 2010 and Outlook 2013
- On the File menu, click Options, and then click Add-Ins.
- In the Manage box, click COM Add-ins, and then click Go.
- Click to clear the check box next to the third-party add-ins that you want to disable.
- Restart Outlook.
Disable third-party browser add-insOutlook uses Internet Explorer settings for HTTP requests. If a third-party browser add-in is causing this issue, disable it in Internet Explorer. For steps on how to do this, see the "Disable add-ons in Internet Explorer" section of the following Microsoft Knowledge Base article:
Article ID: 923575 - Last Review: Mar 29, 2017 - Revision: 3