@ptenggren wrote:
Hi,
After a new/fresh installation the VM Maestro client fails to start with the following error in the .log
My profile is located on a file server, can this cause the issue with the URI?!SESSION 2015-11-10 10:07:32.043 ----------------------------------------------- eclipse.buildId=unknown java.version=1.7.0_67 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Command-line arguments: -os win32 -ws win32 -arch x86 -clean !ENTRY org.eclipse.osgi 4 0 2015-11-10 10:07:42.355 !MESSAGE Application error !STACK 1 java.lang.IllegalArgumentException: URI has an authority component at java.io.File.<init>(Unknown Source) at com.cisco.vmmaestro.Application.start(Application.java:37) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) at org.eclipse.equinox.launcher.Main.run(Main.java:1465) !ENTRY org.eclipse.core.jobs 2 2 2015-11-10 10:07:43.614 !MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: com.cisco.cats.cesmonitor.CheckInternalModeJob
Posts: 5
Participants: 2