Endpoint Protection

We get  the following error on accessing SEPM from a remote console.

Please advice how to resolve it.

 You need to use JRE 1.5 as 1.6 has some issues assocated. 1.5 and below doesnt work too well either

Hi

I have faced the same problem but ressolved it by unistalling  the java runtime and reinstalling JRE 1.5.x. Donot use 1.6 it has some buggs in it.

We have Win XP Professional with SP2 and IE7.

Our control panel, Add Remove program shows the following two entries...

Java (TM) 6 Update 13
Java (TM) 6 Update 7

Do you want us to remove both the programs above?

How do I get the JRE 1.5

Tejas

Yes Mr Shah

 You can also go to control panel->Java and look at various JRE settings. You can disable a specific JRE version to see which version is causing the issue.

Why, with all the maint. releases of Endpoint, have they not allowed for newer versions of Java?  It's really difficult to remember to not upgrade Java on the one machine I check SEPM with.  All other machines are up to date with Java, but I cannot update one machine because I use it to connect to SEPM.  Are they ever going to allow the newest version of Java to work for SEPM?  It's a major pain to keep one machine at an old version when all other clients in the organization are up to date.

If I were you I would set up a test box running 1.6 and see if you can connect to your SEPM. There have been known issues running 1.6 but your configuration might allow it. There have been reports of it working without a hitch depending on how you upgraded Java. I just want to point out as well from a personal standpoint that Java 1.6 seems to have compatitbility issues with a variety of programs I use ie not just  SEPM : ) . I have been esspecially unsuccessful using Java 1.6 on my Mac and the variety of their programs. Don't get me wrong I am not saying that there might have been something we did to cause this incompatability I just don't like to jump to conclusions when other software has compatibility issues with 1.6. Just a thought
Grant-

Same issue with me with 1.6 as a workaround I using rdp then manually launch SEPM console.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008110710263848

How do I get the JRE 1.5

Hi as stated by bjohn, you should install

JRE 5 Update 15
Cannot find..

JRE 5 Update 18 (try this)
http://java.sun.com/javase/downloads/index_jdk5.jsp

JRE 6 Update 7
http://wareseeker.com/Web-Development/Sun-Java-JRE-6-Update-7.zip/8058465

Just by removing Java (TM) 6 Update 13, the problem has been solved.

Tejas

My musings on the SEPM/Java conflict:

I don't claim to be a Java expert, that's for sure. From what I've read, however, where JRE 6 Update 10 and higher breaks applications, it tends to be because of its increased security. Which, if true in this case, makes me wonder why Symantec feels it's OK to not support anything higher than JRE 6 Update 7 on a security product.

Actually, I wonder that whether security improvements are the cause or not. But especially if they're security improvements at fault.

Another puzzle: The http://<servername>:8014/reporting console works perfectly regardless of Java version. The reporting console represents (near as I can tell) 100% of the functionality of the Home, Monitor and Report buttons on the SEPM Console. So the only thing that's failing is those 3 top buttons in SEPM Console and the child windows SEPM opens from hyperlinks. Sounds like they have at least one problem with JRE 6 Update 10 & higher and at most, 2, and only with specific UI functionality. Directly underneath the pretty buttons in the left pane of SEPM and the hyperlinks in the right pane, everything works fine. Doesn't sound like it's going to take a rewrite from the ground-up to solve it.

This core management functionality should have been fixed long before now. Hopefully in MR4 MP2...

But until it is fixed, I'm darn sure not going to downgrade JRE security just for SEPM. I'll live with the Reporting console workaround--and continue to curse Symantec every time I do.

Jeff,

Just to give you a bit more information (I've posted this a few times before too).  The reporting website will work fine with later versions of Java (since it doesn't really use it, just PHP), and the rest of the SEPM console will generally be fine too.  You've hit on the bit thats causing us the problem, and thats the bit in between the SEPM console and the browser.  Its called JDIC, or the JDesktop Integration Component.  You will see it running on your machine when you launch the console, its IeEmbed.exe.

The problem comes from the fact that when Sun updated Java 1.6 to anything post U10, it broke the version of JDIC we use.  We hoped it would be as simple as dropping in the new JDIC and carrying on as normal, sadly its not.. and needs some work to make everything work again.  We are working on it, but its not going to change in MR4 MP2.

If security is what you are worried about, then JRE 1.5 Update 18 should work just fine and has all the security fixes in that 1.6 Ux has.  Yes, I realise its going end of life, but it isn't yet and we will have this sorted soon (long before the end of the year).

Turning out to be more interesting than wht I have thought of initially. Especially after Jeff's comments.

Hi

Its good to hear ur problem was ressolve jusy by removing JAVA (TM) 6 update 13. I will try this well in future.

Ajit

Ya Ajit, go ahead. Lot of time we think very complicated, but the solution comes by doing some simple things.

All the best.