Sharepoint agent Differential or Incremental backup with GRT enabled fails with error: 0xe0001602 - Access is denied

  • Article ID:100028554
  • Modified Date:
  • Product(s):


When performing a differential or incremental Sharepoint Agent backup with Granular Restore Technology (GRT) enabled, the job may fail with an Access Denied error.

Error Message

Final error: 0xe0001602 - Access is denied (SharePoint backup).
Final error category: Security Errors

Additionally within the individual backup set where the Sharepoint Content Database is backed up this message is seen:

This backup set may not contain any data.

This message shows up because the failure occurs during the GRT cataloging phase but the data is indeed backed up and a full database restore is possible.


First, be sure that all backups of a sequence (full+diff/inc) go to the same backup device type (tape or disk/dedup). 

Second, be sure that all backups of a sequence still exist, ie: for an incremental to work, all prior incrementals and the original full backup should still exist. 

If neither of these resolves the issue, use the following workaround:

Perform only full backups of the Sharepoint Content database resources.


Veritas Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Veritas Corporation is committed to product quality and satisfied customers.
  This issue is currently under investigation by Veritas Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.


Was this content helpful?

Get Support