Outlook Sync Issues

Synchronization issues are something that seem to plague any Exchange Admin. They come up for no reason, and go away for no reason. There have been a number of posts on the issue over the years, most telling MS to go fix their issues.

One particular issue that I've seen recently is when moving a database from one Exchange 2010 DAG Member to another, the Sync Issues folder starts filling up with the following Synchronization Log messages:

7:57:57 Synchronizer Version 15.0.4701

7:57:57 Synchronizing Mailbox 'User Name'

7:57:57 Synchronizing Hierarchy

7:57:58 Synchronizing server changes in folder 'Inbox'

7:57:58 Downloading from server 'Client-Access-Server'

7:57:58    1 item(s) added to offline folder

7:57:58 Error synchronizing folder

7:57:58                   [8004010F-501-8004010F-0]

7:57:58                   The client operation failed.

7:57:58                   Microsoft Exchange Information Store

7:57:58                   For more information on this failure, click the URL below:

7:57:58                   http://www.microsoft.com/support/prodredirect/outlook2000_us.asp?err=8004010f-501-8004010f-0

7:57:58 Canceled

Checking all the normal locations, there is nothing wrong with the synchronization, yet every 5 minutes Outlook reports an error synchronizing. The above example is with Outlook 2013 on Exchange 2010 SP3 RU6, but I've seen it through several Service Packs and Rollups. The issue also shows up on Outlook 2010.

Looking through all the settings on the Exchange DAG Members, and the Client Access Server in use (which doesn't change during the failover), there is nothing out of the ordinary that might keep it from syncing.

If I find a solution to this particular issue, I'll post it back here for posterity. Until then, this is merely another "Microsoft, please fix you're sync problems" blog.

------
Dustin Shaw
VCP

Brother ControlCenter4 Scanning Permissions

Brother ControlCenter4 Scanning to File requires certain permissions to write files to the folder. These permissions use the current logged in user permissions. To test that the write permissions are accessible, ControlCenter4 appears to write a .tmp file and create a temp folder. I say appears because I have not found any documentation on the subject.

I ran across these required permissions because a scanner I support was trying to write to a network share that allowed Full Access MINUS the ability to create folders. Without the ability to create folders, it would drop a .tmp file in the folder on scan, and pop up an Unable to write the file to "Destination Folder". error like the below:

Once I assigned the user the ability to create folders in this directory (only), ControlCenter4 was able to scan properly.

------
Dustin Shaw
VCP