- 11 Apr 2023
- 3 Minutes to read
- Print
- DarkLight
Move File from Azure Storage Blob
- Updated on 11 Apr 2023
- 3 Minutes to read
- Print
- DarkLight
Step Details | |
Introduced in Version | 4.0.0 |
Last Modified in Version | 7.12.0 |
Location | Integration > Azure Storage |
The Move File from Azure Storage Blob step moves a file (blob) from one directory to another directory within the same container in Azure Blob Storage. This allows developers to reorganize files and directories within a container without having to delete and recreate them.
Prerequisites
This step requires the Azure module to be installed before it will be available in the toolbox. In addition, the step will require the connection string for an Azure Storage account that has access to the container.
Properties
Inputs
Property | Description | Data Type |
---|---|---|
Connection String | The connection string for an Azure Storage account. This can be located by navigating to the Storage Account within the Azure Portal, then selecting Access Keys to display the connection string. | String |
File Name | The name of the file within the storage container. | String |
From Container Name | The name of the container as it appears in Azure to remove the file from. | String |
From Directory | The name of the directory as it appears in Azure to remove the file from. This input is optional. | String |
To Container Name | The name of the container as it appears in Azure to move the file to. | String |
To Directory | The name of the directory as it appears in Azure to move the file to. This input is optional. | String |
Outputs
Property | Description | Data Type |
---|---|---|
Error Message | Provides a detailed error message, including the Status and Error Codes. | String |
Example Inputs and Outputs
Connection String | File Name | From Container Name | To Container | Output |
---|---|---|---|---|
Correctly Formatted | Existing Blob Name | Existing Container Name | Existing Container Name | Success |
Incorrectly Formatted | Existing Blob Name | Existing Container Name | Existing Container Name | Error Message |
Correctly Formatted | Existing Blob Name | Not existing Container Name | Existing Container Name | Error Message |
Correctly Formatted | Not existing Blob Name | Existing Container Name | Existing Container Name | Error Message |
Common Errors
Server failed to authenticate the request
If the connection string is formatted improperly or the token used within the string has expired, the step will return the following error message. To correct this, confirm the accuracy of the Connection string, and evaluate the expiration dates of the SAS token used in the connection string.
Exception Message:
{
Error Message: "Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:
Time:2023-04-11T15:37:57.2796755Z
Status: 403 (Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.)
ErrorCode: AuthenticationFailed
Additional Information:
AuthenticationErrorDetail: Signature not valid in the specified time frame: Start [Tue, 11 Apr 2023 15:34:10 GMT] - Expiry [Tue, 11 Apr 2023 15:36:10 GMT] - Current [Tue, 11 Apr 2023 15:37:57 GMT]
Content:
<?xml version="1.0" encoding="utf-8"?><Error><Code>AuthenticationFailed</Code><Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
RequestId:
Time:
</Message><AuthenticationErrorDetail>Signature not valid in the specified time frame: Start [Tue, 11 Apr 2023 15:34:10 GMT] - Expiry [Tue, 11 Apr 2023 15:36:10 GMT] - Current [Tue, 11 Apr 2023 15:37:57 GMT]</AuthenticationErrorDetail></Error>
Headers:
Server: Microsoft-HTTPAPI/2.0
x-ms-request-id:
x-ms-error-code: AuthenticationFailed
Date: Tue, 11 Apr 2023 15:37:57 GMT
Content-Length: 544
Content-Type: application/xml
"
}
The specified container does not exist
If either container name does not exist in Azure Storage Blob, the step will return the following error message. To correct this, confirm the spelling of the container, and evaluate if the container is a part of the Azure Storage Account.
Exception Message:
{
Error Message: "The specified container does not exist.
RequestId:
Time:2023-04-11T17:30:45.7730128Z
Status: 404 (The specified container does not exist.)
ErrorCode: ContainerNotFound
Content:
<?xml version="1.0" encoding="utf-8"?><Error><Code>ContainerNotFound</Code><Message>The specified container does not exist.
RequestId:
Time:2023-04-11T17:30:45.7730128Z</Message></Error>
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id:
x-ms-client-request-id:
x-ms-version: 2021-10-04
x-ms-error-code: ContainerNotFound
Date: Tue, 11 Apr 2023 17:30:45 GMT
Content-Length: 225
Content-Type: application/xml
"
}
The specified blob does not exist
If the blob name does not exist in the container or directory specified, the step will return the following error message. To correct this, confirm the spelling of the blob, and evaluate if the blob is in the specified container of the Azure Storage Account.
Exception Message:
{
Error Message: "The specified blob does not exist.
RequestId:
Time:2023-04-11T17:48:25.5204570Z
Status: 404 (The specified blob does not exist.)
ErrorCode: CannotVerifyCopySource
Content:
<?xml version="1.0" encoding="utf-8"?><Error><Code>CannotVerifyCopySource</Code><Message>The specified blob does not exist.
RequestId:
Time:2023-04-11T17:48:25.5204570Z</Message></Error>
Headers:
Server: Windows-Azure-Blob/1.0,Microsoft-HTTPAPI/2.0
x-ms-request-id:
x-ms-client-request-id:
x-ms-version: 2021-10-04
x-ms-error-code: CannotVerifyCopySource
Date: Tue, 11 Apr 2023 17:48:24 GMT
Content-Length: 225
Content-Type: application/xml
"
}
Articles:
Azure Storage Module