UC520 CCA 3.1 Error: com.cisco.nm.lib.cmdsvc.cmdsvc

[Jesse Shumaker]

I always get this error com.cisco.nm.lib.cmdsvc.cmdsvc when connecting to my uc520 and after this error nothing works right within CCA. I actually have to do a force close within task manager on the application to get it to exit out. I have done changes via ssh and I've heard that this can have an impact. how can I tell where in the config file the issues are and howto fix this?

thanks

[David Trad]

Hi Jesse,

You need to avoid CLI changes without the appropriate certifications or you will invalidate your SBSC contract.

Firstly totally remove CCA from your system, use a program like Crap Cleaner (www.ccleaner.com) to clean out registry entries, also manually delete it from program files, and in your C drive (with hidden folders enabled) remove the .configassist folder once you have made a backup of it ( this folder contains settings and backup history).

Now before you reinstall CCA, run crap cleaner again making sure it is deleting bad registry entries and all cached information. Finally make sure you install the latest Java and Flash before you re-install CCA.

This should resolve that annoying error popping up all the time, if it doesn't then the system gas other issues and will continue to struggle with using CCA ( I guess this is what you get when you program with Java )

Give that a go and let us know how you go

Cheers,

David.

[Jesse Shumaker]

some things are easier with command line.especially task automation. thanks for your response. I tried what you suggested and even logged in as another admin but the error continues. Isn't this a common issue or do most people only use CCA and no command line?

After that error com.cisco.nm.lib.cmdsvc.cmdsvc comes up and I don't do anything the following message will appear about voicemail.

voicemail communication failure: Voicemail may not be working correctly, We strongly recommend that you choose yes and run CUE diagnostics to verify that the voicemail is working properly before continuing. so I do choos yes and check status and the message that comes up says diagnostics completed. voicemail may not be opperational.

[mcasimirc63]

People who want support from Cisco, use CCA only.  If your company has the Express UC or Advanced UC specialization you can choose one path for support, CLI or CCA, never both. 

CCA is not compatible with CLI, outside of a certain list of approved commmands from Cisco.

[David Trad]

Hi Jesse,

I was just going through some of my notes and one of them pertaining to a support case I had open a couple of months ago regarding this exact issue yielded some results but no closure to the problem.

It was in relation to CLI changes being made on the system and when CCA loads up it gets a snapshot of the configuration and borks about the CLI changes.

However this issue also happens on systems with NO CLI configuration and can be resolved with a complete fresh re-install.

To-date no resolve could be found for CCA to work with the CLI changes made, actually my notes show me that we couldn't even find which CLI change caused this.

If Dave Harper was still lurking around he might have some advice on it, but I think he is more focused now on the UC-320W at the moment, so not sure if he is up-to-date on current CCA operations.

Sorry I couldnt be of more assistance to you

Cheers,

David.

[Jesse Shumaker]

hmm... that sucks. just surprised that the product would be made so "defenseless" against another way of configuration. can I reach dave harper by phone to chat about this? I would hate to have to wipe the config away. I have a lot of configuration setup.

[Jesse Shumaker]

if I moved this program to another machine entirely would that help?

[David Trad]

Hi Jesse,

Sorry for the late reply

OK here is what I do, I always have a dedicated PC for running CCA (Yes sounds like an expensive way of doing it) but I normally use one of those <$200 laptops with a vanilla flavored Windows 7 install on it, I also turn everything off such as Firewall, UAC, AV etc..etc.. Then I install the latest version of Java and Flash onto it before installing CCA.

This is then my dedicated CCA building system, the only time you panic is when there is a new version to install, occasionally the upgrade causes unusual issues and to-date still do not know why. But all-in-all a dedicated system removes all issues and all possibilities of issues to a greater degree.

Following applications I run on this dedicated system to support the UC deployments:

• CCA  (Obviously)
• PSPad (Free text editing software and very valuable)
• Solarwinds or 3Cdaemon TFTP client
• Cisco Configuration Professional (Just incase you have to work on any ISR's or 800 series routers)
• Cute PDF if you want to turn Topology views into PDF for record keeping
• Putty or my preferrence SecureCRT for CLI work

These are the basic essentials and a great place to start

Cheers,

David.

Message was edited by: David Trad

[shane.hunt · Accepted solution]

Jesse,

I know this answer is well after the fact, but I've seen that many other people are asking this same question so I thought I would add my findings.  I had the same issue tonight trying to install a software pack on my UC520 using CCA 3.2(2) so I fired up wireshark to see what was going on at a packet level. 

I found that for some reason CCA wants to use telnet in addition to https to talk to the device.  Allowing telnet in addition to ssh on the vty fixed this for me temporarily, but it's obviously not a great long term fix since I don't want telnet accessible on my router.

HTH,

Shane

[Jesse Shumaker]

wow yeah that does fix it. nice work man. i work around for this is making a an access list for telnet access from only the device that uses CCA to manage the uc.