Here is the virex link for orbosrvr.exe (version 6.23):
OCR engine embeded in a 3rd party software package we use. Here is the company webpage:
17/41…all the same, and not many of them “generic” detections, that does not look like a false positive.
I understand that was my first post here (why I registered), but I am not new to this game. It’s a problem child, and the last AV vendor that we used also false detected this particular file a few times, however they currently have managed to update their definitions to deal with it. I’m pretty confident it is a false positive.
First seen by VirusTotal
2010-06-15 15:13:40 UTC ( 1 år, 11 måneder ago ) this old and not FP fixed… suspicious
Pondus, any results from the lab tests?
check your mail
Norman lab confirms - False positive
Falsepos case on file orbosrvr.exe (a94a31b99e34bc2c62d5e26c9f37782f) has been processed. FP confirmed!
Thank you for the confirmation. 
So here is my newbie question: What (if anything) has to happen now to get that worked into a future definition for avast?
Whilst Norman now consider it an FP, yesterday, it is still listed in the last scan VT Results from yesterday.
Now it is also detected by avast, see latest VT Results for that file, https://www.virustotal.com/file/a0965a96a07a76f6b10639f761936f895b2f1086c6b020bcafa953ef5edb98b1/analysis/.
Avira confirms False Positive
The file 'orbosrvr.exe' has been determined to be 'FALSE POSITIVE'. In particular this means that this file is not malicious but a false alarm. Detection will be removed from our virus definition file (VDF) with one of the next updates.
The false positive was because of the polymorphic process structure and background service of that executable, but the file wasn’t considered to be malware by Prevx either,
polonus