I have verified this is a pathing issue. I renamed the jre folder where java 7 lives and restarted the app. The window came up as expected and I was able to see the console of the remote server. Now the question is....How do I "fix" this WITHOUT removing java verson 7. I require both versions of java and it's not acceptable to only be running one verion. By the way, when the window came up I look in process explorer.....The java that was started DID NOT come from the Dell install. It came from my local windows install. So while the initial start of the dell management software works, the spawn of the console connection itself is using the local OS version of java and not the supplied dell version of java. DOH!
Please either fix or give me an idea how to get around this issue WITHOUT making changes to my system, like renaming the jre folder every single time. It's tempting work-arounf but does not fix the issue.
gcollins2013
3 Posts
1
August 28th, 2013 10:00
All:
I have verified this is a pathing issue. I renamed the jre folder where java 7 lives and restarted the app. The window came up as expected and I was able to see the console of the remote server. Now the question is....How do I "fix" this WITHOUT removing java verson 7. I require both versions of java and it's not acceptable to only be running one verion. By the way, when the window came up I look in process explorer.....The java that was started DID NOT come from the Dell install. It came from my local windows install. So while the initial start of the dell management software works, the spawn of the console connection itself is using the local OS version of java and not the supplied dell version of java. DOH!
Please either fix or give me an idea how to get around this issue WITHOUT making changes to my system, like renaming the jre folder every single time. It's tempting work-arounf but does not fix the issue.
Thanks!
george.perkins
1 Rookie
•
58 Posts
0
May 21st, 2015 10:00
I am looking for a solution to this as well.