Search Engine: Elastic

Article ID: 116639, created on Aug 5, 2013, last review on Sep 10, 2014

  • Applies to:
  • Operations Automation


A customer created a service user with login in POA Control Panel and assigned Lync 2010 service to it.

POA created the background POA task with the name like 'APS application 'Microsoft Lync 2010', id 131, instance 2292 -> service 'User_Profile', instance 167027: executing configuration script' to provision ordered service to the user.

The task fails with the following error message:

[ERROR]: Limit of execution time was exceeded. Process will be killed. Should be rescheduled.

The error message may be found in the application-log.txt file on the Provisioning Gateway Host which is used to execute provisioning scripts from the Lync 2010 APS application.

Also, the mentioned above log file contains the following entries which show that provisioning script is trying to find the required user in Active Directory and cannot do that:

[04/08/2013 17:55:19]user upn:
[04/08/2013 17:55:19]Trying to get user principal name...
[04/08/2013 17:55:20]done : johndoe@hosting.local
[04/08/2013 17:55:20]Still is not valid. Wait for correct value.
[04/08/2013 17:55:25]Trying to get user principal name...
[04/08/2013 17:55:25]done : johndoe@hosting.local
[04/08/2013 17:55:25]Still is not valid. Wait for correct value.
[04/08/2013 18:00:15]done : johndoe@hosting.local
[04/08/2013 18:00:15]Still is not valid. Wait for correct value.

The task also may fail with the error message like below:

Management object not found for identity "CN=johndoe,OU=S001000101,OU=Provider,OU=Hosting,DC=hosting,DC=local". 

The problem may appear not only for the newly created user with Lync 2010 service, the task may fail if a customer modified existing user with this kind of service assigned.


The user for which the customer is trying to provision Lync 2010 service is absent in Active Directory. Lync 2010 provisioning script cannot find the required user and throws error.

This may happen because the user was not created at all (e.g. because corresponding POA background task was canceled), or user was deleted/renamed manually in AD, or due to problem with AD synchronization between domain controllers.


First of all, try to re-execute the failed task in POA.

If the task does not go through check if the problem user exists in Active Directory.

If the user does not exist - cancel the existing task, remove the problem service user in POA Customer Control Panel and re-create it from scratch.

Additional Information

See also Knowledgebase article #117056 about the problem with similar diagnostics.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF