I am not sure if this thread is being monitored, but I have tried everything else I can think of. I have the dreaded msg ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. ERROR: Java failed to start during the SAS startup. I am working with SAS Support. No luck there yet. I have tried by my count at least 5 different JREs. I have the following code which I execute after every mod to the config file, which I have modified 30x plus %put &sysparm; %put &sysscpl; %put &sysvlong; %put &sysaddrbits; proc options option=CONFIG; run; proc options option=JREOPTIONS; run; proc javainfo; run; The last suggestion was try jre6_181. That did have one noticeable impact. My program no longer hangs when in runs 'javainof' which under ever other version it did (hang - permanently). But it still comes back with an error last lines of log: ..... -Dtkj.app.launch.config=C:\PROGRA~1\SASHome\SASVersionedJarRepository\picklist -Xms128m -Xmx128m ) Java Runtime Environment options NOTE: PROCEDURE OPTIONS used (Total process time): ..... ERROR: The Java proxy is not responding. ERROR: The Java proxy's JNI call to start the VM failed. ERROR: Proc javainfo did not run correctly. Notes: 1. the 181 version that I was given to use has no client directory. Just Server and the jvm is in there, so its what I am pointing to. The sas system is finding it I think, based on the output of the rest of the log. I dont think this is related to the issue, because the 4+ other variants of JRE all did have client directories and they all had the same basic problem. 2. this platform is running windows 2008 data center 3. I have a local install on my PC running under Windows 7 Enterprise, which of course is working perfectly Any words of wisdom or support would be appreciated.
... View more