UTF-8 uses multi-byte sequences for non-ASCII characters and the isi code that 
  was reading these back from the isi_avscan.db was not able to always handle this 
  in the "Infected File" names. The 'isi avscan report threat -a' would stop as 
  soon as it hit one of infected files names with extended characters.   The WebUI 
  would not display any information in the threat tables if one of these file names 
  showed up.  This problem is complicated by some customers that switch encoding on 
  the cluster from UTF-8, this makes it possible to have a path in UTF-8 but the 
  infected name in a different encodeing.   The fix here allows the code to handle 
  these encoding problems.
