Messages and limitations of the Azure BLOB Storage connector
Message code list of AZUREBLOB category
The following message codes correspond to errors that occur in Azure BLOB Storage Connector.
This message code is output when an undefined error occurs.
|
Cause |
Solution |
|---|---|
|
An undefined error occurred. |
Check the error message or the help of the operation in which the error has occurred. |
Corresponding error
-
None
This message code is output when connection to Microsoft Azure BLOB Storage fails.
|
Cause |
Solution |
|---|---|
|
Can't connect for the following reasons:
|
Check the settings for the connection resource and the status of connection. |
Corresponding error
-
com.microsoft.azure.storage.StorageException
This message code is output when the access key setting is incorrect.
|
Cause |
Solution |
|---|---|
|
Access key of the connection resource is incorrect. |
Check the connection resource settings. |
Corresponding error
-
java.security.InvalidKeyException
Exception messages of AZUREBLOB category
|
Exception name |
Cause |
Solution |
|---|---|---|
|
com.microsoft.azure.storage.StorageException |
Can't connect for the following reasons:
- Account or Access key of the connection resource specified in Destination is incorrect. - Double byte characters are included in Account of the connection resource specified in Destination. |
Check the settings for the connection resource specified in Destination and the status of connection. |
|
InvalidPropertyConfigurationException <Property name> is not specified. |
<Property name> isn't specified. |
Specify <property name>. |
|
InvalidPropertyConfigurationException Could not read the local directory. |
Can't read the directory specified in Local directory. |
Specify a readable directory path in Local directory. |
|
InvalidPropertyConfigurationException The local directory does not exist. |
The directory path specified in Local directory doesn't exist. |
Specify a directory path that exists in Local directory. |
|
InvalidPropertyConfigurationException Could not write to the local directory. |
Can't write to the directory specified in Local directory. |
Specify a writable directory path in Local directory. |
|
InvalidPropertyConfigurationException The path specified in local directory is not a directory. |
The path specified in Local directory isn't a directory. |
Specify a directory path in Local directory. |
|
java.security.InvalidKeyException Storage Key is not a valid base64 encoded string. |
Access key of the connection resource specified in Destination is incorrect. |
Check the settings for the connection resource specified in Destination. |
|
ResourceNotFoundException Resource definition could not be found. Name: [] |
Destination isn't specified. |
Specify Destination. |
|
ResourceNotFoundException Resource definition could not be found. Name: [<connection resource name>] |
The resource definition selected in Destination isn't found. |
Check the connection resource specified in Destination. |
Limitations of AZUREBLOB category
Notes
-
The behavior described in the help pages is subject to change depending on specification changes in the destination.
Notes
-
HTTPS is used in communication between Microsoft Azure BLOB Storage and this connector.
-
If an error other than an error that is unrelated to the connection (an error which isn't described in "Exception messages") occurs during execution, "Error" is set for the status attribute of the file element of the file or container in which the result data error occurred, the result data is output, and the subsequent processing continues.
-
When executing this operation in multiple threads, an error may occur (the status attribute of the file element of the target file will be "Error"). In that case, reduce the multiplicity of threads and execute it.
Specification limits
-
Files with the following names can't be downloaded. The status attribute of the file element will be "Error".
-
When any of restricted characters of HULFT Square Storage other than the path separator "/" is included.
-
When the file name ends with the path separator "/".
-
Notes
-
HTTPS is used in communication between Microsoft Azure BLOB Storage and this connector.
-
Naming conventions of container name in Microsoft Azure
-
Containers names must follow the following four rules:
-
A container name begins with alphanumeric characters. It can contain only alphabetic characters, numbers, and hyphens (-).
-
If including a hyphen (-), it must be between two alphanumeric characters.
-
Alphabetic characters must be lowercase.
-
The length of a container name must be from 3 through 63.
-
-
-
If an error other than an error that is unrelated to the connection (an error which isn't described in "Exception messages") occurs during execution, "Error" is set for the status attribute of the file element of the file or container in which the result data error occurred, the result data is output, and the subsequent processing continues.
-
When reading files of large volume in multiple threads, an error may occur (the status attribute of the file element of the target file will be "Error").
In that case, reduce the multiplicity of threads and execute it.
Specification limits
-
The type attribute of the file element of a written file will be "File".
Notes
-
HTTPS is used in communication between Microsoft Azure BLOB Storage and this connector.
-
Naming conventions of container name in Microsoft Azure
-
Containers names must follow the following four rules:
-
A container name begins with alphanumeric characters. It can contain only alphabetic characters, numbers, and hyphens (-).
-
If including a hyphen (-), it must be between two alphanumeric characters.
-
Alphabetic characters must be lowercase.
-
The length of a container name must be from 3 through 63.
-
-
-
If an error other than an error that is unrelated to the connection (an error which isn't described in "Exception messages") occurs during execution, "Error" is set for the status attribute of the file element of the file or container in which the result data error occurred, the result data is output, and the subsequent processing continues.
-
When writing files of large volume in multiple threads, an error may occur (the status attribute of the file element of the target file will be "Error"). In that case, reduce the multiplicity of threads and execute it.
-
Specifying an empty folder as a source of data to write can't create an empty folder on the BLOB storage.
Delete File/Directory/Container
Specification limits
None.
Notes
-
HTTPS is used in communication between Microsoft Azure BLOB Storage and this connector.
-
Naming conventions of container name in Microsoft Azure
-
Containers names must follow the following four rules:
-
A container name begins with alphanumeric characters. It can contain only alphabetic characters, numbers, and hyphens (-).
-
If including a hyphen (-), it must be between two alphanumeric characters.
-
Alphabetic characters must be lowercase.
-
The length of a container name must be from 3 through 63.
-
-
-
If an error other than an error that is unrelated to the connection (an error which isn't described in "Exception messages") occurs during execution, "Error" is set for the status attribute of the file element of the file or container in which the result data error occurred, the result data is output, and the subsequent processing continues.
-
When executing this operation in multiple threads, an error may occur (the status attribute of the file element of the target file will be "Error"). In that case, reduce the multiplicity of threads and execute it.