aha!

"This environment has been running for almost 4 years and we haven't had a problem until now and it's on a single server that we brought online"

So,
(1)Your problem may be with the new "single server"
and
(2)You can't fall back to what used to work just fine
and
(3) you see it as better to have a possibly buggy server causing your business to be invisibly MISSING data (which might, IMO, lead to "bad business decisions") than to take that sucker down and see what ails it?

Belated UPDATE/afterthought: if I read you correctly ie: that package ran fine on (a) different box/boxen, I have to suspect a bad Perl install or some sort of (borken) OS problems.

Re-UPDATE <important>: See BrowserUK's Re^2: Prevent Perl Command Line Interpreter Popup From Appearing On Perl Crash, infra (way below, in fact.)