Showing results for 
Search instead for 
Did you mean: 

CCMAdmin login fails after an upgrade from Cisco CallManager 5.0(1) to 5.0(2), and then a switch to version 5.0(1)


Core Issue

This is a known problem. For more information, refer to Cisco bug ID CSCsd38232.

The Java database connection configuration is written into the /tmp/.bindings file, and is cleaned out by a scheduled process each day.

A new .bindings file is recreated, but with incorrect permissions, it  blocks the ability to update and delete privileges.


This is the workaround for this issue:

  1. Call the Cisco Technical Assistance Center (TAC) to obtain access and perform a platform login (using Secure Shell [SSH]) with the remote access user account.

  2. Modify the permissions to the file named /tmp/bindings. 

  3. Logout, and login again as the administrator (using SSH).

  4. Issue the utils system restart command to restart the Cisco CallManager server.

For a permanent fix to this problem, upgrade the CCM to 5.0(2)1000-3 by visiting:

Software Download-Cisco Unified CallManager Version 5.0

The platform login (also known as the Command Line Interface [CLI]) for the remote access user account can only be generated by Cisco developers at this time. Cisco TAC engineers have to contact the IP Communications Business Unit  (IPCBU) for additional instructions.

Content for Community-Ad