Just to follow up, we migrated from 3.8.7 to 3.8.10 and that fixed our issue.
The Encode library stayed at the same version number (2.43). I am guessing that the problem was in some RT code. Anyway, we are not seeing the error anymore. Cheers, Thierry -------- RT Training Sessions (http://bestpractical.com/services/training.html) * Chicago, IL, USA September 26 & 27, 2011 * San Francisco, CA, USA October 18 & 19, 2011 * Washington DC, USA October 31 & November 1, 2011 * Melbourne VIC, Australia November 28 & 29, 2011 * Barcelona, Spain November 28 & 29, 2011
