• Article for your preferred language does not exist. Below is international version of the article.

Article ID: 116303, created on Jun 20, 2013, last review on Nov 19, 2014

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

Symptoms

A customer cannot create Exchange mailbox, corresponding POA task 'Create mailbox with E-Mail Address ' fails with the error message like this:

Property expression "<value>" isn't valid.
Valid values are: Strings that includes '@', where '@' cannot be the last character
Property Name: UserPrincipalName

More detailed problem diagnostics is as follows:

Provisioning request failed. Error in 'SW ManagedExchange.CreateMailbox'.
Exception calling "Execute" with "3" argument(s): "Property expression "johndoe" isn't valid. Valid values are: Strings that includes '@', where '@' cannot be the last character Property Name: UserPrincipalName"

Error position:

At C:\Program Files\Parallels\Windows Provisioning Engine\Providers\Common\ProviderUtils\ProviderUtils.psm1:53 char:26
+ [void]$Context.Execute <<<< ($Provider, $Method, $exec_data)

Type: Parallels.Wpe.PowerShell.PowerShellException.

Cause

A Service User which a customer wants to create Exchange mailbox for an invalid login name. Service User login name must be in the e-mail address format, like user@example.com.

In the example of the failed task above it can be seen that Service User login name is just 'johndoe', it is invalid value. The screenshot below shows good Service User #775 and Service User #791 with incorrect login name:

serviceusers

Resolution

Log into POA Customer CP under the problem customer account, find the problem Service User at the 'Users' tab and either change login name for the problem user to the valid value (in the e-mail address format) or re-create Service User from scratch (if it does not have any service assigned yet).

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e e12cea1d47a3125d335d68e6d4e15e07 ac82ce33439a9c1feec4ff4f2f638899

Email subscription for changes to this article
Save as PDF