I installed a new Exchange 2003 server into my existing Exchange site. We have 8 Exchange servers all together, one Exchange 5.5 (being phased out), and 7 Exchange 2003 servers all running SP2. I installed a new server into this mixed mode site the other day. But I found that I could not view the public folder tree in ESM. I had this issue once before and managed to clear it up by giving it time to replicate and rebuilding the RUS. This time none of that worked. Here is what I have tried so far...
1. Rebuild RUS
2. Given days to allow full replication
3. Deleted pub.edb and pub.stm and re-created public folder store
4. Verified that the public folder store has a proxy address in adsiedit (rules out RUS right?)
At this point, I am out of ideas. I can say that when I connect to a test mailbox on this new Exchange 2003 server, that the user in Outlook can also not see any public folders. When I try using pfdavadmin and connect to this new exchange server, I also see no public folders there either. I think its definately an issue with Exchange on this new box and not an issue with AD (I think).
Anyone have any other ideas or things I can try? Searching online has not given me much to go on.
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Checked all that, nothing helpful in the event logs, no errors. I upped logging too to make sure I wasn't missing anything. I just ran the Best Practice Analyzer and it did report that my public store doesn't have an SMTP address stamped yet. I don't know why since I see a proxy address in adsiedit. Anyway, I'm still scratching my head over this one.
UPDATE: Issue resolved!
Turned out that the RUS has an old recipient policy that did not have a PRIMARY SMTP address configured. There was an SMTP address in the list, but it was not a primary address. No idea why the problems just recently staretd, since this RUS policy was around for a while, but oh well. Solution was to make one of the SMTP addresses a primary address and then force replication and rebuild the RUS. After this, everything worked fine. Hope this helps someone else.
Business Accounts
Answer for Membership
by: florin_sPosted on 2008-07-11 at 05:51:39ID: 21981860
Hi,
What dose event log say about this, are there any errors loged?
Did you test the connectivity with the domain controller.
Also verify that the Exchange enterprise server group is not empty.