Skip to main content
Participant
July 21, 2026
質問

Acrobat Chrome extension 26.7.2.0 fails to open authenticated OpenText PDFs

We are experiencing a regression with Adobe Acrobat Chrome extension version 26.7.2.0.

Environment:

  • Adobe Acrobat Chrome extension: 26.7.2.0
  • Google Chrome: 150.0.7871.129
  • Source application: Power BI Web
  • PDF repository: OpenText Cloud
  • OpenText URL format: https://otac.sg59.opentext.cloud/archive?get...

Expected result:
Selecting a PDF link in Power BI should open the document in the Adobe Acrobat Chrome extension viewer.

Actual result:
The document begins loading in the Adobe viewer, but Acrobat then abandons the operation and falls back to Chrome’s native PDF viewer.

Acrobat telemetry captured during the failure reports:

DCBrowserExt:Viewer:Error:FallbackToNative:FileDownload:Failed

The same event is classified as:

non_mime

Control test:
A direct public PDF URL ending in .pdf opens correctly in the Adobe extension:
https://web.mit.edu/dvp/Public/butters-lululu.pdf

Troubleshooting already completed:

  • Confirmed “Online PDFs” is enabled in Acrobat preferences
  • Confirmed Adobe has site access on all sites
  • Confirmed Acrobat is the Windows default PDF application
  • Allowed third-party cookies for [*.]opentext.cloud
  • Cleared all cookies and browser data
  • Tested with a new Chrome profile
  • Confirmed the extension works with ordinary direct PDF links
  • Reproduced the issue on multiple computers

One computer initially opened the same OpenText documents correctly. It began failing immediately after its Adobe extension updated to 26.7.2.0. This strongly indicates a regression in version 26.7.2.0, or in remote configuration deployed with that version, involving authenticated or extensionless PDF endpoints.

Current workaround:
Chrome downloads PDFs and user opens the downloaded file in desktop Acrobat. Chrome’s native PDF viewer also displays the document successfully.

Need to confirm:

  1. Whether this is a known issue in extension version 26.7.2.0.
  2. Whether a fix or remote kill-switch is planned.
  3. Whether there is a supported temporary rollback or enterprise mitigation.
  4. What additional sanitized diagnostic information is required.