Feb 22

Walkaround: Workfolders error 0x80c80037 – No sync share is configured for the user.

Walkaround: Workfolders error 0x80c80037 – No sync share is configured for the user.

I am still trying to figure out why Workfolders works at times and then it complete stops working indicating the following error messages:

Log Name: Microsoft-Windows-SyncShare/Operational
Source: Microsoft-Windows-SyncShare

Event ID: 4016

Description:
No sync share is configured for the user. User: UserName; Error code: (0x80c80037) You’re not set up on the server. Email your organization’s tech support and ask them if they can give you access to Work Folders.

Log Name: Microsoft-Windows-SyncShare/Operational
Source: Microsoft-Windows-SyncShare

Event ID: 4015

Description:
There was a problem retrieving a user attribute from Active Directory Domain Services. This can occur if this server could not reach a domain controller or if the attribute has not been set.
No action is required unless you deployed Work Folders with multiple sync servers, want users to automatically discover their sync server, and the msDS-SyncServerUrl user property is listed below.
User: UserName; User property: msDS-SyncServerUrl; Error code: (0x80c80036) ECS_E_AD_PROPERTY_NOT_FOUND

I am still uncertain what causes this issue, and going through my event log I can see that an entire month can go by but then it comes back. There is nothing additional that provides any insight as to why it happens.

Update 1:

This seems to be triggered by a server restart. Based on the error message that an AD property was not found I am willing to bet that I need to apply the 2012 R2 schema again on my DC. I am using Windows 2012 Essentials R2 so I figured this wouldn’t be an issue but I can’t argue with the event logs. Also, because it only happens when I reboot my server I am guessing it is because it loses a setting over the reboot (can’t retrieve it on boot) so it is consistent with the theory. I’ll give it a shot and report back on it. I have also tried setting WorkFolders on an entire different server and I can replicate the behavior so that reinforces the idea something in AD is wrong.

(BTW, I guess I just confessed I didn’t reboot my server for a month, lol.)

The Walkaround

Sometimes all I have to do is to click on “Stop using Workfolders” my client machine and then configure Workfolders again to get this working again… but it does not work all the time. What does seem to do the trick is going to my Workfolders server and remove my Workfolders Sync Share. After that I create a New Sync Share and voila! Generally speaking my client machine manages to figure out its the same work folder and after several minutes confirms the delta to perform a sync if needed. Just one time it decided to go ahead and sync my 1.42TB again! I’ll probably go to the office and plug my computer to the network there because it might take a whole month if not more over my home network.

Where to find the WorkFolders logs

Sometimes it is hard to find the WorkFolders logs. This is because the logs are not found in the same location on a client machine and a host machine. Below are the routes for the logs inside the event viewer:

  • The Host / Server logs can be found at: 
    • Windows logs
      • \ Microsoft
        • \ Windows
          • \ Sync Share
  • The Client logs can be found at:
    • Windows logs
      • \ Microsoft
        • \ Windows
          • \ WorkFolders

Each section is comprised of two sections/logs/channels. In the case of the server log you have the Operational and the Reporting ones while in the client you have the Operational and the ManagementAgent ones.

How to use PowerShell to monitor WorkFolders

As you would expect with Windows Server 2012 R2, WorkFolders has a PowerShell module at your disposal (try gcm –m SyncShare to see all available options).

Get-Service – The Sync Share service (named SyncShareSVC ) status can be read by using PowerShell’s generic get-service command.

Get-SyncShare   The Get-SyncShare cmdlet provides information on sync shares. This includes the file system location, the list of security groups and more.

Get-SyncUserStatus – This cmdlet provides Work Folders users’ information which includes the user name, the devices that the users are using, last successful connections among others.

Enhanced by Zemanta

2 comments

    • Tony on December 7, 2015 at 8:24 am
    • Reply

    any more updates? have the same problem.

    1. No, not really. I ended up reinstalling the server and even active directory in hopes a fresh install would work… but no luck. Every time I restart the server I encounter the error. What I end up doing as a workaround is to disable and re-enable a feature of work folders (like encryption) and somehow that forces the system to reload the settings and work again. If you find a way to fix it let me know, I ended up going with SharePoint as this was becoming too much of a nuisance.

Leave a Reply

%d bloggers like this: