OWApp Error selecting GAL contact - The recipient couldn´t be added. It doesn´t have an email address. - HELP

Hi all,

I need a help and if anyone can do that I appreciate:

- I have an Exchange 2013 CU environment with 4 Servers: 2 CAS (not in NLB) and 2 MBX (in DAG) that was migrated from Exchange 2007.

Everything works fine but when any user open his OWApp, create a new email, click on TO field, goes to GAL and click to select a contact (mailbox or DG) the error "The recipient couldnt be added. It doesnt have an email address." appears.

The users can search for a contact and pick it up, can type the contact and it is picked up but it is not possible clicking directaly on the contact from tha GAL.

In MS Outlook works fine, no issue.

Anyone knows that?

Thanks in advance.

Luiz

November 1st, 2013 8:43am

Hi Luiz

Do you have any GAL segregation done? This could be due to the OWA permissions...

Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 11:22am

Hi Siva,

no, I do not have a GAL segregation

Thanks.

Best Regards.

Luiz

November 1st, 2013 11:42am

Hey Luiz,

when you say Outlook works fine, is the OL client in cached mode or online mode? Why not try with online mode? also, if you have Active Sync devices, try from that too.

Is the issue same for all OWA users? or just specific?

if the issue is for a group of users specific to a location or a DB? see if there were any changes made around those areas. if specific to a DB or a couple of DBs' - try a clean-mailboxdatabase DBName

if the issue is specific to a user - try update-recipient -identity username

Pick a specific user for example - go to ADSIEdit and navigate to the properties of the AD object, check the proxyaddresses field and see whats in there? Also check the LegacyExchangeDN for that object and it should be no different that a working one.

Check the permissions applied to the Default Global Address list and see if something is missing

if the victims are specific to a DB - then see if that DB is using the Default Global Address list or not?

Was the OAB moved between servers recently?

Check this article - may be helpful - http://technet.microsoft.com/en-us/library/aa998569(v=exchg.150).aspx

Regards.

Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 12:05pm

Hi Siva,

In Outlook Online and Cached Mode works fine. I did not test using Active Sync yet, Siva.

Yes, all users are facing the issue. I have already created a new one and the issue occurs.

I have 3 DB and all mailbox on them facing the issue.

I already tried to update GAL and Recipeint, no success.

I already created a new Address List but with no success.

OAB was not moved.

I have a lab environment which there is no similar erro, I compared the GAL from the Lab to the problematic environment and no difference  unless the MSExchQueryFilter is different.

Any clue?

Thanks, Siva.

Best Regards.

Luiz

November 1st, 2013 2:24pm

Hey Luiz, by looking at what you are saying - I would suspect the problem might be with the Global Catalog Servers serving the OWA clients or CAS servers. How many GC's are available in your site? Could you please check your CAS servers as to which GC is connected to and make sure if thats the right GC and not a remote site GC.

If you notice a remote GC is being used, please change it to the right GC and restart the System Attendant service on the Exchange Servers. See if that works.

Also check your IIS logs to see any abnormal OWA permission issues are being reported?

Check if the ExchangeOAB share from OAB generation server is accessible from the CAS server. Disable any 3rd party apps that interact with GAL contacts like IP Telephony apps, Skype and so on.

Best of luck!

Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 3:03pm

... and hey one more thing - try to open the open URL from the CAS server directly and see if this happens. Also try to use the CAS server URL as the OWA url and check.

Who knows, this could be a simple IE issue... lol

November 1st, 2013 3:05pm

:-)

I did that and...it is not working.

Another clue? 

Thanks Siva.

Best Diwali

Free Windows Admin Tool Kit Click here and download it now
November 1st, 2013 3:33pm

Hey, thanks. Wish you the same!

Could you get me a Get-Serverhealth on the CAS servers? how many cas server do you have?

Also were you able to check the GC servicing the CAS servers?

Could you pls open the DNSMgmt and have a quick look on the DNS forward lookup zones and make sure your CAS and MB server entries are correct.

Im getting curious and I feel like walking by your office and take a look at this myself.. lol

November 1st, 2013 4:23pm

Thanks Siva.

Sorry by delay, I will send that information to you next monday, If it does not disturbing you.

I already checked the DC replication between the 3 DCs (they are GCs too) and there are no issues . 

All DCs are up, there are 2 in a AD Site (the Exchange Servers are in that site) and another DC is in a branch office.

I only did ping test but I will check the DNS entries.

The odd thing is I can open the contact from GAL using OWApp Light Mode.

Hahaha....there is a theory (a little bit funny) that say there is one person like us in some place of the world.

Thank you for your help, my friend. Take care.

Best Regards.

Luiz

Free Windows Admin Tool Kit Click here and download it now
November 2nd, 2013 7:46am

Hi,

Ran the command: "Update-GlobalAddressList -Identity "xxxxx" -v

What's the result?

Thanks,

Simon

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com

November 5th, 2013 10:14pm

Hi Siva, how are you?

Weel, sorry by delay but I have good and bad news.

The good news is I found the source of the issue: it occurs when I have in the environment a Windows Server 2008 SP2 DC and Exchange Server 2013 CU2.

The bad is I have to configure a Windows Server 2008 R2 or Windows Server 2013 as DC and the FSMOs must be located on one of those DC servers.

Thanks a lot for the help, Siva.

Best Regards.

Luiz

Free Windows Admin Tool Kit Click here and download it now
November 6th, 2013 2:02pm

Hello Luiz, Im doing well. Thanks.

Im glad that you were able to narrow down to the source of the problem. I dont understand why you need to promote another Domain Controller on Server 2008 R2 or Server 2012, but either way, the problem is specific to DC/GC that is servicing your Exchange server.

Exchange Server will automatically choose the GC (based on the server placements) and availability, so even if you promote another GC, I suspect the problem wont go away unless the GC placements are reviewed and changed. I would recommend you to post another question on the Windows Server Forums to see if someone has experienced this issue and perhaps ask for advice. Promoting a DC (in a pre-existing forest/domain) is a complex process and often involved with multiple prerequesites and a lot of thought process has to be put in place.

As far as the FSMO roles go, it is relatively easy to seize and transfer the roles between Domain controllers but needs more attention and planning.

All the best!

November 6th, 2013 2:51pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics