I've reviewed every post relevant to this topic and sought every resolution to no avail. Here is the chain of events: Updated Office 2007 Pro to Office 2010 which initially functioned correctly except for an address resolution issue when replying to an email. Forum posts here advised to delete mail profile from local machine and start from scratch, reattaching to Exchange. After deleting profile and restarting workstation and server, attempting to create the account in Outlook results in the above stated error. I have subsequently insured: all servers are connected and communicating with the correct DC the account resides in the GAL and is not hidden rebuilt the RUS deleted local .ost files uninstalled/reinstalled Office 2010 suite on workstation The user uses the same account to log in on both a desktop and a laptop. The laptop continues to function correctly and utilize all Exchange 2003 and Outlook 2010 services correctly. An attempt to create the account / profile on a different workstation running Office 2007 resulted in the same error. I posted this in the Client Forum as well. Any additional ideas for a resolution?

The first place to look is name resolution. Verify that you can ping your Exchange server using both DNS and NetBIOS. ping servername ping servername.domain.com Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

DNS is resolving correctly. Both pings successful.

Okay, post the exact sequence of steps and the full error message you receive. Please post exactly what you enter, please don't sanitize it.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Okay, here is the series: CLick on orb and click MS Outlook 2010 which brings up MS Outlook 2010 Startup box Next is the box asking if I want to configure an email account Next produces the Auto Account Setup window with options for E-mail Account, Text Messaging (SMS), and Manually configure server settings. Of note is this window does not auto populate the Name, Email Address settings as typical. Typing in this data along with password does not result in a connection. Chosing manually configure, Next, Microsoft Exchange, Next results in window seeking server name and user name. Entered Server Name, Entered User Name, Use Cached Exchange Mode selected, and clicked Check Name. Immediate window pop stating: "The name cannot be matched to a name in the address list." Click Ok results in another MS Exchange window pop asking for Server, Mailbox with Check Name button. At this point I simply cancel out as the name will not resolve and allow the creation of the account.

On Thu, 5 May 2011 15:04:31 +0000, jhollis01 wrote: >I've reviewed every post relevant to this topic and sought every resolution to no avail. Here is the chain of events: Updated Office 2007 Pro to Office 2010 which initially functioned correctly except for an address resolution issue when replying to an email. Forum posts here advised to delete mail profile from local machine and start from scratch, reattaching to Exchange. After deleting profile and restarting workstation and server, attempting to create the account in Outlook results in the above stated error. > >I have subsequently insured: all servers are connected and communicating with the correct DC the account resides in the GAL and is not hidden rebuilt the RUS deleted local .ost files uninstalled/reinstalled Office 2010 suite on workstation > >The user uses the same account to log in on both a desktop and a laptop. The laptop continues to function correctly and utilize all Exchange 2003 and Outlook 2010 services correctly. An attempt to create the account / profile on a different workstation running Office 2007 resulted in the same error. > >I posted this in the Client Forum as well. Any additional ideas for a resolution? I think you may have a problem with your domain controllers / global catalog servers. When you create the new profile, try putting the name of a working GC into the "Server" edit box. Does that work? Check DNS and the AD Sites and Services snap-in for any GCs that may have been incorrectly/incompletely removed. Your OL client may be trying to use a GC that no longer exists. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Placing the name of a working GC into the server box achieves the same results. Checked DNS and all GCs are correct. The OL client using the same AD account on a laptop continues to function properly. All other users on domain are functioning properly. I simply cannot get the Outlook profile to resolve on any other machine.

On Fri, 6 May 2011 15:37:59 +0000, jhollis01 wrote: > > >Placing the name of a working GC into the server box achieves the same results. Checked DNS and all GCs are correct. > >The OL client using the same AD account on a laptop continues to function properly. All other users on domain are functioning properly. I simply cannot get the Outlook profile to resolve on any other machine. What mailbox permissions are present on the mailbox? Does SELF appear in the list? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

In Exchange Advanced/Mailbox Rights, SELF is there with Read and Full Mailbox Access.

For grins try this: On the working laptop open regedit, hkcu\software\microsoft\windows nt\currentversion\windows messaging subsystem\profile\Bob Smith Highlight Bob Smith and Export the reg file. Log into the desktop and import reg file. Your outlook should work since you've basically copied the profile bypassing the setup. However doesn't explain why it's failing during the setup process especially on any other machines. You may have to report to using netmon and see if there's some strange firewall or communication issue going on. Also maybe move the mailbox to another store for grins.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

On Fri, 6 May 2011 16:44:07 +0000, jhollis01 wrote: >In Exchange Advanced/Mailbox Rights, SELF is there with Read and Full Mailbox Access. Do you get the same error if you use the legacyExchangeDN instead of the user's display name when you try to create a new profile? You can find the legacyExchangeDN value with LDP.exe or ADSIEDIT.msc. While you're there, check the showInAddressBook property, too. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

This resolution allowed Outlook to begin functioning again. While it provided resolution, you are correct in that it did not reveal the root issue. I will need to investigate further, but thank you for sharing this kernel of knowledge and assisting in getting this install back up and running.