0X80040004 OLE_E_NOCONNECTION: No Connection for This Connection ID

Quick Answer

Restore the source file to its original path, or update the OLE link in the host app (Edit > Links > Change Source). That's it.

Why You're Seeing This Error

This error pops up when Windows can't find the source file behind an OLE object. I've seen it most in Excel and Word, usually after someone renames or moves a PDF or another Office doc that's embedded as a link. The OLE object still has the old path burned into its metadata. The error code is 0X80040004, and it means the connection ID (the pointer to the object) is invalid. It's common when you copy a worksheet that contains linked objects from one workbook to another—the links don't travel well. Had a client last month whose entire financial dashboard broke after someone moved the quarterly report PDF to a new folder. The OLE link just pointed to a dead end.

Fix Steps (Numbered)

1. Check the source file location – If you moved or renamed the file you linked to, move it back or rename it to the original name. This is the fastest fix.
2. Update the link in the host app – In Excel or Word, go to Data > Edit Links (or File > Info > Edit Links to Files in older versions). Select the broken link and click Change Source. Point it to the new location. Confirm with OK.
3. Re-link manually – If Edit Links isn't available (sometimes OLE objects are embedded as icons), right-click the object, choose Linked <Object Type> > Links, then change source there. I've seen this hidden in odd places.
4. Break the link – If you just need the data and don't care about the connection, in Edit Links, select the link and click Break Link. This converts the object to a static picture or data, killing the error permanently.

Alternative Fixes (If Main One Fails)

Check DCOM Permissions

Sometimes OLE errors are permission-related. Open Component Services (run dcomcnfg from a command prompt). Go to Component Services > Computers > My Computer > DCOM Config. Find the app that's hosting the OLE (e.g., Microsoft Excel Application). Right-click, choose Properties, then the Security tab. Under Launch and Activation Permissions, click Edit. Make sure your user account has Local Launch and Local Activation permissions. Had a case where a network admin tightened DCOM permissions and broke OLE across the whole office.

Re-register the OLE DLLs

Open an admin command prompt. Run these two commands:

regsvr32 /u ole32.dll
regsvr32 ole32.dll

Repair Office Installation

Open Control Panel > Programs > Microsoft Office > Change > Quick Repair. This re-registers all OLE components. If that doesn't work, try Online Repair—it takes longer but fixes deeper corruption.

Prevention Tip

Never move or rename source files after establishing OLE links. If you must move them, use Edit Links beforehand to update all references. For shared files, embed the data instead of linking—it bloats the file but kills this error forever. I always tell clients: link only for temporary workflows, embed for anything that's sent around.