Symptoms
Affected VDP version: 6.1.3 VDP FLR intermittently failed with error code 10007, 'VmwareFlrWs.log' reported error like [VFW - DEBUG] 2016-12-02T01:41:54.362Z TID=14xxxxxxxx MID=8xxx: __flr__GetErrorDescription: In sufficient access to the MountPoint
Cause
FLR UI makes separate calls to FLR Rest API to get information. For example, browse backup, browse destination, restore. An available thread is automatically assigned to the FLR Rest API. This thread may have been used in previous calls and keeps a "live" connection to the MCSDK. When calling MCSDK to restore, if the MCS connection's last action was a browse backup, MCS associates the browse and restore operations. It is more efficient to use the same connection so MCS doesn't have to create new host sessions and mounts to the backups. However, with FLR, there is no way to guarantee that the same thread/connection is used for browse and restore. If the restore is assigned a thread that had been used by a previous browse for a different backup, then the backups for browse and restore don't match and MCS restore job fails with "In sufficient access to the MountPoint".
Resolution
As a workaround, restart VDP FLR service:
Login VDPRestart VDP flr service by running
service vmwareflr restart
The permanent solution is upgrading to VDP 6.1.4 which will be released in Q1 of 2017
