CMS12 site deployment error: The remote server returned an error: (412)

  • Updated
Description

When you deployed a CMS 12 site via a PowerShell script referring to this document, you may get below error message.

Failed to upload the blob. The error was: Exception calling "UploadData" with "3" argument(s): "The remote server
returned an error: (412) There is currently a lease on the blob and no lease ID was specified in the request.."
At C:\Program Files\WindowsPowerShell\Modules\EpiCloud\1.5.0\EpiCloud.psm1:501 char:17
… throw "Failed to upload the blob. The error was: $($_.Exc …
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CategoryInfo : OperationStopped: (Failed to uploa… the request..":String) [], RuntimeException
FullyQualifiedErrorId : Failed to upload the blob. The error was: Exception calling "UploadData" with "3" argume
nt(s): "The remote server returned an error: (412) There is currently a lease on the blob and no lease ID was spec
ified in the request.."
Cause and Solution

DXP system previously allowed to upload the same package multiple times (Add-EpiDeploymentPackage), but now the package is locked once it uploaded. The reason for that is because overwriting the package won't really make a difference, the site will use the original package anyway (on Linux environments).
So, the solution is to use a different name for .nupkg file (uplaoed package).