This started showing up earlier today. Looks like I'm having issues with the Exchange 2013 OAB, I needed to change the name and email address for a user on the Exchange 2013 server. Used the EAC, renamed the user, and added a new default email address. Simple enough, done it many time before. Connected to an Outlook 2010 client machine, loaded Outlook, hit F9 to update the OAB, and got the following error:
Task 'user@domain' reported error 0x8004010F the operation failed. An object cannot be found
I figured I needed to rebuild the OAB on the server, so I went into Powershell on the server, and ran the following command:
[PS]> update-offlineaddressbook -identity "Default Offline address book"
Per another doc I was referring to, I also ran the GAL update, as per the following command:
[PS]> Update-GlobalAddressList -Identity "Default Global Address List"
I received no errors after running the above commands. Went back to the PC w/Outlook 2010, reran the F9 to update the OAB, still got the same error 0x8004010F
Note that when I remove cached mode for Outlook on that PC and run it in online mode it works, and I can see the latest updates to the GAL.
Went to another PC and looked at the contents of the folder:
c:\users\%userprofile%\appdata\local\microsoft\outlook\Offline Address Books
The files were all dated 2/21/2021 (!)
I closed Outlook on the 2nd PC, renamed the Offline Address Books folder, restarted Outlook, and then ran F9. Nothing happened, so I looked at the newly created Offline Address Books folder, and it was blank. I then clicked on File / Account Settings in Outlook, selected Download Address Book,and ultimately received the same error 0x8004010F.
I checked on a 2nd PC on the same network, and saw that the files in the Offline Address Books folder were also dated 2/21/201.
So apparently this OAB issue has been going on for a while. In hindsight, there have been no personnel changes at this client for a while, so the situation to add/change users didn't come up until now, which brought the issue into view.
If I can't immediately resolve the OAB update issue, 2 temporary workarounds (I think) for this are either:
a) run Outlook in pure online mode (not preferred, as it makes the server labor more)
b) close Outlook on all PC's, rename the Offline Address Books folder, restart Outlook, and have Outlook go directly off the GAL while remaining in cached mode for all other operations.
There are a total of 12 PC's on the network, so the prospect of working directly off the server for online mode and/or direct GAL access should not bring on performance issues.
Any thoughts on how to resolve the error 0x8004010F.? It seems that the OAB can't properly rebuild on the server through the usual means.
Thanks in advance for your assistance.