#1
|
|||
|
|||
![]()
Hello,
I am using Mirth 1.8.2.4472, with 2 undeployed channels, nothing very special this is for a test. Then I go to Settings->Backup , configuration file is created (attached to this post). And now I go to Settings->Restore... bam ! 'Invalid server configuration file' , xml file looks correct to me. xml parsing problem from Mirth ? could it be fixed for 2.0.0 ? Thanks |
#2
|
|||
|
|||
![]()
Problem is coming from 'Inbound template' there is really a problem with Mirth xml parser. Seems like a bug for me.
|
#3
|
|||
|
|||
![]()
On line 227 in your inbound template you have 2 characters that are illegal. If you remove those two characters, then your backup loads fine.
__________________
Mitch Dempsey Software Engineer Mirth Corporation |
#4
|
|||
|
|||
![]()
I know but it should be a good idea to encode its content to B64 when illegal characters are detected, if I export then I must be able to import too (without tweaking) so this is not a feature this is a bug.
|
#5
|
|||
|
|||
![]()
It's done in Mirth versions up to 2
|
#6
|
|||
|
|||
![]()
I am using Mirth 1.8.2, I do not understand your answer sorry.
|
#7
|
|||
|
|||
![]()
Sorry, the aswer had no relation with this thread. IMHO Those special chars should be removed and never written to a backup file
Last edited by albertosaez; 09-06-2010 at 06:42 AM. |
#8
|
|||
|
|||
![]()
I know but I imported a HL7 file as template, so if I can not backup this kind of template... really there is a problem, this is not an exotic format, this is pure HL7.
|
#9
|
|||
|
|||
![]()
Please create a jira issue with the exact hl7 template that causes the problem, along with the steps to get the error. As long as it is 100% reproducible we can find a long term solution for it.
__________________
Jacob Brauer Director, Software Development NextGen Healthcare |
![]() |
Thread Tools | |
Display Modes | |
|
|