Saeed,
The error you are seeing is generated by your browser. It doesn't like something it's being asked to execute in a browser based script. Normally in web applications, the root cause of this has to do with either ASP/ .NET support issues (like a library not being loaded) or a Java Runtime Engine mismatch. Not all JRE's are equal, and unfortunately what works with one Cisco application doesn't necessarily work with another. Of course, this assumes that the error isn't actually with something you're doing wrong (like trying to load character data into a integer field).
Troubleshooting this problem, I would go about like this:
1. Reboot the server. This is to make sure you clear any issues that might be hanging out with the OS or the application itself in a flakey state.
2. Log onto the UCCX server itself, either directly on the console or via Remote Desktop. Try doing the same action from the server console that was failing and see if it works there. If it works there, then the problem with with the JRE on the machine you were working with. Generally, if you need to switch JRE versions, JRE version 6.0.12 is a pretty good one to use for the version you're on.
3. If it also fails on the console, confirm the JRE version you're running there. You should never allow the JRE to update itself outside a Cisco installed patch unless told to do so by TAC. Open the Windows Control Panel, and find the Java icon. Double click it to open, and select the Java tab. Click the view button, and it will show you what versions you have set up on the machine. My lab machine reports 1.6.0_12. If this isn't what you have, I'd suggest you download that version and install it.
4. If everything matches up and you still have a problem, check and see if you can load a very simple script and then attach it to an application that simply has steps like start, accept, play a prompt, and hang up. If this works, but you still have an error with your script, chances are something is wrong with the script you're trying to load. Open it with the editor, and run the validator on it. If it passes, but still won't load, try removing any time of day / day of the week steps, and then see if it will load. If that works, make sure you're working with the version of the editor that is current for the patch level you're on, and remove those steps, and then rebuild them in the editor. Those steps are problematic across versions.
This should get you started. Let us know how it works out.
