Skip to first unread message
gian78567
Aug 7, 2015, 10:26:11 AM8/7/15
to dcm4che
Hi,
I am running dcm4chee-2.18.1-mysq with weasis 2.0.3 and so far it has been working great.
Here is what happens:
I just updated weasis from 2.0.3 to 2.0.4. by replacing the files weasis.war and weasi-ext.war. (eventually I replaced even Pacs-connector with the latest version)
Everything seemed ok at first glance but then I noticed that PET files are not viewable anymore with weasis.
1- Actually I could not roll back and verify the same studies with 2.0.3.( for some reason once I put everything in place like it was,previous version, when I start the viewer the browser shows it is still looking for 2.0.4 and it hangs there until I close the weasis viewer.....here I need some help)
2-With the updated version of Weasis(2.04) I can see all another studies but PT. I am wondering what that is. It can't connect to the study and load the images.
the error is shown below.
The images are present and I can see them through dcm4chee-web3 preview viewer.
I attached the log.
thanks in advance for the good job you are doing here.
Gian
I am running dcm4chee-2.18.1-mysq with weasis 2.0.3 and so far it has been working great.
Here is what happens:
I just updated weasis from 2.0.3 to 2.0.4. by replacing the files weasis.war and weasi-ext.war. (eventually I replaced even Pacs-connector with the latest version)
Everything seemed ok at first glance but then I noticed that PET files are not viewable anymore with weasis.
1- Actually I could not roll back and verify the same studies with 2.0.3.( for some reason once I put everything in place like it was,previous version, when I start the viewer the browser shows it is still looking for 2.0.4 and it hangs there until I close the weasis viewer.....here I need some help)
2-With the updated version of Weasis(2.04) I can see all another studies but PT. I am wondering what that is. It can't connect to the study and load the images.
the error is shown below.
The images are present and I can see them through dcm4chee-web3 preview viewer.
I attached the log.
thanks in advance for the good job you are doing here.
Gian
Nicolas Roduit
Aug 8, 2015, 4:14:14 AM8/8/15
to dcm4che
There is no error on the server side. Please provide the log of the java console when running Weasis (in debug level).
gian78567
Aug 10, 2015, 6:09:06 AM8/10/15
to dcm4che
Hi,
attached you find two logs. One for a patient with PET study that I can open and one for a patient pet study I cant open.
Yes, for some reason I discovered that some pet studies are viewable but most of them are not.
Thanks for helping.
Gian
attached you find two logs. One for a patient with PET study that I can open and one for a patient pet study I cant open.
Yes, for some reason I discovered that some pet studies are viewable but most of them are not.
Thanks for helping.
Gian
Nicolas Roduit
Aug 12, 2015, 7:48:31 AM8/12/15
to dcm4che
According to the log file, the xml manifest contains invalid characters. This file (wado.xml) is located in the windows temp files in a directory called weasis-*.
This could be due to the configuration of the dcm4chee database. If the database has not utf8 encoding, you need adapt the configuration in weasis-pacs-connector with the porperty "pacs.db.encoding=".
Using applet is not recommended. It has been discussed several times on this forum.
gian78567
Aug 12, 2015, 12:11:15 PM8/12/15
to dcm4che
thanks for your help Nicolas!
I restored the 2.0.3 version and everything works well with it. This sounds a bit strange though.
I also removed the applet option as you suggested.
I haven't' change anything else and it works without getting into character set UTF8
Did something change from 2.03. to 2.04 and I should define charset?
well I am using mysql and I getting info on how to know what charset I am using
thanks
I restored the 2.0.3 version and everything works well with it. This sounds a bit strange though.
I also removed the applet option as you suggested.
I haven't' change anything else and it works without getting into character set UTF8
Did something change from 2.03. to 2.04 and I should define charset?
well I am using mysql and I getting info on how to know what charset I am using
thanks
Nicolas Roduit
Aug 13, 2015, 2:21:22 AM8/13/15
to dcm4che
The issue could be related to this modification in 2.0.4.
Could you send me the wado.xml (located in windows tmp in a directory called weasis-*) to analyze where is the encoding problem.
Reply all
Reply to author
Forward
0 new messages