Installing CCM 3.3.2spB Publisher and 1 Subscriber. We had to reimage the SPE's and have the Publisher up and running. When we attempt to load the Subscriber it complans of not having SQL on the machine and the CCM install throws and exception and quits.
Part of the problem may be that we are waiting on a distribution copy of the ICS install software. I have downloaded and installed System Manager 2.6.0 on the Publisher and loaded the Core on the the Sub, but that does not load SQL on the machine. From some docs out on CCO, the CCM installer is supposed to do that.
Anyone know if there is a difference between the 78xx MSI installer and a 77xx installer?
Supported order of CallManager installation on ICS is
1. Reimage with ICS OS CD
2. Install ICS System Software 2.6.0
3. Install win-OS-upgrade-2000-2-3.exe
4. Install Call Manager 3.3(2)
5. Install OS-sp (current version like windows or SQL etc)
6. Install any Call Manager sp's(like Service Pack B for 3.3.2)
What I understand from your email is that CCM installation is throwing an exception about not having SQL on the machine. As I mentioned above OS patches has to be installed after CallManager installation, but I don't think your problem is because of installing OS patch before CM installation. SQL will be installed as part of CM installation. If for some reason SQL wasn't installed properly and CM installation is proceeding then it may throw this type of error.
Can you open a TAC Case and send us logs from "C:\Program files\Common Files\Cisco\Logs"
The CM CDs/installs are identical. We use the exact same CD as CM ships with an MCS. The OS is different and we use the OS-upgrade. It sounds like the install of CCM failed for some reason. I'd suggest getting the install logs to see why it didn't install SQL (see what the errors are).
Note that the OS CDs are different. The MCS OS CDs are not applicable on an ICS. You need to ensure that ICS System Software (Core SW) is installed on the Subscriber SPE. If that's not present, the Subscriber install would fail.
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.