RemoteXP.vmdk is / was a monolithicSparse.vmdk - which following the logs was in a state so that WS did not accept it as a healthy vmdk.
With monolithicSparse this also means the embedded header of the file is damaged.
This again also means that all signature-based recovery-tools will not detect this as a valid vmdk of type "monolithicSparse"
So your situation is as follows: what ever your recovery attempts may have produced as a result : it is very likely meaning less.
If this is really valuable data then I hope you used a LiveCD for your recovery attempts and did not run them from the affected volume !!!
Anyway - let me have a look - I maybe able to locate the file in your recovery results by using other serach criteria.
To get an idea about the reliabilty of your scans - please specify the tools you used.
Before you give up - call me - see signature
Ulli