Skip to main content
Version: 10.0

Office Bridge troubleshooting

Use this guide when Office Bridge does not start, the Office Bridge test fails, Office documents cannot be converted reliably, or the server log contains Office Bridge related exit codes.

If you first need the general setup requirements, start with:

Before you change anything​

  • Confirm that the problem is really related to Office Bridge and not to another converter path.
  • If you convert docx documents with webPDF 10, remember that the native Word Converter is the default path unless officeBridge is requested explicitly.
  • Record which Office version, Windows version, and webPDF version are currently installed.
  • Note whether webPDF runs as a Windows service or as a normal application.
  • If the issue started after a system change, document what changed first:
    • Office update
    • Office version change
    • Windows update
    • service account change
    • DCOM configuration change

1. Check the basic prerequisites​

Office Bridge can only work when all of the following are true:

  • webPDF runs on Windows.
  • Microsoft Office is installed locally on the same server.
  • The Office installation is a classic local installation and not Microsoft 365 Apps.
  • The Office version is Office 2016 or newer.
  • The Office installation is 64-bit.
  • Word, Excel, and PowerPoint are installed and initialized completely.

If one of these prerequisites is not met, Office Bridge is not a valid conversion path.

2. Check whether Office Bridge is really enabled​

Open the Admin Portal and go to the configuration of the Converter web service (1).

  • Make sure the Office Bridge option is enabled (2).
  • Use the Test button in the Admin Portal to validate the Office Bridge setup directly (3).

Office Brdige Test

If the test already fails, continue with the next sections before changing any application-side integration code.

If this test fails, you will see an error message like this:

Office Bridge Test Fails

Use the Clipboard button to copy the error message and the call stack trace. Save the contents to a text file for further analysis by support.

3. Verify the Windows runtime context​

The most common Office Bridge problems occur because Microsoft Office is a desktop application but webPDF often runs as a Windows service.

If webPDF runs as a service:

  • webPDF and Microsoft Office must run under the same local Windows user.
  • The service user must have the Log on as a service right.
  • The service user must have the Log on as a service right.
  • The same user must have logged on interactively at least once so that the desktop profile is initialized.
  • Word, Excel, and PowerPoint must each be started once under exactly that user account to complete all first-start dialogs.

If this setup is incomplete, Office Bridge may fail even though Office is installed correctly.

4. Check DCOM and Office startup behavior​

If Office Bridge cannot initialize Word, Excel, or PowerPoint, verify the DCOM configuration for the Office applications.

Relevant Office applications:

  • Microsoft Word 97-2003 Document
  • Microsoft Excel Application
  • Microsoft PowerPoint Slide

Check especially:

  • the configured identity on the Identity tab
  • the local launch and activation permissions on the Security tab when the user is not an administrator
  • whether the configured user name and password are still valid

Also check whether Office starts correctly outside webPDF:

  1. Log on with the same local Windows user that webPDF uses.
  2. Start Word, Excel, and PowerPoint manually.
  3. Open a sample file in each application.
  4. Save the file as PDF once.

If one of these steps fails, fix the Microsoft Office or DCOM setup first.

5. Check for stale Office processes before starting webPDF​

Before restarting webPDF, verify that there are no stale Office or OLE/DCOM processes left from earlier failed runs.

Typical candidates are:

  • WINWORD.EXE
  • EXCEL.EXE
  • POWERPNT.EXE

If Office Bridge had failed previously, stale processes can block a clean new initialization. In that case:

  1. Stop webPDF.
  2. Check whether stale Office processes are still running.
  3. End only the stale Office processes that belong to the failed setup.
  4. Start webPDF again.
  5. Run the Office Bridge test once more.

6. Collect diagnostics in the preferred order​

When the cause is not obvious, use this workflow:

  1. Run the Office Bridge Test in the Admin Portal.
  2. Save the complete test output (see point 2).
  3. Check the regular log files.
  4. If needed, enable temporary Debug mode.
  5. Reproduce the problem once.
  6. Download Support information.

This is the preferred baseline for further support analysis because the test output often contains the exact OLE or DCOM message.

7. Interpret the most relevant Office Bridge error codes​

At runtime, you may see Office Bridge related webPDF converter error codes in logs, API responses, or the Admin Portal.

CONVERTER_OFFICE_OLE_EXCEPTION = -2501

Meaning:

  • An OLE call failed after Office Bridge already tried to access the Office application.

Typical causes:

  • incomplete Office installation
  • Office not initialized completely
  • changed or broken Office COM/OLE registration
  • Office dialog boxes or add-ins blocking automation
  • permission problems while Office is already being addressed

Recommended checks:

  • verify the Office installation and initialization
  • disable Office add-ins
  • check the detailed exception message and OLE code in the test output
  • review the DCOM and service-user setup

CONVERTER_OFFICE_UNABLE_TO_INITIALIZE_OLE_SERVER = -2504

Meaning:

  • The OLE server for Word, Excel, or PowerPoint could not be started at all.

This is the most relevant public webPDF error for Office Bridge startup failures. Internally, the Office Bridge executable reports the exit code -4 for the same condition.

Typical causes:

  • no usable local Office installation
  • unsupported Office edition such as Microsoft 365 Apps
  • wrong service user context
  • incomplete first start of the Office applications
  • wrong DCOM identity
  • outdated DCOM credentials after a password or system change
  • Office update or Office version change that invalidated earlier assumptions

Recommended checks:

  1. Confirm the Office edition, version, and architecture.
  2. Confirm that Office is installed locally and fully.
  3. Confirm that webPDF and Office run under the same local Windows user.
  4. Recheck the DCOM identity and permissions for Word, Excel, and PowerPoint.
  5. Re-enter the configured DCOM credentials if the account password changed.
  6. Remove stale Office processes and restart webPDF.
  7. Run the Office Bridge test and keep the complete output.

CONVERTER_OFFICE_UNABLE_TO_GET_THREAD_LOCK = -2505

Meaning:

  • The internal synchronization for Office Bridge could not be initialized.

Typical causes:

  • internal startup problem
  • damaged or inconsistent runtime state

Recommended checks:

  • restart webPDF
  • retry once
  • collect logs and support information if the problem persists

CONVERTER_OFFICE_UNABLE_TO_GET_THREAD = -2506

Meaning:

  • Office Bridge could not obtain its execution lock in time.

Typical causes:

  • another Office Bridge thread is still active
  • a previous Office Bridge run is frozen
  • stale Office or bridge state blocks new work

Recommended checks:

  • wait briefly and retry once
  • check whether a previous Office conversion is still running
  • restart webPDF if the lock does not clear
  • check for stale Office processes

CONVERTER_OFFICE_NOT_AVAILABLE = -2507

Meaning:

  • Office Bridge was requested but is currently not available.

Typical causes:

  • Office Bridge is disabled in the Converter configuration
  • Office Bridge is configured incorrectly
  • the Office Bridge startup already failed earlier

Recommended checks:

  • verify that Office Bridge is enabled in the Admin Portal
  • run the Office Bridge test
  • inspect the server logs for the first startup failure

CONVERTER_OFFICE_NOT_ENOUGH_EXECUTION_TIME = -2508

Meaning:

  • The remaining execution time was too short for Office Bridge to run.

Typical causes:

  • aggressive service timeout settings
  • long Office startup time under load

Recommended checks:

  • inspect timeout-related configuration
  • repeat the test under lower system load
  • check whether Office startup is delayed by dialogs, updates, or profile initialization

8. Focus case: Office Bridge executable exit code -4​

If the server log contains a line such as:

Unable to execute 'C:\Program Files\webPDF\officebridge\officebridge.exe' (process exit code '-4')

the Office Bridge executable could not initialize the OLE server.

In practice, start with this checklist:

  1. Check whether Office or Windows was updated recently.
  2. Check whether the Office edition or version was changed.
  3. Check the DCOM identity for Word, Excel, and PowerPoint again.
  4. Check whether the configured identity credentials are still valid.
  5. Check whether stale WINWORD.EXE, EXCEL.EXE, or POWERPNT.EXE processes exist.
  6. Run the Office Bridge test in the Admin Portal and keep the full output.

If the test output contains explicit OLE/DCOM text such as wrong identity, access denied, or missing registration, use that message as the primary diagnosis signal.

9. When to switch away from Office Bridge​

If the requirement is only docx conversion on webPDF 10, do not use Office Bridge by default unless you specifically need Microsoft Office for that workflow.

The native Word Converter is the standard and usually more stable option for docx because it avoids:

  • local Microsoft Office installation
  • OLE/DCOM dependencies
  • service-user and desktop-automation problems

For other Office formats such as doc, xls, xlsx, ppt, or pptx, Office Bridge may still be required depending on the intended conversion path.