Appmanager.sh Internal Error
Cisco Bug: CSCub72346 - Refresh Upgrade failing to 8.6.2 and above in Install DB Component Last Modified Sep 28, 2016 Product Cisco Unified Communications Manager (CallManager) Known Affected Releases 8.6(2) 8.6(2.21900.5) Description (partial) Symptom: --Refresh Upgrade to 8.6.2.21900-5 fails in Install DB Component . --Upgrade gets stuck at 57% . Conditions: --Upgrade to 8.6.2.21900-5 -- Subnet mask for server must be created as 255.255.255.000 during installation, it can be verified from Install / Upgrade Logs : +++++++++++++++++++++++++++++++++++++++++++++++++++ 08/24/2012 19:37:14 InstallWizard|validateIpAddr: 255.255.255.000|
Us Facebook Twitter Google + LinkedIn Newsletter Instagram YouTube DirectoryNetwork InfrastructureWAN, Routing and Switching LAN, Switching and Routing Network Management Remote Access Optical Networking Getting Started with LANs IPv6 Integration and Transition EEM Scripting Other Subjects SecurityVPN Security Management Firewalling Intrusion Prevention Systems/IDS AAA, Identity and NAC Physical Security MARS Email Security Web Security Other Subjects Service ProvidersMetro MPLS Voice Over IP XR OS and Platforms Video Other Subjects Collaboration, Voice and VideoIP https://quickview.cloudapps.cisco.com/quickview/bug/CSCub72346 Telephony Video Over IP Jabber Clients Unified Communications Applications TelePresence Digital Media System Contact Center Conferencing UC Migrations Other Subjects Wireless - MobilitySecurity and Network Management Wireless IP Voice and Video Getting Started with Wireless WLCCA Other Subjects ServicesCisco ServiceGrid Connected Analytics Smart Call Home Smart Net Total Care Operations https://supportforums.cisco.com/discussion/12334191/upgrade-cucm-1051-fails Exchange Mobile ApplicationsCisco Proximity Cisco Technical Support Online Tools and ResourcesCisco Bug Discussions Technical Documentation Ideas Cisco CLI Analyzer Support Community Help Data CenterApplication Centric Infrastructure Application Networking Intelligent Automation Server Networking Storage Networking Unified Computing Wide Area Application Services (WAAS) Other Subjects Small BusinessNetwork Storage Routers Security Surveillance Switches Voice and Conferencing Wireless Solutions and ArchitecturesBorderless Networks Collaboration Cisco User GroupsSeattle Cisco User Group (SEACUG) Silicon Valley Cisco User Group (SVCUG) Southern California Cisco User Group (SCCUG) Cisco Certifications Cisco.com Idea Center Cisco Cafe Expert CornerTop Contributors Leaderboards Cisco Live! Events Events Community CornerAwards & Recognition Behind the Scenes Feedback Forum Cisco Certifications Cisco Press Café Cisco On Demand Support & Downloads Community Resources Security Alerts Security Alerts News News Video Cisco Support YouTube Cisco YouTube Blogs Technical Documentation Cisco Products Products Services Services Solutions Solutions Global Support Numbers Cisco Support Community Directory Network Infrastructure WAN, Routing
( 6 ), IM&P ( 5 ), Jabber ( 4 ), Presence ( 4 ), SSO, Unity Collaboration SSO After configuring SSO in our https://ccie45333.wordpress.com/tag/cisco/ internal Collaboration-environment, a few things to remember; Cross-check time-sync (!!!). It costed me quite some time in troubleshooting when expecting that the AD was synchronized. Don't do that. Seriously. Be careful with the Claim Rules. The documentation may be misleading in terms of the namequalifier, probably due to versioning differences between ADFS 2 and 3. Claim Rules should consist of the following; 1.) appmanager.sh internal Send LDAP Attributes as Claims, store Active Directory and map SAM-Account-Name to uid. 2.) Send Claims Using a Custom Rule, paste the following; c:[Type == "http://schemas.microsoft.com/ws/2008/06/identity/claims/windowsaccountname"] => issue(Type = "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier", Issuer = c.Issuer, OriginalIssuer = c.OriginalIssuer, Value = c.Value, ValueType = c.ValueType, Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/format"] = "urn:oasis:names:tc:SAML:2.0:nameid-format:transient", Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/namequalifier"] = "Note1*", Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/spnamequalifier"] = "Note2*"); Note1) EntityID of the ADFS (pull from entityID in FederationMetaData.xml, i.e. http://fqdn/adfs/services/trust for appmanager.sh internal error ADFS 3.0) Note2) EntityID of the Collaboration-host (pull from entityID in SPMetadata_fqdn.xml, i.e. fqdn) …also, be careful with linebreaks when copying the custom rule, it should just be one line. If needed to debug, the option to modify log-level for SAML is missing in CCMService. Use CLI-command to change level; admin:set samltrace level DEBUG Thanks to CSCul45929 for pointing this out. Next step will be to convince our Netscaler to become an ADFS-proxy and deploy this to the Expressway as well.🙂 Share this:Click to share on Twitter (Opens in new window)Click to share on LinkedIn (Opens in new window)Share on Facebook (Opens in new window)Like this:Like Loading... mlundbom 7:42 pm on July 6, 2015 Tags: Cisco, CUP ( 4 ), Database ( 2 ), IM&P ( 5 ), Jabber ( 4 ), Presence ( 4 ) Managed File Transfer inIM&P From getting MFT to work in IM&P and Jabber, I've discovered that it is really important to configure everything in the right order. DO have the database completely configured before attempting to perform the configuration within cupadmin (See my previous blog-post for notes on Oracle-configuration). Prepare the