Mon Jun 03, 2013 7:28 am
Re: The JVM could not be started.. (£5 for anyone who can he
By the looks of it SaS is still messing with Java. I have some experience distributing Java with a product we develop at, and you can get all sorts of problems if the installation is messed up that are such a pain to trouble shoot. It may be that you restored jvm.dll from a different version of Java than you have now, or that SaS has done something with another file.
I would be tempted to download java. Remove SaS, reboot, re-install Java and see what happens, if it works, then re-install SaS, reboot and see if it still works. You could also try the lastest Java 6, as the jvm.dll will be differnt. However, what ever you do I would contact SaS seeing as if you want to keep using SaS, its going to need to be fixed/you need to work out which options are needed so that it doesn't keep doing this, as by the sounds of it/the timing of all of you, its a definition update gone bad. They have a forum section for False positives, or you could try email them.
I would be tempted to download java. Remove SaS, reboot, re-install Java and see what happens, if it works, then re-install SaS, reboot and see if it still works. You could also try the lastest Java 6, as the jvm.dll will be differnt. However, what ever you do I would contact SaS seeing as if you want to keep using SaS, its going to need to be fixed/you need to work out which options are needed so that it doesn't keep doing this, as by the sounds of it/the timing of all of you, its a definition update gone bad. They have a forum section for False positives, or you could try email them.
