Task Using Wasabi S3 Fails With "XML error: [Error document empty.]. Error code: [13]."
Challenge
A task targetting Wasabi S3 storage fails with the error:
[Error document empty.]. Error code: [13].
Cause
The Veean application sent Wasabi a request for data. Wasabi responds claiming the file exists, but the document is actually empty.
Example
This content is from an environment where S3 verbose logging has been enabled, which is not necessary to troubleshoot this issue; it just makes the requests and responses become listed in the logs to clarify the issue.
Solution
More Information
Enabling S3 Verbose Logging Mode
The log files for tasks interacting with S3 storage (non-vendor specific) will contain basic logging of S3 interactions. To enable verbose S3 request and response interaction logging, create the following registry value on the machine(s) acting as Veeam Backup & Replication Gateway for S3 interactions.
Note: This value should be set to 0 or removed when not needed, as it will dramatically increase the size of the log files.
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value Name: S3VerboseLoggingMode
Value Type: DWORD (32-Bit) Value
Value Data: 1 [ 1 = enabled / 0 = disabled ]
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.