Applies To
Call2Teams - Customers
Note:
Microsoft use references to both Phone System Licence to Teams Phone Licence in their documentation.
These are the same thing, describing the license required to enable Direct Routing (PSTN).
Overview
This is a table of additional Sync errors, supplementary to those found elsewhere in this support Knowledge Base:
| Message | Likely cause |
| Management object not found for identity | Typically occurs if the users have only recently been given licences in Office 365 and Microsoft is still setting them up behind the scenes. The Office 365 admin portal currently advises that this can take 24 hours, and offers a link to see the Teams provisioning status of users. Advice: Wait and try again later. |
| Cannot modify the parameter: "EnterpriseVoiceEnabled" because it is restricted for the user service plan: MCOProfessional | This means the Sync process sees the user has a Phone System licence in one of Microsoft's systems, but this has not been propagated to the Microsoft subsystem responsible for voice yet. "MCOEV" is the Phone System plan, and if this is not listed in the error message then the Skype for Business PowerShell server does not see it yet. Advice: Wait and try again later. |
| PSERROR> Failed to start remote PowerShell -or- Unexpected PS Runspace is null | The most likely cause is not being logged in as Global Admin when running sync. Advice: Look into the logs further for messages like "No cmdlets have been authorized for use by the RBAC role that the user belongs to" to confirm this. If the log shows something like "Connected as 'name@example.com' with roles: User Account Administrator" then this is the cause of the issue. Company Administrator, is the required role. |
| Domain takeover failed | The admin first logged in with a global admin account from another M365 tenant, and the Sync Now feature has created the same DNS in the two different tenants. Advice: Delete the Teams service (click the trash can icon in the Teams tab) and create new domains, or remove this service's DNS from the incorrect Microsoft tenant. Run sync again. |
| The term 'Set-CsUser' is not recognized as the name of a cmdlet, function, script file, or operable program. | The most likely cause is not being logged in as Global Admin when running sync. Advice: Check the logs, the admin role will be detailed near the top.The required role is Company Administrator. If the log shows something like "Connected as 'name@example.com' with roles: User Account Administrator" then this may be the cause of the issue. In the Microsoft 365 admin center, ensure the 'Global Admin' role is assigned to the user running the sync. |
| The term 'Get-CsMeetingRoom' is not recognized as the name of a cmdlet, | The most likely cause is not being logged in as Global Admin when running sync. Advice: Check the logs, the admin role will be detailed near the top.The required role is Company Administrator. If the log shows something like "Connected as 'name@example.com' with roles: User Account Administrator" then this may be the cause of the issue. In the Microsoft 365 admin center, ensure the 'Global Admin' role is assigned to the user running the sync. |
| Cannot modify the parameter: "OnPremLineURI" as the user has dirsynced onpremise LineURI | This error occurs because the user is set on the portal to be DirSynced. Read more about DirSync here: OnPremLineURI |
| Failed To Validate Domain | Microsoft may be taking longer than usual to configure the domains we need setting up. Subsequent revisits to the Sync button in Call2Teams should eventually resolve this but on rare occasions, Microsoft can take several days. Advice: Raise a support ticket with Microsoft, quoting the relevant lines from the sync log. See the section: Setup Partially Complete - Domains Waiting Activation |
| An error occurred while creating the pipeline | The usual reason for this is because the Teams Service Connector is out of date. If the upgrade Teams Connector button on the Teams Services tab shows, consider upgrading. |
| An item with the same key has already been added | This error can appear in the Sync Logs at any point where an entry is being made. The error indicates that the item being added already exists. The command being executed will relate to one of the Sync Module sections. Advice: Find which section contains the error. Using Chapter 5 of the Teams Admin Setup Guide, execute the PowerShell commands for that section manually. This will identify the duplicated parameters so action can be taken. Usually this action involves removal of the previous item in the MS tenant. |
Disclaimer
Please note Dstny Automate cannot be held responsible for the content of any third-party documentation offered.