I upgraded from CM 3.09 to 3.12c and my pilot points stopped working. Deleting the pilot point and re-creating it doesn't fix the problem, either. Also, new pilot points do not work, either.
If I delete the pilot point and create a phone, with an extension identical to the deleted pilot point, all is well in Mudville.
I checked the NumPlan table and there are no CS listings for ANY pilot point record. Is this normal? Could someone check their numplan table and see if their pilot point record(s) and let me know which field(s) are populated with the corresponding CS ID?
I am working with TAC on this one. San Jose upgraded one of their servers to CM 3.12c (from 3.12a) and they don't seem to have any problems. More troubleshooting today, but I may end up starting from my previous configuration (3.09), re-upgrading and see if I have the same issues.
It was definitely a bug in the upgrade. Per TAC, the directory team is looking into it.
The fix is rather simple. It has to do with one small setting in "Directory Administrator". TAC changed my setting via Terminal Services over the Internet and all is fine. Initial testing shows it seems to be fixed. If you need to know how to fix it, my TAC case number was B917878.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.