Exchange Server Forums

"Bookmark is not valid" Error when using Oulook 2007

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [Microsoft Exchange 2007] >> General >> "Bookmark is not valid" Error when using Oulook 2007

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!

"Bookmark is not valid" Error when using Oulo... - 22.Feb.2007 3:20:57 PM

stevehoot

Posts: 8
Joined: 22.Feb.2007
Status: offline

Hi All,

Got E2k7 Enterprise on a Win2k3 R2 x64 Ent server. All roles on one server.

Brand new install, no migration at all! (Although there have been failed attempts previous to me working here at E2k3 - so there was some stuff in AD from it but all I think has been removed)

Got bulk of E2k7 setup and work. (Send email, OWA, etc.) However when I try to connect an Outlook 2007 client up I get the "Bookmark is not valid" error message.
I've yet to find anything on the net that is just for E2k7, and the steps for resolving it on E2k3 regarding permissions have been done but no luck yet. (Used ADSI Edit to change permissons on the "Default Global Address List" container in AD. Even set to 'Everyone - Full Control' as a test but still same problem)

Can't find anything in the event logs.

Any help would be appreciated!

Cheers,

Steve.

Post #: 1

Featured Links*

RE: "Bookmark is not valid" Error when using ... - 7.Mar.2007 4:12:26 PM

stevehoot

Posts: 8
Joined: 22.Feb.2007
Status: offline

Solved it!!!!

Was an AD issue. Basically ran DCDIAG /V and NETDIAG /V on both Exchange server and all GC's in the forest and fixed any errors. (Found a problem on a DR backup server we have at a co-location that was causing it)

Once the tools showed a clean bill of health I booted all GC's (and DC's) to be sure and reinstalled. Everything worked fine after that!!!

Cheers,

(in reply to stevehoot)

Post #: 2