Hi, all!
Have a nice day to you!
This topic describes how to resolve the question that the CDE (LMT) client cannot be started after being installed on the windows server.
Description
In Windows Server series PC, sometimes the CDE client cannot be run after being installed which is caused by that the environment does not have necessary runtime library files.
Solution
The solutions are as follows based on three different symptoms:
A dialog box will be displayed indicating that the specified .dll file is missing when you start the CDE client
Methods: Find the specified .dll file in \uninstall\jre\jre_win\bin\ in the CDE client installation directory and copy the file to the \omu\workspace1\client\ directory. Then run the CDE again.
No response or prompt is displayed when you start the client
Methods: Copy all msvcp***.dll and msvcr***.dll files in the installation directory \uninstall\jre\jre_win\bin\ of the client to \omu\workspace1\client\ to solve the problem.
If the client still cannot be opened, copy the vcruntime***.dll file. Generally, the client can be opened normally. If an error is reported when you run the client installation package, try to run the installation package as the administrator. If the problem persists, try to install the client in another Windows 7 environment. Then compress all the installation directory, and then copy it to the target host.
Cause
Huawei JDK is compiled using Huawei's preferred visual studio 2017. The running of Huawei JDK depends on a series of dynamic link libraries such as Microsoft's vcruntime140.dll. These link libraries are released together with Huawei JDK and are located in the jre/bin directory. When java.exe is run independently (for example, in cmd), Java can be loaded to these dependent libraries. When java.exe is invoked from an external exe or bat, the jre/bin directory is not in the DLL search path of the current program. Therefore, the DLL in the jre/bin directory cannot be loaded. In a new Windows system or a Windows system that has vc++runtime redistributable 2015 or later installed, the DLLs are usually stored in the System32 directory. In this case, Java can still run properly. If the system32 directory does not contain dlls such as vcruntime140, the preceding problem occurs.
Thanks for reading!
