Creating new CCX applications with new Scripts

[Joel Fox]

Good afternoon. I'm currently running UCCX version 9.0.2.11001-24, and I'm attempting create a new script and application for one of our call centers. I can create the script easily enough, but when I try create a new application and attach the new script, I get an error stating "An error occurred while loading the Script SCRIPT[TestHelpDesk.aef]. Please check log for more details." I'm not certain what logs I can check. I saw a related post suggesting to check the database status in the Serviceability page, and everything appears to be up and running. I'm using the UCCX editor from my CCX server which is 9.0(2.00). I know this worked right after we upgraded from v7.x a couple years ago, but I don't do too much with uccx aside from adding agents and changing prompts. Without having a deeper knowledge of this, I am creating a TAC case to see if anyone has a suggestion. I did try changing an application that is rarely used and tried using the new script, and I received the same error stated above.

Any suggestions would be greatly appreciated!

[zdesignstudio]

Did your script pass validation in the editor?

Please rate useful posts and mark answers as correct if applicable.

[Deepak Rawat]

Is it happening just with this script or any other script as well. How about testing with one of the default system script and see if that works.

Regards

Deepak

[Joel Fox]

It appears that the issue is with a bug in the current version of UCCX that I'm running. The logs do not automatically purge, and the log file was at 100%. The temporary solution is to use RTMT to periodically purge the logs until a permanent fix is in place. The permanent fix will be upgrading to the latest 9.x release, which is 9.2. This bug is fixed in this version, but I need to do some research to ensure that upgrading UCCX to 9.2 will not have any adverse effects within my callmanager environment. I may need to upgrade callmanager, which is currently at 9.1.2, but as I said I need to do some research first.

[Deepak Rawat]

Joel, you must be hitting below defect then:

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCul18667/?referring_site=bugquickviewredir

However, please note there had been below defect opened in lieu of CSCul18667 that shows the known affected releases as even the latest version of 9.0(2) i.e, 9.0(2) SU3, 10.6(1) and even 11.0(1).

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv76430/?referring_site=bugquickviewredir

Please check this with TAC for a definite confirmation that if the defect is

1) Fixed or not in the first place

2) Which version has the fix

3) Is there any ES that you can apply on your current version avoiding the upgrade then

Regards

Deepak

[Joel Fox]

I did speak with TAC regarding this; they stated that version 9.2 fixed this issue and that it wouldn't be a major upgrade. Unfortunately the only thing I can do to fix the issue permanently is upgrade to v9.2, but that isn't a huge issue; I just need to get it scheduled. Thank you for your input!