Exchange server 2016 is one of the most recent iterations of Microsoft’s widely popular mail and calendaring server platforms. Being Microsoft’s flagship platform, it facilitates emails, scheduling, notes, journals, calendar, contacts, various tools for collabs etc. Some of the notable differences in the latest iteration of the exchange server include:
Quick Solution
EdbMails for EDB to PST Converter is an free tool to convert online & offline corrupt and healthy EDB Files to PST, Live Exchange and Office 365.
- Only two roles – Mailbox Server and Edge Transport
- Outlook UI on the web updated
- The Hybrid Configuration Wizard (HCW) that used to come bundled with Exchange 2013 is now a cloud-based application. The users will be prompted to download and install the wizard when configuring a hybrid deployment in Exchange 2016.
- New DLP (Data Loss Prevention policy) and Archiving/Retention/eDiscovery features.
- MAPI over HTTP is now the default protocol for connections between Outlook and Exchange this allows for enhanced discoverability of errors in the transport layer.
- The overarching goal is to match work habits evolving from a communication focus to a collaboration focus and to this end, Exchange 2016, along with SharePoint Server 2016, enables Outlook on the web users to easily link and share documents stored in OneDrive.
0x8004010F – Error
Now that we’ve seen what the latest iteration of Microsoft Exchange Server brings to the table, let’s see how to deal with one the most common issues exchange server 2016 users encounter.
(0x8004010F): ‘The Operation failed. An object cannot be found’
The above error is most commonly observed when running an exchange server 2016 platform with Outlook version 2010 installed. Upon receiving this error, your attempts at sending mails via Outlook could be un vain and return error:
Task “Microsoft Exchange Server” reported error (0x8004010F): ‘The operation failed. An object could not be found’
Causes
The 0x8004010F error can be due to one of the following reasons:
- There are incorrect items in the Offline Address Book (OAB) list object
- The OAB has either a missing or incorrect address list in Offline address list settings
One can easily check these by going to ‘Properties’ in Offline Address list settings
Rectifying the error
Below are some steps that can help troubleshoot the 0x8004010F error.
To solve properties in the Address lists, the following can be attempted:
- Open Exchange Management Console
- Expand ‘Server Configuration’ and select mailbox.
- Bring up ‘Properties’ by right clicking ‘in the ‘Database Management’ window.
- Go to ‘client settings’ tab, browse and select the correct OAB.
To solve properties in the Offline Address list:
- Go to properties in Exchange System Manager.
- Check whether the offline address lists are populated by valid offline address list-objects.
If the error still persists even after trying out the above steps, then it could very well be a case of Exchange Database (.edb file) corruption. Exchange database corruption is a serious issue as the edb file is the store of all data within the server and hence could put all of that information in jeopardy.
This is where EdbMails exchange recovery tool, which is a forensic exchange recovery software, can help you in recovering the exchange database and all its contents seamlessly. EdbMails has an intuitive and easy to use user interface, it also employs deep scan techniques which allows it to repair and recover lost data from corrupt or inaccessible exchange databases quickly.