Open in Excel failing due to failed certificate revocation check

We are running Google Looker Cloud and attempting to use the Open in Excel feature on an explore. We are able to get it to work on one computer and not on another. We use the User explore for simplicity’s sake and create a simple table with a few fields and select Open in Excel. An .odc file is downloaded.

When we open the ODC file, on one machine (non-working machine), we receive the following error:

schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate.

We have disabled the Check for server certificate revocation in Internet Properties. We have also temporarily disabled our security software (CrowdStrike) and Windows Defender and the issue persists.

We are able to curl to the server URL on the non-working machine.

There is no difference between the two ODC files and we have even tested by opening the ODC file from the working computer on the non-working computer.

On both machines, we have identical ODBC connections configured and in both cases, clicking “Test” works correctly when testing the ODBC connection. The same user credentials are used for both machines against the same environment.

This DOES work on the non-working machine if we use the Data→Get Data feature in Excel and use the exact same ODBC data source. The issue only occurs when the ODC file is used.

[Edit] - We have gotten this to work with the Looker downloaded ODC file by unchecking the “TLS Verify Peer” option on the Advanced tab of the Looker ODBC Data Source tab. This is not ideal as it does present a possible security hole.

What else could be blocking the certificate revocation check?

Other information

Windows version:
Working machine: Windows 10 Pro
Non-working machine: Windows 11 Business

Excel version:
Working machine: Microsoft 365 version 2601 Build 19628.20214
Non-working machine: Microsoft 365 Apps for Business version 2508 Build 19127.202532

Looker ODBC Driver: Latest 64-bit driver

We were able to resolve this. The issue was that our data loss prevention software (Safetica) was “hijacking” the SSL connection. The cert for any site was on a local machine, which then forwarded on to the cert on the target host. The local cert was not responding as expected for the ODBC connection. We put an exception in our DLP software for the specific domain on which our Looker instance lives.