Failed to Launch JVM

[Rob Meade]

Hi all,

So, I wanted to get access to a recent XRay... the hospital sent me some convoluted Powerpoint, embedded in a separate email attachment to their main email... a few days later I get an email from IEP to download some software to view the XRay...

This began my journey to here... they appear to have bundled up Weasis in the Zip file... however, when running the Weasis-Windows.exe - it fails.  It briefly shows some command prompt window and then that disappears.

In my searching I found the Weasis website, downloaded the main product... that fails to launch... downloaded the Weasis Dicomm viewer, that also fails to load with the above error message.

Needless to say I am somewhat at my wits end... what was a simple request "Can you send me my Xray digitally please" has turned into an entire ball-ache of a process, and I'm still no closer, and have a lot of downloads/software that I never wanted on my laptop, none of which appears to be working.

Does anyone have any ideas?  My hope was that if the Dicomm viewer ran, I might be able to view the xrays and then just take a f*cking screenshot, because that would just be about a million times more straight forward.

Thanks in advance.

Kind regards,

Rob

[Rob Meade]

Anyone? :o/

[Nicolas Roduit]

I can't answer why the viewer doesn't launch on the CD because according to the name of the binary it's a packaging that was made by a company I know nothing about.

I advise you to download on the official website the version of Weasis according to your system:

1. Install it
2. Launch Weasis from the system menu
3. Click on the button to import a CD/DVD (the second button in the toolbar). See also how to import data

[Rob Meade]

Hi Nicholas,

Thank you for taking the time to reply - appreciated.

It was actually the official site that lead me to this group.  As mentioned in my OP, I downloaded the Weasis Dicomm Viewer from the official site, and that was what finally gave me an error message that I could read, which was the "Failed to Launch JVM" etc.

I don't have a CD, the hospital seems to use this other company (IEP), which you then log in to an download a file, it contains (I assume) the images of my xrays, an the weasis software, all bundled up.  I suspect the reason that faile to run may have been the same, but there's nothing in the Windows event log (in either case) to provide further information.

I'm assuming JVM is Java Virtual Machine, is this something that would typically be installed as necessary when installing Weasis, or, is it something that would be expected to be sourced/installe separately?

Thanks again for the reply and any further support.

Kind regards,

Rob

[Nicolas Roduit]

If you have installed Weasis using the MSI installer then there is no need to install Java or any other software.

This is the first time this error has been reported. Can you tell me what is the version of your system? And are there any errors in the boot.log file when launching (see this page)? 

[Rob Meade]

Hi Nicholas,

Thanks again for the support.

I believe it was the MSI Installer I used, I followed the links through from the main website to get to, specificially, the Weasis Viewer.

I'm running Windows 10 (21H2) / 19044.1741, experience pack 120.2212.4180.0) on my laptop. 64bit.

These are what I see when I launch (a reboot was done before launching btw, just in case)



when I click that one away, I see this...



Everything from the log file from this morning appears to be stamped with *INFO*, I'm assuming it would say *ERROR* etc if it was anything more series...

Below the line is the log from today, that said, there are a couple of other file versions in there too, but that might have been generated from the packaged version that I had run previously?  That one contains this line;

27.05.2022 10:45:49.686 *SEVERE* [main] org.weasis.launcher.WeasisLauncher: Cannot read properties file: file:///C:/Users/baldy/Desktop/RA772165041/weasis-i18n/buildNumber.properties
java.io.FileNotFoundException: C:\Users\baldy\Desktop\RA772165041\weasis-i18n\buildNumber.properties (The system cannot find the path specified)

which is why I think it was the previous packaged version, as the one I downloaded from your website "installed" etc.. that line above appears multiple times in that version of the log, but based on the time stamps, is probably just from where I kept trying to re-run it.

Your installed version doesn't appear to have the *SEVERE* error messages (see below).

Thanks again for any further help you can provide.

Kind regards,

Rob


------------------------------------------------------------------------------------------------------------------
30.05.2022 16:09:23.338 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
30.05.2022 16:09:23.393 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
30.05.2022 16:09:23.431 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=4.0.0-RC, weasis.config.hash=-1743951967, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=64D59807, weasis.profile=default, http.agent=Weasis/4.0.0-RC (Windows 10; 10.0; amd64; default; NATIVE)}
30.05.2022 16:09:23.448 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 59,096
30.05.2022 16:09:23.481 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
30.05.2022 16:09:23.481 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
30.05.2022 16:09:23.481 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
30.05.2022 16:09:23.482 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
30.05.2022 16:09:23.482 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
30.05.2022 16:09:23.482 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
30.05.2022 16:09:23.482 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
30.05.2022 16:09:23.482 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}
30.05.2022 17:41:57.209 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
30.05.2022 17:41:57.255 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
30.05.2022 17:41:57.285 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=4.0.0-RC, weasis.config.hash=-1743951967, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\WindowsApps\4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6\VFS\ProgramFilesX64\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app/conf/config.properties, weasis.source.id=53129AC2, weasis.profile=default, http.agent=Weasis/4.0.0-RC (Windows 10; 10.0; amd64; default; NATIVE)}
30.05.2022 17:41:57.303 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 65,242
30.05.2022 17:41:57.335 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
30.05.2022 17:41:57.336 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
30.05.2022 17:41:57.337 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}
07.06.2022 09:11:47.216 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 09:11:47.304 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 09:11:47.360 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=4.0.0-RC, weasis.config.hash=-1743951967, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\WindowsApps\4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6\VFS\ProgramFilesX64\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/WindowsApps/4871NicolasRoduit.Weasis_4.0.0.0_x64__awnrdhvhtfgg6/VFS/ProgramFilesX64/Weasis/app/conf/config.properties, weasis.source.id=53129AC2, weasis.profile=default, http.agent=Weasis/4.0.0-RC (Windows 10; 10.0; amd64; default; NATIVE)}
07.06.2022 09:11:47.388 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 62,918
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 09:11:47.428 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}

[Nicolas Roduit]

According to the paths,  it seems that there are several types of installation, the one from the Windows store and the one from the MSI installer.

I suggest you to uninstall all the versions and reinstall the one from the MSI file.

[Rob Meade]

Hi Nicholas,

Yeah, I tried to see if it was available via Windows Store also, I can't remember if that was in between, or after the MSI didn't seem to work for me.  I thought that if it was on the store it would include any components that I may need etc... I will do as you suggest and uninstall.

The "packaged" version is just sitting in a folder... it didn't seem to install, although it fires a command prompt when run and, the first time, it seemed to suggest it was going to execute a shell command, but I didn't get to see what... it appears/disappears too quickly now to see anything at all. I'll only be able to uninstall the MSI and Windows App versions, and then, as you suggest, I'll do the MSI install again and report back.

Thanks again.

Rob

--
You received this message because you are subscribed to a topic in the Google Groups "dcm4che" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dcm4che/Ca7OlSE38LE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/22a9ba83-daa3-407b-9d7d-5188d55a18b1n%40googlegroups.com.

[Rob Meade]

Hi Nicholas,

So I uninstalled the MSI and Windows App versions - rebooted for good measure.

Downloaded and installed the MSI (previously linked in your replies etc).

The logo image appears, then the "Failed to launch JVM" message again. Ok'ing that gives the same "Child process exited with code 1" error.  I dont really know the difference between Weasis and Dicomizer but I've tried launching both, and they both end with the same error/problem.

I don't know whether its relevant or not, but I took a look at the Windows Event Log, under the "Administrative Events", there's quite a few warnings for "DistributedCOM", but only one that is in the time frame of trying to launch the fresh install.. but there isn't really anything in that that means anything at all to me.  Looking at the "Application" log (in windows event viewer) there's two entries for the MSI installation, then an entry for VSS, then two "Security-SPP" entries, but these are all just "info" as opposed to warnings/errors from what I can see.  These appears to be the only entries in the same time frame as running it, but I dont know if they are relevant.

Example Administrative Log entry

Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          07/06/2022 11:10:07
Event ID:      10016
Task Category: None
Level:         Warning
Keywords:      Classic
User:          GAMMA\baldy
Computer:      Gamma
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user GAMMA\baldy SID (S-1-5-21-2883409882-2712135542-2883000671-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10016</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2022-06-07T10:10:07.2179254Z" />
    <EventRecordID>113664</EventRecordID>
    <Correlation ActivityID="{9da7f344-d0f7-4944-8bbf-aba4c6283a9e}" />
    <Execution ProcessID="1136" ThreadID="5592" />
    <Channel>System</Channel>
    <Computer>Gamma</Computer>
    <Security UserID="S-1-5-21-2883409882-2712135542-2883000671-1001" />
  </System>
  <EventData>
    <Data Name="param1">application-specific</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}</Data>
    <Data Name="param5">{15C20B67-12E7-4BB6-92BB-7AFF07997402}</Data>
    <Data Name="param6">GAMMA</Data>
    <Data Name="param7">baldy</Data>
    <Data Name="param8">S-1-5-21-2883409882-2712135542-2883000671-1001</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
    <Data Name="param10">Unavailable</Data>
    <Data Name="param11">Unavailable</Data>
  </EventData>
</Event>


These are the entries from the log (just the ones from the time I started from the fresh install etc);

07.06.2022 11:09:25.507 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 11:09:25.550 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 11:09:25.583 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=4.0.0-RC, weasis.config.hash=-1743951967, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=64D59807, weasis.profile=default, http.agent=Weasis/4.0.0-RC (Windows 10; 10.0; amd64; default; NATIVE)}
07.06.2022 11:09:25.597 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 54,493
07.06.2022 11:09:25.623 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 11:09:25.623 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 11:09:25.623 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 11:09:25.623 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 11:09:25.623 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 11:09:25.624 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 11:09:25.624 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 11:09:25.624 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}
07.06.2022 11:11:43.343 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 11:11:43.383 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 11:11:43.410 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis Dicomizer, weasis.version=4.0.0-RC, weasis.config.hash=388904634, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:conf/ext-dicomizer.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=9E1396C0, weasis.profile=dicomizer, http.agent=Weasis Dicomizer/4.0.0-RC (Windows 10; 10.0; amd64; dicomizer; NATIVE)}
07.06.2022 11:11:43.425 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 54,704
07.06.2022 11:11:43.451 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 11:11:43.451 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 11:11:43.451 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 11:11:43.451 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 11:11:43.452 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 11:11:43.452 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 11:11:43.452 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 11:11:43.452 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}

[Nicolas Roduit]

Sorry for the inconvenience but the problem could be related to the new graphic framework in version 4.

Could you try?

1. Launch the viewer with a parameter to not insert the menus in the window bar. Open Command Prompt, copy start weasis://%24weasis%3Aconfig%20pro%3D%22flatlaf.useWindowDecorations%20false%22 and enter return.

2. Or uninstall Weasis and install version 3.8.1

[Rob Meade]

Hi Nicholas,

Its ok, its no inconvenience, I appreciate your help.  I know if I tried contacting the hospital regarding this they'd have absolutely no clue at all.  I'm hoping with each little test/check/install we are getting closer to it working etc :)

I've tried the command prompt approach and that resulted in the same error message popups.  I will uninstall and reinstall 3.8.1 now and report back.

Thanks again,

Rob

You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/8fe1c05d-9369-415c-8060-28422912e6d5n%40googlegroups.com.

[Rob Meade]

So, I uninstalled version 4, rebooted, and installed the 3.8.1 MSI etc... 

Same issue/messages I'm afraid.  I dont think there's anything "new" in the logs either, but I've added the new entries below.

Being that it's constantly the JVM thing which is getting mentioned, is there any test I can do to check that the JVM is actually ok, kinda, aside from your product? 

This is my own development laptop, I have various software installed, Visual Studio and the like.  I don't expect any of that is causing the problem, as I suspect everything this product needs to run is kinda included, but thought I'd best mention it in case.

I'm happy to run any other tests you can think of.

Kind regards,

Rob



07.06.2022 12:06:33.997 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 12:06:34.036 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 12:06:34.037 *INFO* [main] org.weasis.launcher.ConfigData: Main arg 0 = weasis://%24weasis%3Aconfig%20pro%3D%22flatlaf.useWindowDecorations%20false%22/
07.06.2022 12:06:34.067 *INFO* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=4.0.0-RC, weasis.config.hash=-1743951967, flatlaf.useWindowDecorations=false, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=64D59807, weasis.profile=default, http.agent=Weasis/4.0.0-RC (Windows 10; 10.0; amd64; default; NATIVE)}
07.06.2022 12:06:34.082 *INFO* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 49,348
07.06.2022 12:06:34.108 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 12:06:34.109 *INFO* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}
07.06.2022 12:11:54.463 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 12:11:54.500 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 12:11:54.515 *CONFIG* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis, weasis.version=3.8.1, weasis.config.hash=1490119093, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:/C:/Program%20Files/Weasis/app/conf/ext-config.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=64D59807, weasis.profile=default, http.agent=Weasis/3.8.1 (Windows 10; 10.0; amd64; default; NATIVE)}
07.06.2022 12:11:54.535 *CONFIG* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 57,818
07.06.2022 12:11:54.558 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 12:11:54.558 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 12:11:54.558 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 12:11:54.558 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 12:11:54.559 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 12:11:54.559 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 12:11:54.559 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 12:11:54.559 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}
07.06.2022 12:12:11.130 *INFO* [main] org.weasis.launcher.ConfigData: Starting Weasis...
07.06.2022 12:12:11.167 *INFO* [main] org.weasis.launcher.ConfigData: Initialization of the launch configuration...
07.06.2022 12:12:11.185 *CONFIG* [main] org.weasis.launcher.ConfigData: Properties: {weasis.export.dicom.send=true, weasis.user=baldy, weasis.name=Weasis Dicomizer, weasis.version=3.8.1, weasis.config.hash=-2077759917, weasis.path=C:\Users\baldy\.weasis, weasis.launch.type=NATIVE, weasis.import.dicom=true, weasis.codebase.url=file:/C:/Program%20Files/Weasis/app, weasis.pref.local.session=true, weasis.codebase.local=C:\Program Files\Weasis\app, weasis.export.dicom=true, weasis.import.dicom.qr=true, felix.extended.config.properties=file:conf/ext-dicomizer.properties, felix.config.properties=file:/C:/Program%20Files/Weasis/app/conf/config.properties, weasis.source.id=9E1396C0, weasis.profile=dicomizer, http.agent=Weasis Dicomizer/3.8.1 (Windows 10; 10.0; amd64; dicomizer; NATIVE)}
07.06.2022 12:12:11.205 *CONFIG* [main] org.weasis.launcher.Singleton: Local port of the Singleton server: 57,903
07.06.2022 12:12:11.228 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of locale.lang.code = en
07.06.2022 12:12:11.228 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of locale.format.code = system
07.06.2022 12:12:11.228 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.level = INFO
07.06.2022 12:12:11.228 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.activate = false
07.06.2022 12:12:11.229 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.number = 5
07.06.2022 12:12:11.229 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.file.size = 10MB
07.06.2022 12:12:11.229 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.stack.limit = 3
07.06.2022 12:12:11.229 *CONFIG* [main] org.weasis.launcher.WeasisLauncher: Config of org.apache.sling.commons.log.pattern = {0,date,dd.MM.yyyy HH:mm:ss.SSS} *{4}* [{2}] {3}: {5}

On Tue, 7 Jun 2022 at 12:02, Nicolas Roduit <nicolas...@gmail.com> wrote:

You received this message because you are subscribed to the Google Groups "dcm4che" group.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/8fe1c05d-9369-415c-8060-28422912e6d5n%40googlegroups.com.

[Nicolas Roduit]

Well, I think there is something that must be interfering. Are there any Java versions installed and any system environment variables related to Java, in PATH? 

[Rob Meade]

Hi Nicholas,

I'm not entirely sure, its not a framework/software I use (knowingly).  After responding yesterday I did a quick Google search to see how you can check whether Java is correctly installed etc... there were a couple of articles that suggested;

java -version 
and 
jview

from the command prompt - I tried both and got "unrecognised" as a response in the command prompt, so I'm guessing its not installed.  Does it need to be to support Weasis, or, does Weasis come with a distribution of whatever it needs Java wise to run etc?

One thing I can try, which I didn't think of yesterday, is downloading/running on my son's laptop.  For me, this is just a one-time use-case, e.g. I just want to view my xrays, if there's no "export" option for a normalised file format I'll just screen grab, and then thats it, I'm done etc.

I'll try Weasis on my son's laptop shortly and respond back, that might at least narrow it down to my own laptop - of course - it would still be nice to know why it isn't working.

Kind regards,

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/f8b7a96e-6337-4c90-8430-9c57dac1eb84n%40googlegroups.com.

[Rob Meade]

Hi Nicholas,

Just an update.

I downloaded the MSI version (version 4) from the Weasis website and installed it on my son's laptop.  Launching it, there was a little initial delay (perhaps usual as things get configured) but then it opened without issue.

I was then able to point it to the folder location on my USB hard drive which I'd plugged in which contained the DICOMM directory sent to me by the hospital (with the packaged version).  Each image opened perfectly and I was really pleased to find the Export option which enabled me to get all of my xrays out of the original format and into something I can use personally.

Thank you so much for all of your help / support, I would never have received this from the hospital themselves, so it really is very much appreciated.

It obviously still leaves the question as to why it won't run on my own laptop, and, if there is any benefit to yourself in still doing a little more digging to try and find out (perhaps it will help someone else in the future etc) I'm very happy to work with you to ascertain what it may be.  I do however appreciate you are busy, and, as I now have what I wanted, you may feel that that is enough, which is absolutely fine also.  Just let me know.  If there are any other tests or anything else I can do which may help, I am happy to.

Kind regards,

Rob

[Nicolas Roduit]

Glad you can finally get to launch Weasis.

While searching, I guess I found the cause of the problem, it's the activation of a java parameter (which is normally disabled by default). You have to uncheck "Enable Java Access Bridge".

[Rob Meade]

Hi Nicholas,

Thanks for the follow up.  I've just checked, and I don't even have that as an option.  Being that its under "Other programs installed", is there something else I'd have needed to install?  I still have Weasis installed on my laptop, so presumably it wasn't that which adds the option.

Kind regards,

Rob

To view this discussion on the web visit https://groups.google.com/d/msgid/dcm4che/018feb52-3cbd-4211-a4b5-13ae91a810ben%40googlegroups.com.

[Gil]

Hey guys,

Just came to say I'm also experiencing the "Failed to launch JVM" error.

I tried to disable the Java Access Bridge and rebooted, but the error continues.

My computer is also used for development, so I wonder if the java installation interferes with Weasis.

Regards,

Gil

[Nicolas Roduit]

Unchecking this option seems to be not enough, see this post. You need to execute the command "jabswitch -disable" from the java installed on your system.

[Rob Meade]

Hi Nicholas,

That's just the thing though, I don't believe I have Java installed at all.

In one of my other replies I mentioned that I'd run a couple of commands that should display the Java version and all I got was an unrecognised message as a response.  This might be why I don't have the option in the Windows settings you suggested I unticked?

I can try the command you suggest, but I'm not sure it's going to work.

Kind regards,

Rob

[Gil]

Thank you so much for your time and effort! Running "jabswitch -disable" fixed everything, and without reboot.

@Rob maybe java is installed but just not in your system search path? Try looking for an Eclipse\Oracle\Java directory in your program files dir, could be hidden there.

Regards,

Gil

[Nicolas Roduit]

I opened an issue and found a workaround. It should solve the problem for the next version 4.0.2.