All our users kept getting:
|
1 2 3 |
There was a problem, but sync will try again. (0x80c80317) |
On the server we kept getting the following event:
|
1 |
The Windows Sync Share service failed to setup a new sync partnership with a device. Database: \\?\S:\users\SyncShareState\WorkFolders\Metadata; User folder name: \\?\S:\WorkFolder\WORKFOLDERS_ROOT\USER.TEST; Error code: (0x8e5e0408) Unable to read from or write to the database. |
To fix it:
- I failed the roles over and rebooted both nodes of the cluster, nothing.
- I disabled restarted the sync share through the server admin console,
- I’ve tried to rename the metadata on the client:
|
1 |
C:\Users\User\AppData\Local\Microsoft\Windows\WorkFolders\Metadata |
- I’ve tried repairing a user which seems broken:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
Repair-SyncShare -name workfolders -user Domain\test Repair-SyncShare : (0x80c80317) There was a problem, but sync will try again. At line:1 char:1 + Repair-SyncShare -name WorkFolders -user Domain\test + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo: NotSpecified: (Msft_SyncShare (Name = "MA_Userfiles"):Root/Microsoft/.../Msft_SyncShare) [Repair-SyncShare], CimException + FullyQualifiedErrorId : HRESULT 0x80c80317,Repair-SyncShare |
So here’s the weird thing, I tried the following which seemed to fix it (I’ve no idea why):
|
1 |
Get-SyncUserStatus -User domain\test -syncshare WorkFolders |
So to apply to all users (which also worked), first I gained the users from the AD group I used (I dont have the AD functions on my work folders server):
|
1 2 |
Get-ADGroupMember -Identity "Workfolders Users" | select SamAccountName | Export-Csv c:\temp\WorkFolders.csv |
Then used the CSV to apply the Get-SyncuserStatus to all users:
|
1 2 3 |
$List = Import-Csv C:\temp\WorkFolders.csv foreach ($user in $list) { Get-SyncUserStatus -User $user.SamAccountName -syncshare WorkFolders} |
