All of a client’s workstations were showing un-updated OAB in their Outlooks. When updating was initiated manually, it would fail with error 0x8004010F – object not found. This is with Exchange 2003.

Usually this is caused by the wrong address book being specified within ESM.  However, in this case, that setting was fine.  To be sure, we created another OAB and specified thi new one as default within ESM, but the error continued.

What resolved it in this case was a rather arcane item.  Within the C:\Sindoes\system32 folder is the file MAPISVC.INF and within that file is this line:

6603001f=<server name>    where <server name> is the netbios name of the server

Removing that line and saving the file cleared the problem.