BACK TO KB LIST

Unable to Create Folder (name: ) Error

KB ID:	3097
Product:	Veeam Backup for Microsoft 365
Version:	4.0.0.1345, 4.0.0.1553
Published:	2020-02-10
Last Modified:	2020-08-13

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

Oops! Something went wrong.

Please, try again later.

Challenge

The following error occurs when creating a folder in the S3-Compatible Object Storage bucket: "Unable to create folder (name: <folder_name>)".

User-added image

Cause

Certain S3-compatible API do not support an unsigned payload used by Veeam Backup for Microsoft 365 as the x-amz-content-sha256 authorization header. Applicable to builds: 4.0.0.1345, 4.0.0.1553.

Solution

Upgrade the Veeam Backup for Microsoft 365 server to version 4.0b (build 4.0.0.2516) or contact technical support to get a patch for version 4.0a (build 4.0.0.1553).

More Information

Veeam Backup and Replication and the S3-Browser tool (a 3rd party tool for S3 storage) are not affected.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

Product

Topic

Description

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Verify your email to continue your product download

We've sent a verification code to:

An email with a verification code was just sent to

Didn't receive the code? Click to resend in sec

Didn't receive the code? Click to resend

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.