Setting up OneDrive for Business successfully completed sign-in and two factor authentication, but failed on final step with error:
Sorry, OneDrive can’t add your folder right now
Please contact support.
Taking a trace with Fiddler showed a HTTP 501 error occurring:
HTTP Request
GET https://mycompany-my.sharepoint.com/personal/malcolm_mccaffery_mycompany_com_au/_api/SPFileSync/sync/a5dbb123de934919a713088f2308a099/RootFolder HTTP/1.1
Connection: Keep-Alive
Accept-Language: en-AU
Cookie: SPOIDCRL=…
User-Agent: Microsoft SkyDriveSync 17.3.6799.0327 ship; Windows NT 6.3 (9600)
Application: OneDriveSync
X-MachineDomainInfo: {19B44062-2A9A-4D7E-AF96-92F286583EA3}
X-MachineId: 565a5069-f661-462d-8b1e-f138a34a14d1
X-RequestStats: btuc=0;did=380d4a0e-68e8-ca9e-abea-ca20c1862c8f;ftuc=0;
X-TransactionId: …
Host: mycompany-my.sharepoint.com
HTTP Response
HTTP/1.1 501 Not Implemented
Cache-Control: private, max-age=0
Expires: Sat, 06 May 2017 11:06:03 GMT
Last-Modified: Sun, 21 May 2017 11:06:03 GMT
Server: Microsoft-IIS/8.5
X-SharePointHealthScore: 0
X-SP-SERVERSTATE: ReadOnly=0
X-SyncError: 3031
X-ClientErrorCode: MachineIsNotAllowedToSync
SPClientServiceRequestDuration: 26
SPRequestDuration: 83
X-AspNet-Version: 4.0.30319
SPRequestGuid: c5cdf39d-5091-3000-fc55-e85a5fc44411
request-id: c5cdf39d-5091-3000-fc55-e85a5fc44411
Strict-Transport-Security: max-age=31536000
X-FRAME-OPTIONS: SAMEORIGIN
X-Powered-By: ASP.NET
MicrosoftSharePointTeamServices: 16.0.0.6511
X-Content-Type-Options: nosniff
X-MS-InvokeApp: 1; RequireReadOnly
P3P: CP=”ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI”
Date: Sun, 21 May 2017 11:06:04 GMT
Content-Length: 0
On a working machine the request only had two differences
GET https://mycompany-my.sharepoint.com/personal/malcolm_mccaffery_mycompany_com_au/_api/SPFileSync/sync/a5dbb123de934919a713088f2308a099/RootFolder HTTP/1.1
Connection: Keep-Alive
Accept-Language: en-AU
Cookie: SPOIDCRL=…
User-Agent: Microsoft SkyDriveSync 17.3.6798.0207 ship; Windows NT 6.3 (9600)
Application: OneDriveSync
X-MachineDomainInfo: {8ABF2899-769C-4892-B86C-7DDE44C75D1F}
X-MachineId: 565a5069-f772-462d-8b1r-g138a41a14e5
X-RequestStats: btuc=0;did=c97f4f1a-9ffd-3100-313d-6cf40b68bab4;ftuc=0;
X-TransactionId: …
Host: mycompany-my.sharepoint.com
The reason for the failure is client has implemented tenant sync client restriction by domain GUID; the failing device is on a different domain than those that had been allowed.
This can be fixed by running PowerShell cmdlet to enable all required domain GUIDs, like so:
Set-SPOTenantSyncClientRestriction -Enable -DomainGuids “786548DD-877B-4760-A749-6B1EFBC1190A; 877564FF-877B-4760-A749-6B1EFBC1190A”
To workout domain GUIDs in an environment you can use the following PowerShell cmd:
$domains = (Get-ADForest).Domains; foreach($d in $domains) {Get-ADDomain -Identity $d | Select ObjectGuid}
The domain’s objectGUID can also be viewed with tools like ADExplorer
We also learn that by using Fiddler you can get much better info about the reason for OneDrive error message, then OneDrive offers…
You can simulate a different Domain GUID by using Fiddler AutoResponder feature:
