File not exist: C:\Users\liyiliang\Desktop\bacnetip-1.2.x\config.yml

文件不存在的错误通常是由于文件路径错误或文件确实不存在导致的。请确保文件路径正确，并检查文件是否存在。如果文件确实不存在，则需要创建该文件或使用正确的文件路径。

如果您正在使用Maven并遇到了“Error executing Maven. The specified user settings file does not exist”错误，请检查指定的用户设置文件路径是否正确。如果路径不正确，请更正路径或创建该文件。

如果您的Android应用程序在Android 10上获得了读写存储卡权限，并且您遇到了问题，请在AndroidManifest.xml的application标签下声明android:requestLegacyExternalStorage="true"。这将启用旧版的外部存储权限模型，以便您的应用程序可以继续访问共享存储空间。

相关问题

Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. 2023-05-15T22:28:42.434+08:00 ERROR 9660 --- [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPLICATION FAILED TO START *************************** Description: An attempt was made to call a method that does not exist. The attempt was made from the following location: org.springframework.boot.autoconfigure.security.servlet.SpringBootWebSecurityConfiguration$SecurityFilterChainConfiguration.defaultSecurityFilterChain(SpringBootWebSecurityConfiguration.java:56) The following method did not exist: 'org.springframework.security.config.annotation.web.configurers.AuthorizeHttpRequestsConfigurer$AuthorizationManagerRequestMatcherRegistry org.springframework.security.config.annotation.web.builders.HttpSecurity.authorizeHttpRequests()' The calling method's class, org.springframework.boot.autoconfigure.security.servlet.SpringBootWebSecurityConfiguration$SecurityFilterChainConfiguration, was loaded from the following location: jar:file:/C:/Users/86152/.m2/repository/org/springframework/boot/spring-boot-autoconfigure/3.0.6/spring-boot-autoconfigure-3.0.6.jar!/org/springframework/boot/autoconfigure/security/servlet/SpringBootWebSecurityConfiguration$SecurityFilterChainConfiguration.class The called method's class, org.springframework.security.config.annotation.web.builders.HttpSecurity, is available from the following locations: jar:file:/C:/Users/86152/.m2/repository/org/springframework/security/spring-security-config/5.5.0/spring-security-config-5.5.0.jar!/org/springframework/security/config/annotation/web/builders/HttpSecurity.class The called method's class hierarchy was loaded from the following locations: org.springframework.security.config.annotation.web.builders.HttpSecurity: file:/C:/Users/86152/.m2/repository/org/springframework/security/spring-security-config/5.5.0/spring-security-config-5.5.0.jar org.springframework.security.config.annotation.AbstractConfiguredSecurityBuilder: file:/C:/Users/86152/.m2/repository/org/springframework/security/spring-security-config/5.5.0/spring-security-config-5.5.0.jar org.springframework.security.config.annotation.AbstractSecurityBuilder: file:/C:/Users/86152/.m2/repository/org/springframework/security/spring-security-config/5.5.0/spring-security-config-5.5.0.jar

这个错误信息看起来是 Spring Boot 应用启动失败了，可能是因为在 Spring Security 的配置中调用了一个不存在的方法导致的。建议你重新运行应用并开启调试模式，查看详细的错误信息。同时，你也可以检查一下应用中的 Spring Security 配置，确认是否存在调用了不存在的方法的情况。

Description: An attempt was made to call a method that does not exist.The attempt was made from the following location: org.apache.dubbo.metadata.store.nacos.NacosConfigServiceWrapper.publishConfigCas(NacosConfigServiceWrapper.java:65) 家 The following method did not exist: 15:18:30 The method's class,com.alibaba.nacos.api.config.configservice,is available from the following Locations: 兆科技有限公司 as -0 Gar:file:/var/www/java/api-java-meeting2.0/ubains-meeting-inner-api-1.0-SNAPSHOT.jar!/BOOT-INE/lib/nacos-api-1.4.0.jar!/com/alibaba/nacos/api/config/Configservice.class The class hierarchy was loaded from the following locations: 2025 2023 深 com.alibaba.nacos .api.config.Configservice:jar:file:/var/www/java/api-java-meeting2.0/ubains-meeting-inner-api-1.0-SNAPSHOT.jar!/BOOT-INF/lib/nacos-api-1.4.0.jar!/ 怎么解决

这个问题看起来是 Dubbo 使用了错误的版本的 Alibaba Nacos Config，导致方法调用时出现了错误。

要解决这个问题，你可以尝试以下几种方法：

1. 检查应用程序的依赖，确保使用的是与 Dubbo 兼容的版本的 Alibaba Nacos Config。
2. 确保应用程序的 Classpath 中只存在一份 Alibaba Nacos Config 的 JAR 包，避免出现多个版本的 JAR 包导致冲突。
3. 如果使用的是 Maven 作为项目构建工具，可以尝试使用 Maven Dependency Plugin 等工具来排除重复依赖。
4. 如果仍然无法解决问题，可以尝试升级 Dubbo 或 Alibaba Nacos Config 的版本，或者联系 Dubbo 或 Alibaba Nacos 的技术支持寻求帮助。

总之，在解决问题时要确保使用的是与 Dubbo 兼容的版本的 Alibaba Nacos Config，并避免出现多个版本的 JAR 包导致冲突。