Exchange Server Forums

Cannot Open Address Book in OWA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> Outlook Web Access >> Cannot Open Address Book in OWA

Page: [1]

Message

<< Older Topic Newer Topic >>

Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM

TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!

Cannot Open Address Book in OWA - 29.Mar.2007 12:15:30 PM

Ex2k7Admin

Posts: 1
Joined: 29.Mar.2007
Status: offline

When you click "To" I get an error page that says

"Access is denied" Outlook Web Access was unable to access the active directory resource. This may be because the active directory object does not exist or the object has become corrupted, or because you do not have sufficient access rights for the object.

It used to work and then one day it quit. If you start the persons name, it will resolve it and/or bring up suggestions, it just won't let you browse the address book.

Thanks

Post #: 1

Featured Links*

RE: Cannot Open Address Book in OWA - 11.Apr.2007 4:40:37 PM

maav

Posts: 1
Joined: 11.Apr.2007
Status: offline

Hi,

I had the same issue and we have just resolved it. It appears that the users' AD attribute was not set. Open ADSIedit.msc and check the properties of a mail-enabled user. Check the msexchquerybaseDN specifically and verify that your domain's distinguished name is listed (DC=domain, DC=com). After setting these, I cured the problem. I am just trying to figure out a way to do this for OUs right now.

(in reply to Ex2k7Admin)

Post #: 2

RE: Cannot Open Address Book in OWA - 17.Dec.2008 5:44:07 AM

Searla

Posts: 2
Joined: 29.Mar.2006
Status: offline

Hi, this fix worked for me too - very strange......

Did you get any further with finding a domain level fix? Or is there a better fix for this?

Many thanks

(in reply to maav)

Post #: 3