Problems With Public Folder Store after Forklift move
I recently performed a swing procedure on a sbs 2003 server, in order to take the server to new hardware. I did a forklift copy of the exchange data, (copy the mdbdata folder off the old server, stick it on the new and mount).
After jumping trough a few hoops, the mailbox store mounted and clients could open outlook and see the corect data displayed.
My Question is about the public store. I had some issues getting it to mount initially, those have been resolved now. Currently the sutuation is as follows :
When the public folder store is mounted, if clients open outlook, send and recive, they get a error
task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed. An object could not be found.'"
This happens with both the origanal store mounted and a new blank store mounted.
If the public store is NOT mounted and a client opens outlook, they can work, send recive and what ever else no problem. There seems to be no downside to not having the public store mounted.
I'm guessing the outlook clients are detecting that the mounted store is somehow difrent from the store of which they have an offline copy. Removing and returning the exchange account on client pc's is a last option, as I would have to do this on all clients and some mail boxes are large. Unless I can remove and return the public folders on each client without removing and returing the exchange account.
As a temp solution I have stoped the public folder store from mounting, is this a viable solution ?
If you do a default install of exchange, and dont put anything into public folder storage, does it get used at all ?
I know little about MSE Public folders, so constructive comments are welcome.
After jumping trough a few hoops, the mailbox store mounted and clients could open outlook and see the corect data displayed.
My Question is about the public store. I had some issues getting it to mount initially, those have been resolved now. Currently the sutuation is as follows :
When the public folder store is mounted, if clients open outlook, send and recive, they get a error
task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed. An object could not be found.'"
This happens with both the origanal store mounted and a new blank store mounted.
If the public store is NOT mounted and a client opens outlook, they can work, send recive and what ever else no problem. There seems to be no downside to not having the public store mounted.
I'm guessing the outlook clients are detecting that the mounted store is somehow difrent from the store of which they have an offline copy. Removing and returning the exchange account on client pc's is a last option, as I would have to do this on all clients and some mail boxes are large. Unless I can remove and return the public folders on each client without removing and returing the exchange account.
As a temp solution I have stoped the public folder store from mounting, is this a viable solution ?
If you do a default install of exchange, and dont put anything into public folder storage, does it get used at all ?
I know little about MSE Public folders, so constructive comments are welcome.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
--snip-- have the server create a blank public store (by moving the old one to a backup location, when it is started and finds no store it will recreate a blank one) then exmerge the data back in, this should not affect the users mailboxes (or outlook logins) and it should simply sync the public folders.
--snip--
If I'm correct, Exmerge imports and exports the data in the mail box store, not the public store, or is that wrong ? Anyhow, the Mailbox store already has all the users data, and is 100%. With a blank public store I get the error I described.
Not really woried about the info in the public store, since we did not put any info in the public store. I just want the error gone.
navdhanjal:
--snip --- If you are not using the public store at all then it is a viable solution. --- /snip---
Thanks !
--As for the error itself, does it actually go away if you re-setup a profile on Outlook. I have a feeling the error will remain even with a new Outlook profile. --/
I think I did try this once, and it worked ! (only did it one one client pc) But after that I kept on messing with it to see if I could not get arround the problem without redoing the clients
sandeep_narkhede:
Does creating a new profile works? YES
do you see the OAB folders replica created on the same server as you have now? Sorry, where exactly would I check that ?