I ran through the process for installing 3.1.3a flawlessly (and I followed the install procedure to the letter). EXCEPT, after the final reboot of 3.1.3a, my CallManager, FTP Publishing and CTI Manager services all fail to start. Call Manager gives a database connection error, FTP gives "The specified module could not be found" (ISM won't open either, that says it can't connect to the local server) and CTI Manager gives a "Node Undefined" error.
Any ideas? Has anyone fixed this?
I have applied OSupdate2-3 and 2-3a and SQL sp4., both downloaded from Cisco Software site.
I did reapply all updates, service packs, and upgrades with the same results.
The "database connection error" is kind of interesting. I'm curious if the SQLSvc account's password had been changed before? If SQL doesn't start right, CallManager will give this error and refuse to start, and upgrades tend to change the service's LogOn account's password.
Wow Thanks. My TAC engineer mentioned that as part of his troubleshooting and I would think that after one documented case where that happened they would publish that info in the readme somewhere? It's not, I checked twice. At least that's what *I'D* do if I wanted to keep my customers happy. This has been a painful upgrade for the client as well as me.
I am off to rebuild my publisher now, any other "undocumented features" anyone knows about this process? Rebuild, Restore, Upgrade again...
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: firstname.lastname@example.org Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...