I
ITguy_uk
I have recently migrated some mailboxes from a MS Exchange 5.5 server
to an Exchange 2003 server using Outlook 2003 (on W2K SP4)in Cached
Exchange Mode. All of the client PC's seem to be correct apart from a
two. These Outlook 2003 clients don't seem to be able to download the
OAB(Offline Address Book). Whenever I select "Download Address Book"
from the SEND|RECEIVE dropdown on the toolbar at the top of Outlook
2003 I get the error:
Task 'Microsoft Exchange Server' reported error (0x8004010F) : 'The
operation failed. An object could not be found.'
I thought this maybe caused by a corrupted local OAB on the desktops
but when I searched all the local disks on the machine for *.OAB it
found nothing. Is this error because it is looking for OAB files that
do not exist? Will removing the Outlook profile and recreating it
solve the issue?
I did look for KB articles and on Google but they all seem to be
server side and on Exchange 2000 not Exchange 2003. As it is only some
of the desktops that have this issue it seems that the problem is
probably client side.
Anyone experiencing the same issue, solved this or have hints for
diagnosing it?
to an Exchange 2003 server using Outlook 2003 (on W2K SP4)in Cached
Exchange Mode. All of the client PC's seem to be correct apart from a
two. These Outlook 2003 clients don't seem to be able to download the
OAB(Offline Address Book). Whenever I select "Download Address Book"
from the SEND|RECEIVE dropdown on the toolbar at the top of Outlook
2003 I get the error:
Task 'Microsoft Exchange Server' reported error (0x8004010F) : 'The
operation failed. An object could not be found.'
I thought this maybe caused by a corrupted local OAB on the desktops
but when I searched all the local disks on the machine for *.OAB it
found nothing. Is this error because it is looking for OAB files that
do not exist? Will removing the Outlook profile and recreating it
solve the issue?
I did look for KB articles and on Google but they all seem to be
server side and on Exchange 2000 not Exchange 2003. As it is only some
of the desktops that have this issue it seems that the problem is
probably client side.
Anyone experiencing the same issue, solved this or have hints for
diagnosing it?