Unified Manager Not Displaying Properly

[pronei]

I've been fighting with a BCM200 for almost a year now and I finally won.

I thought my BCM200 was toast because I could not get all the drill down menu's in Unified Manager to work properly. Specifically, I could not manage the Telephony Services, The Media Bay Modules or the Media Services Card. So naturally I assumed I had a defective BCM200.

After numerous HDD re-images, Mobo Swaps, & MSC swaps. I had finally called it quits.

Then one day a Java update pops up on my computer and I run the update. Then it clicked, I was running the wrong version of Java. I immediately switched to the Java version that comes on the BCM and voila! A year of fighting with that BCM200 is over, after everything I tried, it was the most obvious yet most elusive solution I could have imagined.

I'm posting this in hopes that if anyone seems to be having the same problem I did with my BCM200, you will first check your Java software version BEFORE you decide to tear your BCM into pieces.

 

[pccal]

This is a known problem in older windows based BCM's. There was a patch to fix the issue as the Unified manager would not work properly with Java 6. The fix is to run the Java patch or roll your Java back & turn Java updates off.

 

[pronei]

Yeah, I found that out as well, after I my fight ended

 

[TLDuk]

wow this has been a know problem for over 18 months a quick forum search would have found you the answer a long time ago..

If its not broke tweak it..

 

[snowman50]

There is an OLD saying in the BCM world


"If it doesn't work REBOOT IT!
If in Doubt PATCH IT!

 

[Deweyhumbolt]

Pronei, I know your sharp. I've followed your posts, you know BCM/CSK/Call Pilot and we appreciate your honesty and integrity!

It's easy to cherry pick questions.

Adversity is Opportunity

 

[pronei]

Simple case of assuming the worst, when the fix was so easy. Although, let me give you a bit more background.

This BCM was in service for 4 years. My company closed the site this BCM was located at and we took the BCM back into inventory where it sat for another year. When I had use for that BCM again I fired it up and found that the BCM had a corrupted HDD, it was caught in a boot cycle and received a windrv.dll BSOD on boot.

So I automatically assumed the worst of this "cursed" BCM.

This is the ONLY BCM200 I have/manage.

During the 1 year the BCM sat in inventory I had a lease swap come due on the laptop I used to manage that BCM. On my new laptop, it never occurred to me to install a 100 year old version of Java that I needed to manage a single 5 year old BCM200.

So, basically after the HDD crashed, and I replaced the HDD, I couldn't manage the BCM's Media Bay Modules, Telephony Services, etc. I assumed the Mobo, the MSC, the PEC, were all suspect. Yet the final answer was the simplest solution, check my Java version.

Anyway, so ends my saga of the BCM200 war!