Article ID: 126646, created on Aug 23, 2015, last review on Aug 23, 2015

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

Symptoms

Task related for Lync phone number assignment task with the following error:

Application configuration script reported errors: 'Execution problem. See the inner exception.
Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Filter failed to return unique result, "[SipAddress : sip:test.user@domain.com] [LineURI : tel:+123123123] [PrivateLine : tel:+123123123] "

Cause

The issue can occur if the task is trying to assign phone number to Lync account while the same phone number is used by another object in Lync infrastructure (e.g. another user, call group, conference dial in settings etc.)

Resolution

To resolve the issue it is needed to find out the object which has the same number:

Get-LyncNumberAssignment -Number "+123123123"
LineUri       : TEL:+123123123
DisplayName   : TEST
SipUri        : sip:testconf@test.com
Type          : DialInConf
RegistrarPool : testpool.com

and reassign it if needed. For example, it can be achieved using this script.

Search Words

Execution problem: Command execution stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: Filter failed to return unique result

Provisioning "LyncUserLicense" for APS application Microsoft Lync Hosting Pack v2

Filter failed to return unique result

Lync Filter failed to return unique result

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF