Error 0x8004010F ("Outlook data file cannot be accessed" or sometimes "The operation failed. An object could not be found.") shows up when Outlook tries to send or receive email but can't properly reach the PST or OST file your profile is supposed to be using.

Ad placeholder — in-article responsive unit

Common causes

Fix 1: re-download the Offline Address Book

Worth trying first since it's quick and low-risk:

  1. In Outlook, go to Send/Receive tab
  2. Click Download Address Book
  3. Check the box for Download changes since last Send/Receive
  4. Click OK, let it complete, then close and reopen Outlook
  5. Try sending an email to check if the error is resolved

Fix 2: locate your data file and create a new profile

If the address book refresh didn't help, this is Microsoft's own recommended fix for this error:

  1. Open Control Panel → Mail (you can search "Mail" directly in Windows search if Control Panel's classic view is hard to find)
  2. Click Show Profiles
  3. Select your current profile and click Properties → Data Files
  4. Note down the exact name and file path of your current data file(s)
  5. Close this window, then click Add (back in the profile list) to create a brand new profile
  6. Set up the new profile, and when prompted for a data file, point it to the existing PST/OST file you noted down — don't create a new blank one, since your existing emails live in the file you already have
  7. Set the new profile as default, then restart Outlook

Your data is safe through this process — creating a new profile doesn't delete or touch your existing PST/OST file. You're just rebuilding the connection between Outlook's settings and the data file, which is often enough to clear up a corrupted profile without losing anything.

Fix 3: if the data file itself is corrupted

If the above doesn't resolve it, the PST/OST file itself may be damaged:

If the file is stored inside OneDrive

If your PST/OST currently lives inside a folder OneDrive is actively syncing, moving it to a purely local folder (outside any cloud-sync folder) resolves the underlying file-locking conflict permanently, rather than needing to repeat any of the above fixes each time it recurs.