Revision history [back]

This could be due to a variety of reasons, such as:

1. The file may not exist at the specified location.
2. The file may be named differently or may not have the .cfg.xml extension.
3. The path may be incorrect or may be pointing to a different location in the file system.
4. The file may be present in a different project or module and is not accessible from the current project.

To fix the issue, you can try the following steps:

1. Check if the file exists in the specified location and has the correct name and extension.
2. Double-check the path in the configuration or code to ensure that it is pointing to the correct location.
3. If the file is present in a different project or module, try to include it in the current project or add the dependency to the build file.
4. If none of the above solutions work, try to provide an absolute path to the configuration file instead of a relative path.