We have encountered a problem with SandBlast TE250 equipment.
We have cases where letters from the MTA go to Bypass without waiting for a response from SandBlast. When such cases occur, we see the following errors in the ted.elg directory.
[TE (TD::Surprise)] te::Emulation::EmulationInvestigator::HandleFileEmulationFailed: {CA........} Failed to emulate file on image 'e........' (file status: VM assigned): Internal virtual sandbox communication error
[TE_TRACE]: {................} Run 3 for image: 'e50....' ended with verdict 'Error' (0 malicious runs, min:2), reason: Internal virtual sandbox communication error
[TE_TRACE]: {................} verdict 'Error' set for image: 'e50e...' (WinXP,Office 2003/7,Adobe 9) by: 1, reason: Internal virtual sandbox communication error
[TE_TRACE]: VM 272 KeyPoint: Terminating VM due to error: Failed to connect to SYMO client
[TE (TD::Surprise)] te::Emulation::EmulatingVM::TerminateWithError: VM 272 (Creation In Process): Terminating VM due to error: Failed to connect to SYMO client
[TE_TRACE]: VM 272 KeyPoint: Terminating (error occured? 1, detected events: 0 malicious, 0 benign)
We found similar sk120479 and sk135392, they don't fully correspond to our problem, but they are similar.
Both SKs say about TAS. Unfortunately our existing cases in TAS are going very long, so I would like to know if anyone has any experience with similar errors and how you can diagnose these errors?