CCM Java Errors 1

[GeorgeKC]

Hello all,

I'm hoping that perhaps someone has seen the same problem I seem to be having with CallManager 4.2(3).

We currently do not have the CDR flag enabled, but wanted to do so.

Today when attempting to change the CDR flag from False to True - the java applet doesn't seem to respond to the fact that something on the page has changed. Thus the "Update" button (as well as the "Set to Default" button) remain grayed-out and cannot be used. The only button that is available is "Advanced".

Obviously, as a result, I cannot turn on the collection of CDR data or change anything else on that page.

I've attempted to use a different browser (Firefox instead of IE6) and I've updated Java to the latest version (1.6_13) but it makes no difference.

We have 1 Publisher and 1 Subscriber and the issue is the same on both machines.

Would anyone happen to have any ideas how I can resolve this problem or what else to try?


Thank you.

 

[Iwontremember]

reboot?

Hope this helps.

 

[GeorgeKC]

Yeah - I guess I didn't mention I had already tried that, too. No joy.

Most of what I've used within CCM has been merely adding/deleting phones, extensions, etc. The system was already up and running when I started.

But I've noticed different errors in other sections besides Service. The page for Servicability actually shows a yellow "!" with "Error on page" in the lower-left-corner of IE whenever you make a change on the page. But the Update button never changes (remains grayed-out).

When you click on the yellow "!" it provides further information about a java error. I don't have the exact verbiage in front of me but it is something like:

"Line 4 document.frmControlsomething.buttonStart is null or not an object"

I connected to the Publisher CCM today from a remote machine using IE7 and Windows XP (the CCM server is W2K and IE6) and I received the same errors/unable to click update. I personally think something is hosed in the .asp pages being served. It is too much of a coincidence that both the Publisher and Subscriber are acting the same

But I have no idea if they can be resolved without reinstalling - likely from scratch.

Any other suggestions would be appreciated.


Thank you.

 

[whykap]

what happens of you do this from the publisher itself?
From a terminal session right on the pub instead of using a remote machine or another PC?

 

[GeorgeKC]

whykap -

We normally work directly in front of the Publisher, so the result is the same and this is where I first noticed the problem.

Once I saw what was occurring, I tried to enable the CDR flag on the Subscriber (since notes indicate it needs to be turned-on on each node). I was in front of the Subscriber and the issue was the same. That is when I tried a different browser/java update - with no luck. I then tried to connect from a remote desktop and still no luck.

Thanks.

 

[whykap]

It's hard to say without looking at this closer. If this is service affecting I suggest a TAC case.
You mentioned remote desktop. So you just use another PC but you RDP to the server?
What about from another PC on the network, running IE6, open your browser and type:

https://publisheripaddress/ccmadmin

still the same outcome?

Are you using MLA by any chance? Could it be the account you log in as does not have rights to enable services? Only read?

 

[GeorgeKC]

whykap -

When I say remote desktop I'm not talking about RDP, but rather connecting to the .asp page using the browser on another machine (

https://)

- and yes the outcome is the same. I've used another machine running IE6 and one running IE7 with no change. Since I'm at the same location as the CCM servers, I have not used a terminal service or RDP connection.

We may indeed be using MLA, I wasn't even aware of what it was before you mentioned it. I had asked our IT director if there were any other usernames/passwords for CCM but he wasn't aware of any. It may be that this is the problem.

I can tell you that the username/password for CCM is 'saved' in IE6 so that it is remembered. The username that appears upon login is 'PhoneAdmin'.

I'll check to see if MLA is enabled. If it is then I'll have to ask the IT director further regarding other usernames/passwords.

I hope this is what the issue is - thanks.

 

[GeorgeKC]

whykap -

Thanks for the assistance - it was indeed an MLA issue and the IT director didn't have the username/password for anything other than PhoneAdmin.

Ended up reseting password for the CCMAdministrator account so I could login and make the necessary changes.

Live and learn.
Thanks again.

 

[whykap]

Right on. Glad you fixed it anmd it works.