If an error occurs when you call an Apsara File Storage NAS API operation, an error code is returned.
Components of an error code
The following table describes the components of an error code.
Component | Description |
---|---|
HttpCode | The HTTP status code that complies with the HTTP syntax. |
Code | The error ID. |
Message | The error message. |
Advice | The recommended solution. |
Error codes
HttpCode | Code | Message | Advice |
---|---|---|---|
500 | InternalError | The request processing has failed due to some unknown error. | Try again later. If the issue persists after you try again, contact NAS technical support. |
503 | ServiceUnavailable | The request has failed due to a temporary failure of the server. | The request failed due to an unexpected error. Try again later. |
504 | ServiceTimeout | The request processing has failed due to timeout. | Try again later. |
503 | SecurityToken.CheckFailed | The security token check has failed due to some internal error. | The system failed to authenticate the Security Token Service (STS) token due to the failure of an internal call. Try again later. |
503 | SecurityToken.DecodeFailed | The security token decode has failed due to some internal error. | The system failed to decode the STS token due to the failure of an internal call. Try again later. |
503 | SubRam.CheckFailed | The sub user ram check has failed due to some internal error. | The system failed to authenticate the Alibaba Cloud account or the RAM user due to the failure of an internal call. Try again later. |
503 | VpcRam.CheckFailed | The Vpc ram check has failed due to some internal error. | The system failed to authenticate the client that attempts to access the file system over the virtual private cloud (VPC) due to the failure of an internal call. Try again later. |
503 | VpcSubRam.CheckFailed | The Vpc sub user ram check has failed due to some internal error. | The system failed to authenticate the Alibaba Cloud account and the RAM user due to the failure of an internal call. Try again later. |
400 | MissingParameter.callerUid | Parameter `callerUid` is mandatory for this action. | Specify a valid value for the callerUid parameter. |
400 | MissingParameter.RegionId | Parameter `RegionId` in endpoint is mandatory for this action. | Specify a valid endpoint for the RegionId parameter. |
400 | MissingParameter.VSwitchId | Parameter `VSwitchId` is mandatory for this action. | Specify a valid value for the VSwitchId parameter. |
400 | MissingParameter.VpcId | Parameter `VpcId` is mandatory for this action. | Specify a valid value for the VpcId parameter. |
400 | InvalidParameter.StorageType | Parameter `StorageType` is mandatory for this action. | The valid values of the StorageType parameter are Performance and Capacity. |
400 | InvalidParameter.ProtocalType | Parameter ProtocalType is mandatory for this action. | The valid values of the ProtocalType parameter are NFS and SMB. |
400 | InvalidParameter.Description | Parameter Description is mandatory for this action. | The value of the Description parameter can contain letters and the following special characters: at signs (@), number signs (#), dollar signs ($), underscores (_), plus signs (+), and hyphens (-). |
404 | InvalidFileSystem.NotFound | The specified FileSystem does not exist. | The specified file system does not exist or is deleted. |
403 | InvalidFileSystem.AlreadyExisted | The specified FileSystem has been already existed. | The specified file system already exists. You can call the DescribeFileSystems operation to query the information about the file system. |
404 | InvalidMountTarget.NotFound | The specified MountTarget does not exist. | The specified mount target does not exist or is deleted. |
404 | InvalidAccessGroup.NotFound | The specified AccessGroup does not exist. | The specified permission group does not exist or is deleted. |
403 | InvalidAccessGroup.AlreadyExisted | The specified AccessGroup has been already existed. | The specified permission group already exists. You can call the DescribeMountTargets operation to query the information about the permission group. |
403 | InvalidAccessGroup.AlreadyAttached | The specified AccessGroup is still attached by some MountTarget(s). | One or more mount targets are attached to the specified permission group. Before you delete the permission group, you must detach the mount targets. |
404 | InvalidAccessRule.NotFound | The specified AccessRule does not exist. | The specified rule does not exist or is deleted. |
404 | InvalidLocatin.NotFound | The specified Location is not found or is not supported. | The specified location does not exist or is unavailable. |
404 | InvalidRegionId.NotFound | The specified Region is not found. | The specified region does not exist or is unavailable. |
404 | InvalidAZone.NotFound | The specified AZone is not found. | The specified zone does not exist or is unavailable. |
404 | InvalidVpc.NotFound | The specified Vpc is not found. | The specified VPC does not exist. Create a VPC. |
404 | InvalidVip.NotFound | The specified Vip is not found. | The specified VPC cannot be found. Check whether the information about the VPC is valid. |
404 | InvalidLBid.NotFound | The specified LBid is not found. | The system failed to create the LBid. Try again later. |
404 | InvalidVpcTunnelId.NotFound | The specified vpc tunnelId is not found. | The tunnel ID of the specified VPC does not exist. Check whether the information about the VPC is valid. |
404 | InvalidVpc.CreationFailed | The specified vpc instance creation failed. | The system failed to create the specified VPC. Check whether the information about the VPC is valid and whether available IP addresses exist. Try again later. |
403 | OperationDenied.DefaultAccessGroupCannotDelete | The default AccessGroup can not be deleted. | You can modify a custom permission group. |
403 | OperationDenied.DefaultAccessGroupCannotModify | The default AccessGroup can not be modified. | You can modify a custom permission group. |
403 | OperationDenied.NetworkTypeNotMatched | The NetworkType of MountTarget is not matched with AccessGroup. | Make sure that the value of the NetworkType parameter for the mount target is the same as the value of the AccessGroupType parameter for the permission group. |
403 | OperationDenied.MountTargetNotEmpty | There are still MountTarget(s) on the specified FileSystem. | One or more mount targets are created for the specified file system. Before you delete the file system, you must delete the mount targets. |
403 | OperationDenied.FileSystemCountsExceeded | The amount of FileSystem has reached its limits(maximum 10). | To increase the upper limit, contact NAS technical support. |
403 | OperationDenied.MountTargetCountsExceeded | The amount of MountTarget has reached its limits(maximum 2 per FileSystem). | To increase the upper limit, contact NAS technical support. |
403 | OperationDenied.AccessGroupCountsExceeded | The amount of AccessGroup has reached its limits. | To increase the upper limit, contact NAS technical support. |
403 | OperationDenied.AccessRuleCountsExceeded | The amount of AccessRule has reached its limits. | To increase the upper limit, contact NAS technical support. |
403 | User.Disabled | Your account does not open Nas Service yet or balance is insufficient. | If NAS is not activated, activate NAS. |
403 | Forbidden.InvalidUserType | The operation is not permitted due to type of account. | The NAS API operation does not support your account type. |
403 | Forbidden.Ram | User not authorized to operate on the specified resource, or this API doesn't support RAM. | The system failed to authenticate the RAM user. Go to the Resource Access Management (RAM) console and grant the RAM user the permissions to access NAS resources. |
403 | Forbidden.EcsTokenNotAuthorized | User not authorized to check ecs on creating MountTarget of classic network type. | Go to the RAM console and grant NAS the permissions to call the verification API operations of Elastic Compute Service (ECS). |
403 | NotQualified | User has not been approved for the trail application. | We recommend that you apply for a free trial of the new features. If your application is pending approval for a long period of time, contact NAS technical support. |
Sample responses
XML format
<?xml version="1.0" encoding="UTF-8"?> <Error> <RequestId>B71B4C68-6C6B-4D4B-AD70-8951BD7D188E</RequestId> <HostId>nas.cn-hangzhou.aliyuncs.com</HostId> <Code>InvalidFileSystem.NotFound</Code> <Message>The specified file system does not exist.</Message> </Error>
JSON format
{ "RequestId": "B71B4C68-6C6B-4D4B-AD70-8951BD7D188E", "HostId": " nas.cn-hangzhou.aliyuncs.com ", "Code": "InvalidFileSystem.NotFound", "Message": "The specified file system does not exist." }