Normally these problems occur if two different modules use the same library but a different version of it, resulting in two different versions of the jar file in your userlib folder, since these come with the download of the module. Then the solution always is to remove the older version and hope the module using the older version can also switch to the newer version.
If I read your story it seems to me that exactly this case isn’t valid here; one of the modules can’t handle using the upgraded library and it’s affiliated files. The approach I would follow then: