Error while user email creation in exchange server in SAP IDM 7.2

[Former Member]

Hi Team,

We are getting few errors while creation of email account in exchange server. We are using To custom pass to create user email in exchange server.

Please find below error logs:

1> Exception: com.sap.idm.ic.ToPassException: ERROR: Cannot process argument transformation on parameter 'PrimarySmtpAddress'. Canno

t convert value "undefined" to type "Microsoft.Exchange.Data.SmtpAddress". Erro

r: ""undefined" is not a valid SMTP address"

2> Exception: com.sap.idm.ic.ToPassException: ERROR: This task does not support recipients of this type. The specified recipient mod

elo.gmodelo.com.mx/Fabricas/Usuarios/Mazatlan/Yemil Aviles De Leon is of type U

serMailbox. Please make sure that this recipient matches the required recipient

type for this task.

Regards,

Saurabh Kumar

[former_member201064]

The second exception occurs when there's already a mailbox. At least this message returns the mail creation task uses the powershell command Enable-Mailbox on an already existing mailbox. Most of the times this happens during the "reprovision AD" task sequence which I created.

[Former Member]

Hi Saurabh,

Need to check if you are using To Custom pass and attribute is 'smtp' in Destination tab the attribute value user 'email id' might be is 'undefined' or empty value, please ensure that the script is not returning empty value or mail domain server name is incorrect.

[former_member2987]

Hi Saurabh,

Is it happening just for this one user or is it happening for all users that you are trying to provision?

If it's just for this one person, look for any extended characters.  Maybe something with an accent?

Regards,

Matt

[Former Member]

Hi Matt,

Thanks for your reply.

It is happening for few cases like 5-10% cases.

We have checked the name for failure cases and its not because of any accent.

Ex: saurabh.kumar@domain

Let me know in case of any further input needed from our end.

Regards,

Saurabh

[former_member2987]

Hi Saurabh,

That's weird.  Usually when I see something like this it's because of an embedded accented character.  Are there any corresponding errors showing up on the Exchange side?

Matt