Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MAPI Client (Outlook): Bookmark is not valid error

Status
Not open for further replies.

Stevehewitt

IS-IT--Management
Jun 7, 2001
2,075
GB
Hi Guys,

Got a brand new Windows 2003 R2 x64 server installed and then installed Exchange 2007 Ent. No problems so far. OWA checks out good, sent a first test message and all great.

When I try to connect Outlook 2007 to the Exchange Server I get an error stating:

The name cannot be resolved. The bookmark is not valid.

Not getting much else in terms of errors in the event logs (GC/DC, Exchange or client)

Any advice really appreciated!

Thanks,




Steve.

"They have the internet on computers now!" - Homer Simpson
 
Thanks for the Pat. Found that link earlier on but unfortunatly I have no idea how to set permissions on the GAL. Any advice on this would be great.
(To be honest, I am having a very hard time adjusting to using 2007 compared to the little 2003 admin I used to do - where the hell is the AD U&C Integration gone?!)

Cheers.





Steve.

"They have the internet on computers now!" - Homer Simpson
 
It has been removed. Its a "feature".

You now manage the bits I think you want through the Exchange Manager a la Exchange 5.5 rather than forwards through AD.
 
Cheers. Trust Microsoft!

I've done some digging around and changed the ACL on the Default Address List container in AD using ADSI Edit (don't use Exchange 2003). Even set Everyone to Full Access but no luck.

Any other ideas appreciated.

Cheers,




Steve.

"They have the internet on computers now!" - Homer Simpson
 
On the Outlook front, try outlook /resetfolders and see if that helps.
 
No luck with that either.

FYI this is happening on all computers and all mailboxes. Also I uninstalled Exchange and reinstalled, leaving all defaults in place. Added a single mailbox and tested.

Exactly the same issue.

Any other ideas people?

Cheers again,





Steve.

"They have the internet on computers now!" - Homer Simpson
 
FYI Guys the solution was AD.

DCDIAG /V and NETDIAG /V on my DC's in each site for each domain, and also on the Exchange server.

Also, make sure all DC's are rebooted after you install Exchange, followed by testing replication.




Steve.

"They have the internet on computers now!" - Homer Simpson
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top