Common Problems in Dedicated Software Porting Warehouse Management

Table 1 lists common problems in dedicated software porting warehouse management and handling suggestions.

**Table 1** Common problems in dedicated software porting warehouse management
Problem	Possible Causes	Handling Suggestions
Failed to package or copy the dedicated software porting warehouse.	The drive space is insufficient.	Check the size of the /opt directory.
No valid porting warehouse file exists in the directory of the dedicated software porting warehouse.	The dedicated software porting warehouse file does not exist.	Check whether the dedicated software porting warehouse file exists in the corresponding directory. Directory of the dedicated software porting warehouse: /opt/DevKit/devkitplugins/porting/resource/migration
The file for upgrading the dedicated software porting warehouse does not exist or is incorrect.	The file for upgrading the dedicated software porting warehouse does not exist or is incorrect.	Check whether the file for upgrading the dedicated software porting warehouse exists in the corresponding directory, and whether the file format and size are correct. Ensure that the correct upgrade package has been downloaded. Upgrade directory: /opt/DevKit/devkitplugins/porting/resource/migration
The resource package of the dedicated software porting warehouse is repeatedly uploaded.	The resource package of the dedicated software porting warehouse has been manually uploaded to the server.	Delete the existing resource package of the dedicated software porting warehouse from /opt/DevKit/devkitplugins/porting/resource/migration.
Failed to upload the resource package of the dedicated software porting warehouse.	The existing dedicated software porting warehouse is of the latest version.	No upgrade is required.

Parent topic: FAQs