What version of VMWare are you using? We've never been able to reproduce this in all of our testing (and we do a lot of VM tests). VMWare in particular "fixes" the date and time so that it matches your system time, rather than the paused time. Is your VM time being fixed?
What function is returning the error? Is the app running as the VM is restored, or are you starting it after the VM is restored?