After the Cisco CallManager publisher server is rebuilt and restored, call forwarding set and unset does not show the correct status due to some hardware issues. The Cisco CallManager and Computer Telephony Integration (CTI) Manager services fail to start or remain started.
The Database Layer Monitor traces reveal Open Database Connectivity (ODBC) logon failures by the Cisco CallManager system account CCMServiceRW. Also, the kDbConnectionFailed - Database connection failed error is seen in the error application log.
Missing specific permissions to view and edit the databases can cause the ODBC logon failures for the Windows user accounts created for Cisco CallManager services.
View the user permissions through the Structured Query Language (SQL) Enterprise Manager in either of these two ways, in order to identify any permission corruption:
Path 1 -Go to Server > Database > Users Path 2 - Go to Server > Security > Logins
Note: The user permission information provided by these two paths are identical.
In order to resolve this issue, delete all users from both paths and re-add the users. Then, grant permissions per default settings through a reference server. Perform these steps:
Open the SQL Enterprise Manager, and expand the SQL Server Group > SQL Server > Databases > SQL database > Users, and delete the users in question.
Open the SQL Enterprise Manager, and expand the SQL Server Group > SQL Server > Security > Logins, and delete the users in question.
Proceed to Add users.
Open the SQL Enterprise Manager, and expand the SQL Server Group > SQL server > Security > Logins, and right-click on Logins, and choose New Login.
Click the button next to Name, and search and select the Windows user account. Leave the rest as defaults (Windows Authentication, Domain field blank, Database is master, and Language).
Click and select the Database Access tab, then click the appropriate Permit box for the database to which this user must have permissions granted.
Select the roles in the Permit in Database Role window.
Click OK to close.
Open the SQL Enterprise Manager, and expand the SQL Server Group, the SQL server, and verify the permissions granted to the user just added.
Also, make sure that there are no broken connections between the subscriber and the publisher.