the recipient couldn't be added. it doesn't have an email address.

Hi,

when click the TO: field and choosing a user from the GAL and double click it I get:

"The recipient couldn't be added. it doesn't have an email address."

When I search for a name, I get the Contact including the email adress, when i click the address it gets added to the TO field.

September 11th, 2013 5:54pm

Hi,

In order to troubleshoot the issue more efficiently, I need to clarify one thing.

Did the issue occur in OWA or Outlook?

If the issue occurs in Outlook Cached Mode, I recommend you check whether the issue occurs in Outlook Online Mode.

If the issue doesn't occur in Outlook Online Mode, I recommend you update OAB manually to check the result.

If there are any problems, please feel free to let me know.

Best regards,
Belinda

Free Windows Admin Tool Kit Click here and download it now
September 12th, 2013 5:41am

It only occurs in OWA

In Outlook, cached or not, all is fine.

In OWA it seems it does not load all information from the GAL, only when I search for the names it does a proper search with all the informations.

September 12th, 2013 8:29am

Hi,

Based on your description, the issue may be related to browser version.

I recommend you check the result with another browser.

Best regards,
Belinda

Free Windows Admin Tool Kit Click here and download it now
September 12th, 2013 9:52am

I did, it is the same in IE, Chrome and Firefox
September 12th, 2013 10:42am

Hi,

I recommend you use the Get-ServerHealth cmdlet to retrieve health information related to the server you specify.

In order to troubleshoot the issue more efficiently, I recommend you check whether there is any error message on the event log with Exchange.

Could you please post the error message here at your convenience?

Best regards,
Belinda

Free Windows Admin Tool Kit Click here and download it now
September 13th, 2013 1:22am

I could not find a error in the event log that i could connect to the problem.
I however found issues with the healthmailbox:


Process MSExchangeHMWorker.exe (ExHMWorker) (PID=5324). Recipient object CN=HealthMailboxedbb5fd503374b2893697d6c87e091dc,CN=Users,DC=intra,DC=mimoon,DC=de read from pdc.intra.mimoon.de failed validation and will be excluded from the result set.  Set event logging level for Validation category to Expert to get additional events about each failure.

Also I did run the get-serverhealth and found some unhealthy entries:

Server          State           Name                 TargetResource       HealthSetName   AlertValue ServerComp
                                                                                                     onent     
------          -----           ----                 --------------       -------------   ---------- ----------

DE-MAIL1-W2K12  NotApplicable   HealthManagerHear...                      Monitoring      Unhealthy  None      
DE-MAIL1-W2K12  NotApplicable   MaintenanceFailur...                      Monitoring      Unhealthy  None      .
DE-MAIL1-W2K12  NotApplicable   OwaIMInitializati... OWA.Protocol.Dep     OWA.Protocol... Unhealthy  None      
DE-MAIL1-W2K12  NotApplicable   MailboxMigrationC... MailboxMigration     MailboxMigra... Unhealthy  None   
DE-MAIL1-W2K12  NotApplicable   Mapi.Submit.Monitor  MailboxTransport     MailboxTrans... Unhealthy  None      
DE-MAIL1-W2K12  NotApplicable   MailboxDeliveryAv...                      MailboxTrans... Unhealthy  None   




September 13th, 2013 1:07pm

Hi,

According to my knowledge, the error message indicates that the recipient object specified in the event description is in an inconsistent state.

To resolve this warning, please follow these steps below:

First, please increase diagnostic logging so that you can determine which attributes or properties contain invalid values.

Specifically, increase the diagnostic logging level on the Validation counter of the MSExchangeADAccess performance object.

You can increase logging by running the following Exchange Management Shell cmdlet: Set-EventLogLevel MSExchangeADAccess\Validation -Level High.

Secondly, please review the additional MSExchangeADAccess events in the Application log to determine which attributes or properties contain invalid values.

Note: After you have completed troubleshooting this issue, return logging to the default level by running the following cmdlet: Set-EventLogLevel MSExchangeADAccess\Validation -Level Lowest.

For detailed information about increasing logging, see http://technet.microsoft.com/en-us/library/3030124a-ac14-4d45-afc0-a06b9ce9ce39.aspx.

Best regards,
Belinda

Free Windows Admin Tool Kit Click here and download it now
September 16th, 2013 2:49am

the health mailbox has no Database set.

The homeMDB is not set.

Can I delete thoses boxes from AD?
I suspect those are left from an DB we deleted.

September 16th, 2013 3:42pm

The only option you have for now is to delete those accounts from Active Directory Users and Computers.
Free Windows Admin Tool Kit Click here and download it now
September 16th, 2013 4:12pm

OK, that solved the error in the event log from the health boxes.

But sadly the initial problem still persists.
When I try to add an recipient from the GAL in OWA I get:

http://imageshack.us/a/img716/8962/ys9m.jpg

when I search for the name it works:

http://imageshack.us/a/img818/475/rj2c.jpg

Any idea what could cause this?

Or what logging to activate?

September 19th, 2013 8:51pm

could you solve it? Because we have exactly the same strange behavior as discribed in the last post.
Free Windows Admin Tool Kit Click here and download it now
April 30th, 2014 3:29pm

Hi all,

I have the same problem with Exchange Server 2013 SP1. Please help.

Thank you.

July 29th, 2014 2:33pm

I have the same problem too.

Please help.

Free Windows Admin Tool Kit Click here and download it now
March 25th, 2015 10:43am

I too am having the same issue. Please advise.

Kevin

April 7th, 2015 1:54pm

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

Other recent topics Other recent topics