We have installed UCCX8.5 on ESX4 everything goes fine as far installation is concerned now after installation UCCX Engine is not coming up when we check logs we find this
Service operational status is DOWN. Cisco AXL Web Service;Cisco UXL Web Service;Cisco Unified CCX Engine. The alert is generated on Tue Apr 26 17:02:46 PKT 2011 on node uccx85.
But when we check these services they all are in running state.
Anyone knows how to solve this .
Without Engine logs it's tough to know for sure what is preventing the engine from starting up. One possibility is a defect on CUCM, CSCtn38319 that causes the engine to crash with an OutOfMemory exception 2 or 3 minutes after the startup attempt. Another cause for this issue that I have seen in several cases is a driver issue that prevents the CMT Subsystem (part of the engine) from coming into service. I have seen this problem several times, but only when the VM is running on Hardware not compatible with UCCX.
I'm having an issue in my lab install where the CMT Subsystem not starting up, and RTMT shows:
Error: Failure to get an application: %[Param_0=com.cisco.wf.media.driver.DriverException: ERROR StreamManager::getApplicationId - failed appId=-1, confId=-1, partyId=-1 ERROR][
I'm wondering if your driver issue applies to my problems; I get an error on booting the VM that the hardware is not supported. Can you provide more information for the fix?
Sounds like you and I are having the same issue. When you try to start the engine does it hang on CMT and never move past that and then ultimately put everything back into SHUTDOWN state?
I never got it working and just abandoned the thing altogether as it was only to demo TAPS in a lab environment. But here's a full description of my issue that I sent to a co-worker:
"I'm building the environment in my home lab, and installed UCCX 8.0(2) for TAPS. UCM is also v8.0(2). I've installed, loaded the 30-day demo Premium license, and configured the TAPS application with the .aef file downloaded from the UCM. I completed the CTI Route Points and created the trigger for the pilot number.
After a fresh boot of the CCX server, all services show as "IN SERVICE" except the CCX Engine and the subservices, which come in service for a moment before the Manager Manager subservice shuts down and the Subsystem Manager follows. I can't find any logs in the web UI, but RTMT shows an error:
Error: Failure to get an application: %[Param_0=com.cisco.wf.media.driver.DriverException: ERROR StreamManager::getApplicationId - failed appId=-1, confId=-1, partyId=-1 ERROR]
The logs are all swell and everything is coming in service, then that hits and it all starts shutting down."
This is an old fix but I believe it still works: http://www.fatturtle.com/2010/06/ip-voice-media-streaming-app-service-wont-start/
The process is basically:
1) Boot to an Ubuntu live CD to gain access to the file system
2) Copy the Intel binaries and change the name so they work with Athlon (AMD)
I believe the file structure is slightly different on UCCX, but you can still find what you're looking for.
Also, I believe this is fixed in 9.x and 10.x versions since they have support for specs-based UCS. So give those a try if there's no compelling reason to be using 8.x.
Thanks for that mate. I will give it a try. I've had the same happen on both ver 9 and 10. Will try rebuilding it again (3rd time lucky perhaps?). Will update on how I go
I have seen the same in our installation.
The server is running correctly and the engine is started but I see that in the Alert Central from the RTMT ...
The strange thing is that when I look into the CM & CCX, all the services are started correctly.
As we are sometimes experiencing some agents disconnection from calls, I'm investigating all the parts that can give problems. Not sure if this can, but checking all the stuff.
Anyone have a clue?