Replies: 3 comments 2 replies
-
@odoodo wrote that. |
Beta Was this translation helpful? Give feedback.
-
It seems like it writes the backup of the mirth configuration but it does not add the configuration map to the zip file. In later versions of Mirth Apache Commons lib has been replaced by Apache Commons 2. The code that seems to fail in your case is the part that detects the version of the Commons lib. As we are currently still on v3.7.1 (will hopefully change around the end of the year) it was not possible for me to test when I added the support for later Mirth versions. Thus, working blindfolded, it seems like I forgot to instantiate the PropertiesConfiguration for commons v2 (new after ? is missing). // prepare structure
var properties = useCommons2 ? org.apache.commons.configuration2.PropertiesConfiguration() : new org.apache.commons.configuration.PropertiesConfiguration(); (I actually wonder why nobody reported an issue before ;-) ) You can find the fixed code template here. Please let me know if this worked for you. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the help. Updating to the new version of the code template seems to have resolve the issues. |
Beta Was this translation helpful? Give feedback.
-
Hi,
We upgraded to Mirth 4.4 recently and are having issues using the backupMirth server code template that was popular on the other forum. I know we probably need to update versions, but it looks like other forum is having some issues being up right now.
Does anyone have an updated version of the code templates involved by chance?
We are getting this in the dashboard log, but it looks like it actually writes the files:
ERROR (transformer:138): unable to write file "e:/Mirth_Backups/2023-09-25/MirthDevServer.131_2023-09-25 09-18-33.zip": [JavaPackage org.apache.commons.configuration.PropertiesConfiguration] is not a function, it is object.
But then in the messages, looking at the error message shows this:
I've tried commenting out some things related to these errors related to getPath and they are no longer producing error messages that are viewable as ERRORS, they now show SENT, but the error in the dashboard log saying 'unable to write' still exists even though I see a ZIP file with the backup XML in it. So, just trying to see if the template has been updated recently to work with 4.0+ or higher.
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions