Sync Log Errors in AT&T Office@Hand Cloud PBX for Microsoft Teams
Article #73325
This article lists the different sync errors in AT&T Office@Hand Cloud PBX for Microsoft Teams and their possible causes.
| Error |
Likely Cause |
| Management object not found for identity |
That typically occurs if the users have only recently been given licenses 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 find specified Gateway |
See Setup Partially Complete Error Message During Initial Sync on Microsoft Teams | AT&T Office@Hand for more information.
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 license 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. |
During the sync process, the Microsoft platform may return an error condition. If this occurs, the Sync Now button will show Sync Failure and display in red.
Review the logs, then check the error conditions and their possible causes as shown below.
| |
Wait and try again later. |
Cannot find specified Online
PSTN usage |
This message can occur when the tenant is setup and there are no licensed users to sync with the phone system. License some users and re-try.
The issue also can be caused by the Microsoft platform not being updated in time for the check. In this case wait and try again later. |
| PSERROR> Failed to start remote PowerShell -orUnexpected 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.
Remove the AT&T Office@Hand Cloud PBX for Microsoft Teams 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.
|
Key Words: AT&T Office@Hand Cloud PBX for Microsoft Teams, sync errors, sync log errors, sync failure, sync now log errors, sync failed, sync error explanation, sync error causes
Was this page helpful? Yes No
