Applies To
Call2Teams - Customers
Latest Note
Microsoft are changing the name of the Phone System Licence to Teams Phone Licence. Please be aware that references to both may continue to co-exist for a time.
Overview
If you have searched our Knowledge Base for the Sync Error you have and cannot find it, this list may have the information your require.
| Message | Likely cause |
| Management object not found for identity | That typically occurs if the users have only recently been given licences in Office 365 and Microsoft is still setting them up behind the scenes. In the Office 365 admin portal they currently advise this can take 24 hours and have a link to click to see the Teams provisioning status of users. 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. Wait and try again later. |
| PSERROR> Failed to start remote PowerShell -or- Unexpected PS Runspace is null | Most likely cause is not being logged in as Global Admin when running sync.. 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. Also at the top of the log the admin role will be detailed. If this reads something like "Connected as 'tom@greenbackhealth.com' with roles: User Account Administrator" then this is clear that the logged-in user is not Company Administrator, which is the required role. |
| Domain takeover failed | The admin first logged in with the wrong global admin account (from another M365 tenant) and the Sync Now feature has created the same dns in the two different tenants. Either Delete the Teams service (trash can icon in Teams tab) and create new domains or remove the Call2Teams dns from the wrong Microsoft tenant and then the sync will work |
| The term 'Set-CsUser' is not recognized as the name of a cmdlet, function, script file, or operable program. | Most likely cause is not being logged in as Global Admin when running sync.. Look into the logs, the admin role will be detailed near the top. If this reads something like "Connected as 'tom@greenbackhealth.com' with roles: User Account Administrator" then this is clear that the logged-in user is not Company Administrator, which is the required role, 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, | Most likely cause is not being logged in as Global Admin when running sync.. Look into the logs, the admin role will be detailed near the top. If this reads something like "Connected as 'tom@greenbackhealth.com' with roles: User Account Administrator" then this is clear that the logged-in user is not Company Administrator, which is the required role, 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. You can 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 we have noted that on rare occasions, Microsoft can take several days. If you feel you have been waiting excessively long, you can always ask Microsoft for support, 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 you can see the upgrade Teams Connector button on the Teams Services tab, you should 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. It is advising that the item being added already exists. The command being executed will relate to one of the Sync Module sections. Firstly it is helpful to understand which section contains the error and then, using Chapter 5 of the Teams Admin Setup Guide, execute the PS 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 Qunifi cannot be held responsible for the content of any third-party documentation offered.