Work Folders Syncing

Posted by robd on July 03, 2017
Work Folders

All our users kept getting:

There was a problem, but sync will try again.



On the server we kept getting the following event:

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:
  • I’ve tried repairing a user which seems broken:
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):

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):

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:

$List = Import-Csv C:\temp\WorkFolders.csv
foreach ($user in $list) {
Get-SyncUserStatus -User $user.SamAccountName -syncshare WorkFolders}


Tags: ,

5 Comments to Work Folders Syncing

  • Hi there, this is an interesting read. We are about to roll out Work Folders and I wonder what your experience of the technology has been like, as it seems most are going O365/OneDrive? I couldn’t contact you via the ‘About Me’ page but perhaps if you could drop me an email we could chat a bit?

  • There is a permanent fix for this.
    Give for a Groupe who use WF access to SyncShareState with rights “Edit”.

    • After more digging turns out that under:

      “XYZ:\SyncShareState\Workfolders” the group “local service” is there as “denied”.

      Give “local Service” premission “allowed”.

      Restart Server

      If you get “0x80070057” after that, it should be gone after some time.

      Hope this helps!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.