Java 6 Update 10 broke SEPM Console here as well.  You are correct, Java updates do tend to have issues with various applications more often than not.  I cringe every time one comes out.

I've discovered that you can ONLY run the JAVA that comes with the SEP CD.

Any other installs or updates, and you are on your own..............

I had to remove ALL traces of JAVA and all updates to JAVA, totally strip it, then install from the Symantec CD and all was well again.

I've turned off all Java updates.

Same here. SEPM (MR3) works for me up to Java version 1.6.0_7-b06 (Java 6 update 7), too.

FYI - just saw that Java 6, update 11 came out.  I just tested it and SEPM management console works fine. 

Seems to me that Sun must have recognized it had a little "issue" with 10 to update it so quickly to 11.

Can't confirm this my console don't start with Java 6u11. The javaw.exe just terminates after starting. If there would be any log file...

Doesn't work with update 11 on our end either.

You might have already tried this, but did you remove the Java 6, update 10 and reboot, before you installed the Java 6, update 11?  That's what I did and it works fine, but then again there could be lots of other variables between our different systems for why it works on mine but not on yours...

A quick question for you S3curityFreak:  Are you using the management console on the SEPM server itself with u11?

The reason I ask is that this bug with u10, and now u11, only rears its' ugly head when running the console from a remote machine.  The bug doesn't exist when running the management console from the SEPM server. 

This could be why it's working for you and not for the others.  Then again, maybe a reboot will do the trick.  Haven't had time to do so here yet, but pre-reboot I'm seeing the same thing as the others.  Console exits before initialization.

Edit:  After a reboot, still no love.  Had to dual-install u7 again for the remote console to work.  I do recall another thread here just after u10 was released mentioning that this would be fixed in the next MR after MR3.

Good point, Scott.

For the record, I was indeed running the console from a remote machine.

Yes, I am using SEPM management console on the server itself.  I would think that the problem would happen on any system where you have installed the SEPM 11.x management console, and where Java 6, update 10 is installed? 

I can confirm after testing, the remote console ability is broken now. I just tested on a host with Windows XP/SP3 (+all latest MSFT updates), IE7, + Java 6, update 7.  I first installed the SEPM management console by accessing/installing it via web browser, connecting to my SEPM management server and the SEPM management console worked fine.  Then I updated to Java 6, update 11, and it broke my ability to use the browser from this host to remotely connect with the SEPM management console.

UPDATE:  After I went through Add/Remove, uninstalled Java 6,  update 11...now remote SEPM management console works fine.

The issue has something to due with internal security changes within the Java runtime.  If it's like most other programs, security is more restrictive for remote connections than it is for local ones.  That's why this issue only appears for remote console installs.

I have the latest java version 1.6.0_11 and everything is working as expected.

Try uninstalling and then re-installing java or playing with the other java settings from the control panel etc.

Z

@zer0: guess how many times I installed/uninstalled various Java versions and combinations without any success!

@Scott: Sounds reasonable. Maybe there is a option in Java for this?