To update this thread... the issue being discussed here by andybon appears to have been resolved. We applied a fix on his site and thus far, all is well. It's been discussed in another thread. Hard to keep track of everything when people get the same stuff going in multiple threads. Anyway, we did update the 2.7.2c package with this fix. Didn't change the version letter. Updated yesterday though.