嵌入式轻分析无法打开，提示错误码2102000

1.报错提示：

退出出错了！准备数据过程中出现错误

重新抽取显示错误日志错误日志

错误码：2102000

2.报错场景：

轻分析之前使用正常，突然间嵌入式分析不可用，提示如上 ，但是轻分析主题是可以打开的。

详细报错如下：

退出

出错了！准备数据过程中出现错误

重新抽取显示错误日志错误日志

错误码：2102000

kd.bos.mservice.qing.bill.preparedata.exception.FormAPICallPrepareDataException: kd.bos.mservice.qing.bill.exception.FormAPICallException: kd.bos.exception.KDException: Exception in invoke kd.bos.service.DispatchService(appId=), error is: 服务不可用, invoker列表为:[invoker :interface kd.bos.service.DispatchService -> zookeeper://192.168.22.132:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=mservice-qing&check=false&default.loadbalance=healthactive&default.reference.filter=activelimit&default.retries=0&default.timeout=580000&dispatcher=all&dubbo=2.8.4&generic=false&has.default.app.id=false&interface=kd.bos.service.DispatchService&methods=invoke&payload=52428800&pid=3745&revision=1.0&router=kd_debug_router&side=consumer&timestamp=1632001601876,directory: com.alibaba.dubbo.registry.integration.RegistryDirectory@46abbc1f]

at kd.bos.mservice.qing.bill.preparedata.handler.BillPrepareDataHandler.createDataSource(BillPrepareDataHandler.java:137)

at kd.bos.mservice.qing.bill.preparedata.handler.BillPrepareDataHandler.createDataSource(BillPrepareDataHandler.java:121)

at com.kingdee.bos.qing.preparedata.task.DataExtractTask.call(DataExtractTask.java:103)

at kd.bos.mservice.qing.preparedata.PrepareDataService.startExtractData(PrepareDataService.java:215)

at kd.bos.mservice.qing.preparedata.PrepareDataService.billStartExtractData(PrepareDataService.java:121)

at sun.reflect.GeneratedMethodAccessor346.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at com.kingdee.bos.qing.util.MethodInvokeUtil.reflectInvokeMethod(MethodInvokeUtil.java:51)

at com.kingdee.bos.qing.util.MethodInvokeUtil.invoke(MethodInvokeUtil.java:40)

at com.kingdee.bos.qing.common.framework.server.task.AsynServerRequestInvokeTask.call(AsynServerRequestInvokeTask.java:43)

at com.kingdee.bos.qing.common.framework.server.task.AsynServerRequestInvokeTask.call(AsynServerRequestInvokeTask.java:12)

at com.kingdee.bos.qing.util.QingContextCallable.call(QingContextCallable.java:25)

at kd.bos.thread.ThreadLifeCycleManager$CallableWrap.call(ThreadLifeCycleManager.java:180)

at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: kd.bos.mservice.qing.bill.exception.FormAPICallException: kd.bos.exception.KDException: Exception in invoke kd.bos.service.DispatchService(appId=), error is: 服务不可用, invoker列表为:[invoker :interface kd.bos.service.DispatchService -> zookeeper://192.168.22.132:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=mservice-qing&check=false&default.loadbalance=healthactive&default.reference.filter=activelimit&default.retries=0&default.timeout=580000&dispatcher=all&dubbo=2.8.4&generic=false&has.default.app.id=false&interface=kd.bos.service.DispatchService&methods=invoke&payload=52428800&pid=3745&revision=1.0&router=kd_debug_router&side=consumer&timestamp=1632001601876,directory: com.alibaba.dubbo.registry.integration.RegistryDirectory@46abbc1f]

at kd.bos.mservice.qing.bill.data.FormMserviceUtil.invokeBOSServiceByFormId(FormMserviceUtil.java:26)

at kd.bos.mservice.qing.bill.data.FormMserviceUtil.getAppId(FormMserviceUtil.java:51)

at kd.bos.mservice.qing.bill.preparedata.handler.BillPrepareDataHandler.createDataSource(BillPrepareDataHandler.java:131)

... 17 more

Caused by: kd.bos.exception.KDException: Exception in invoke kd.bos.service.DispatchService(appId=), error is: 服务不可用, invoker列表为:[invoker :interface kd.bos.service.DispatchService -> zookeeper://192.168.22.132:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=mservice-qing&check=false&default.loadbalance=healthactive&default.reference.filter=activelimit&default.retries=0&default.timeout=580000&dispatcher=all&dubbo=2.8.4&generic=false&has.default.app.id=false&interface=kd.bos.service.DispatchService&methods=invoke&payload=52428800&pid=3745&revision=1.0&router=kd_debug_router&side=consumer&timestamp=1632001601876,directory: com.alibaba.dubbo.registry.integration.RegistryDirectory@46abbc1f]

at kd.bos.mservice.rpc.dubbo.ProxyFactory$Handler.invoke(ProxyFactory.java:135)

at com.sun.proxy.$Proxy40.invoke(Unknown Source)

at sun.reflect.GeneratedMethodAccessor219.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at kd.bos.mservice.rpc.dubbo.debug.LocalDebugProxy$1.lambda$invoke$0(LocalDebugProxy.java:61)

at kd.bos.mservice.rpc.dubbo.debug.DubboDebugUtil.invoke(DubboDebugUtil.java:49)

at kd.bos.mservice.rpc.dubbo.debug.LocalDebugProxy$1.invoke(LocalDebugProxy.java:58)

at com.sun.proxy.$Proxy40.invoke(Unknown Source)

at kd.bos.servicehelper.DispatchServiceHelper.invokeBOSService(DispatchServiceHelper.java:96)

at kd.bos.mservice.qing.bill.data.FormMserviceUtil.invokeBOSServiceByFormId(FormMserviceUtil.java:22)

... 19 more

Caused by: com.alibaba.dubbo.rpc.RpcException: 服务不可用, invoker列表为:[invoker :interface kd.bos.service.DispatchService -> zookeeper://192.168.22.132:2181/com.alibaba.dubbo.registry.RegistryService?anyhost=true&application=mservice-qing&check=false&default.loadbalance=healthactive&default.reference.filter=activelimit&default.retries=0&default.timeout=580000&dispatcher=all&dubbo=2.8.4&generic=false&has.default.app.id=false&interface=kd.bos.service.DispatchService&methods=invoke&payload=52428800&pid=3745&revision=1.0&router=kd_debug_router&side=consumer&timestamp=1632001601876,directory: com.alibaba.dubbo.registry.integration.RegistryDirectory@46abbc1f]

at com.alibaba.dubbo.rpc.cluster.support.AvailableCluster$1.doInvoke(AvailableCluster.java:57)

at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:229)

at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72)

at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:55)

at com.alibaba.dubbo.common.bytecode.proxy0.invoke(proxy0.java)

at sun.reflect.GeneratedMethodAccessor219.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at kd.bos.mservice.rpc.dubbo.ProxyFactory$Handler.invoke(ProxyFactory.java:99)

... 29 more

检查项目：

重启mservice-qing

检查端口

检查组件zookeeper是否启动

检查更改setAPPenv.sh

最后唐老师检查发现谁更改了HOST文件。

总结：

对于之前正常使用的，一定详细咨询对应IT及相关人员是否有更改对应配置，因果因果，有果必有因。