Log In
Register
Topic RSS
9:42, EET
December 20, 2025
Offline
My application shows an error during startup. I tried uninstalling and reinstalling it, but it still doesn’t work. I checked the log content from the official manual as follows (excerpt of the error part).
12/20/2025 15:22:23.403 ERROR [SimulationServer] com.prosysopc.ua.app.simserver.i [] – Could not start the application.
java.lang.IllegalStateException: Expected the service c [FAILED] to be RUNNING, but the service has FAILED
at com.google.common.util.concurrent.AbstractService.checkCurrentState(AbstractService.java:387) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.AbstractService.awaitRunning(AbstractService.java:307) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.AbstractIdleService.awaitRunning(AbstractIdleService.java:169) ~[guava-33.4.7-jre.jar:?]
at com.prosysopc.ua.app.simserver.i.b(SourceFile:136) [app-5.5.4-384.jar:5.5.4-384]
at com.prosysopc.ua.app.simserver.SimulationServer.main(SourceFile:55) [app-5.5.4-384.jar:5.5.4-384]
at com.prosysopc.ua.app.Main.main(Main.java:13) [prosys-opc-ua-simulation-server-5.5.4-384.jar:5.5.4-384]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.base/java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
at com.exe4j.runtime.LauncherEngine.launch(LauncherEngine.java:84) [i4jruntime.jar:?]
at com.exe4j.runtime.WinLauncher.main(WinLauncher.java:94) [i4jruntime.jar:?]
at com.install4j.runtime.launcher.WinLauncher.main(WinLauncher.java:25) [i4jruntime.jar:?]
Caused by: java.lang.IllegalStateException: Expected to be healthy after starting. The following services are not running: {STARTING=[PubSubSettingsService [STARTING]], FAILED=[NamespaceService [FAILED]]}
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.checkHealthy(ServiceManager.java:764) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.ServiceManager$ServiceManagerState.awaitHealthy(ServiceManager.java:585) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.ServiceManager.awaitHealthy(ServiceManager.java:299) ~[guava-33.4.7-jre.jar:?]
at com.prosysopc.ua.app.simserver.services.c.startUp(SourceFile:97) ~[app-5.5.4-384.jar:5.5.4-384]
at com.google.common.util.concurrent.AbstractIdleService$DelegateService.lambda$doStart$0(AbstractIdleService.java:63) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.Callables.lambda$threadRenaming$1(Callables.java:104) ~[guava-33.4.7-jre.jar:?]
at java.base/java.lang.Thread.run(Thread.java:833) ~[?:?]
Suppressed: com.google.common.util.concurrent.ServiceManager$FailedService: NamespaceService [FAILED]
Caused by: java.lang.NullPointerException: Cannot invoke “com.prosysopc.ua.app.simserver.server.namespaces.Namespace.d(com.prosysopc.ua.UaNodeSet$a)” because the return value of “com.prosysopc.ua.app.simserver.server.namespaces.NamespaceService.be(String)” is null
at com.prosysopc.ua.app.simserver.server.namespaces.NamespaceService.iR(SourceFile:562) ~[app-5.5.4-384.jar:5.5.4-384]
at com.prosysopc.ua.app.simserver.server.namespaces.NamespaceService.iQ(SourceFile:548) ~[app-5.5.4-384.jar:5.5.4-384]
at com.prosysopc.ua.app.simserver.server.namespaces.NamespaceService.startUp(SourceFile:281) ~[app-5.5.4-384.jar:5.5.4-384]
at com.google.common.util.concurrent.AbstractIdleService$DelegateService.lambda$doStart$0(AbstractIdleService.java:63) ~[guava-33.4.7-jre.jar:?]
at com.google.common.util.concurrent.Callables.lambda$threadRenaming$1(Callables.java:104) ~[guava-33.4.7-jre.jar:?]
at java.base/java.lang.Thread.run(Thread.java:833) ~[?:?]
How should I get back to normal use?
11:29, EET
Moderators
February 11, 2020
Offline
Hello,
It seems like something has corrupted your Simulation Server configuration to the point where opening the application won’t work. Unfortunately there is nothing else that can be done except deleting the existing configuration located in [userhome]\.prosysopc\prosys-opc-ua-simulation-server where [userhome] is your userhome, which on Windows is C:\Users\[username] where [username] is your username. You should be able to keep log, PKI and USERS_PKI folders and license.lic and log4j2.xml files but everything else should be deleted to start using Simulation Server with a new configuration.
Also, you’re using an older version of Simulation Server. The newest version adds project management, which enables saving the Simulation Server configuration to file and loading configurations from files. We would recommend updating to the newest version as project management would enable creating back ups of the configuration that you could load if the configuration somehow becomes corrupted.
1 Guest(s)
