Migrated to Exchange 2010, now clients getting OAB error (0x8004010f)
Hello,
Over the weekend I moved my mailboxes from my Exchange 2003 server to my newly installed Exchange 2010 server. All is working with one exception. After a send/receive from any and all clients workstations (all running Outlook 2003), the user receives a detail box in the upper left corner that says Task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed. An object could not be found.'
I've verified I can see the OAB from the Exchange Management Console, and it resides on my new mailbox server. What can I do to repair/resolve this?
Thanks.
Over the weekend I moved my mailboxes from my Exchange 2003 server to my newly installed Exchange 2010 server. All is working with one exception. After a send/receive from any and all clients workstations (all running Outlook 2003), the user receives a detail box in the upper left corner that says Task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed. An object could not be found.'
I've verified I can see the OAB from the Exchange Management Console, and it resides on my new mailbox server. What can I do to repair/resolve this?
Thanks.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Akhater: Thanks! I had created a new database, and when I do properties, client settings, there is no OAB listed. I've since selected it, do I need to restart the store or another service to make it work (I'm still getting the error).
yes it might take a bit of time to kick in maybe a couple of hours,
try to restart the server and test if you can
try to restart the server and test if you can
ASKER
HI Folks,
Still have the error. Akhater, servers have been rebooted.
AustinComputerLabs, I've reviewed those and have assigned the address book for pf distribution. I'm logged in as administrator, and if I try and update the offline address book through the EMC, I receive the following:
Error:
Failed to generate the content of the offline address book '\DOM\OAB. Two possible reasons off the failure are that the system attendant service is not running or you do not have permission to perform this operation. Error message: 'Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from RpcEpResolveBinding'
I created a new offline OAB as well, set it as default and tried the same thing, and get this error. My system attendant service is running, and I'm logged in as the domain admin, the same account I used to install and set up the servers.
Thoughts? Thanks
Still have the error. Akhater, servers have been rebooted.
AustinComputerLabs, I've reviewed those and have assigned the address book for pf distribution. I'm logged in as administrator, and if I try and update the offline address book through the EMC, I receive the following:
Error:
Failed to generate the content of the offline address book '\DOM\OAB. Two possible reasons off the failure are that the system attendant service is not running or you do not have permission to perform this operation. Error message: 'Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from RpcEpResolveBinding'
I created a new offline OAB as well, set it as default and tried the same thing, and get this error. My system attendant service is running, and I'm logged in as the domain admin, the same account I used to install and set up the servers.
Thoughts? Thanks
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
v-2nas: Same error. I even restarted the SA on the old 2003 server as well.
ASKER
Folks, After I restarted my SA and that didn't work, I went back, did an "update address book" from EMC and didn't get an error. I then restarted SA and the error is gone. Thanks for your help and patience!
thank you for the updates and the points and sorry i wasn't able to follow on the question in the past 2 days
glad to know it works
glad to know it works
what is the effect of this error ?
Also plz post a screenshot of the error.
Regards,
v-2nas
http://www.exchadtech.blogspot.com