Help Center/ Object Storage Migration Service/ FAQs/ Error Codes and Solutions/ TRF.0024 & TRF.0025 & TRF.0026 & TRF.0028 & TRF.0029 & TRF.0030 Failed to obtain the metadata of the specified file or folder.
Updated on 2026-07-06 GMT+08:00
TRF.0024 & TRF.0025 & TRF.0026 & TRF.0028 & TRF.0029 & TRF.0030 Failed to obtain the metadata of the specified file or folder.
Symptom
The system fails to obtain the metadata of the specified file or folder, and returns the following error codes:
- TRF.0024 and TRF.0028: The migration task is bucket migration.
- TRF.0025 and TRF.0029: The migration task is prefix migration.
- TRF.0026 and TRF.0030: The migration task is list migration.
Possible Causes
- The specified file or folder does not exist in the destination storage.
- The source storage account does not have the permission for listing destination objects.
- The file or folder path is misspelled or does not meet the format requirements.
- The storage service is temporarily abnormal or the network is disconnected.
Solution
- Check whether the file or folder path is correct, including the case and special characters.
- If the path is incorrect, correct the path based on the actual storage structure.
- If the file or folder does not exist, confirm the target path, then upload or create the corresponding object again.
- Log in to the source storage account and check whether the permission policy of the account contains the list or read permission.
- If the permission is insufficient, grant the list objects permission to the source storage account.
- Check the network connection status to ensure that there is no network disconnection or high latency. Alternatively, check the system logs or monitoring alarms to determine whether the server is temporarily abnormal.
- If the network or service is temporarily abnormal, try again later or contact technical support to check the service status.
Parent topic: Error Codes and Solutions
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot