Do you have any question about this error?
Message type: E = Error
Message class: CU - Variants / configuration messages
Message number: 390
Message text: Exported files for knowledge base & were not deleted
Exported files are saved to a temporary directory and saved to the PC
database from there. Then they are deleted for security and other
reasons.
This is a warning that the files have not been deleted. If you are
concerned about security, delete the files manually from directory
...\SAP\SCE\DB\TEMP.
Error message extract from SAP system. Copyright SAP SE.
CU390
- Exported files for knowledge base & were not deleted ?The SAP error message CU390 indicates that exported files for the knowledge base were not deleted. This can occur in the context of SAP Knowledge Management (KM) or when dealing with content management in SAP systems. Here’s a breakdown of the potential causes, solutions, and related information for this error:
Causes:
- File System Permissions: The user or the process attempting to delete the files may not have the necessary permissions to perform delete operations on the file system.
- File Locking: The files may be locked by another process or user, preventing deletion.
- Configuration Issues: There may be misconfigurations in the SAP system settings related to file handling or knowledge base management.
- System Errors: Temporary system errors or issues with the underlying database or file system can also lead to this error.
- Incomplete Export Process: If the export process did not complete successfully, it may leave behind files that are not deleted.
Solutions:
- Check Permissions: Ensure that the user or service account running the SAP processes has the necessary permissions to delete files in the relevant directories.
- Release Locks: Investigate if the files are locked by other processes. You may need to terminate those processes or wait until they release the locks.
- Review Configuration: Check the configuration settings in SAP related to the knowledge base and file management. Ensure that they are set up correctly.
- Manual Deletion: If the files are not being deleted automatically, you can manually delete them from the file system, but ensure that this does not affect any ongoing processes.
- Check Logs: Review the SAP application logs and system logs for any additional error messages or warnings that could provide more context about the failure.
- Restart Services: Sometimes, restarting the relevant SAP services or the entire system can resolve temporary issues.
- Consult SAP Notes: Look for any relevant SAP Notes or Knowledge Base Articles that address this specific error message. SAP frequently updates its documentation and may have specific patches or recommendations.
Related Information:
By following these steps, you should be able to identify the cause of the CU390 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
CU389
& could not be exported
What causes this issue? One of the files that was to be exported to your PC by the "Download" cannot be saved. Does the file already exist ...
CU388
Generation for SCREEN_DEP: dependency &1, &2, facet &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CU391
& could not be loaded to the database
What causes this issue? One of the files to be exported by the "Download" could not be loaded to the PC database. Is the database table loc...
CU392
User &1 could not create SCE database schema in data source &2
What causes this issue? Knowledge bases for the SCE are saved to their own database on a PC. This means that you need to set up the database first. I...
Click on this link to search all SAP messages.