Technical References

During initialization, the Router process rejects the configuration data load from logger.
Message:
Cause:
This occurs because the Logger is busy and does not send a heartbeat to the Router. The Router
waits for the heartbeat for 2 minutes (the default interval), doesn't receive a heartbeat, and finally
rejects the data.
Action:
Increase the following registry key value:
Router\CurrentVersion\Configuration\Config\LargeTableTimeout
Logger Setup Fails
Symptom:
Logger Setup fails with the following message:
Message:
“Unable to connect to the database”
Cause:
Microsoft SQL Server Client Network Utility and/or Server Network Utility is specified
incorrectly.
Action:
Perform the following steps:
Open “Client Network Utility” from Microsoft SQL Server folder. Open General tab "enabled
protocols by order“. Make sure TCP/IP does not appear prior to Named Pipe.
Open “Client Network Utility” from Microsoft SQL Server folder. Open "Server alias
configurations“. Make sure there is not an entry for "." for TCP/IP or Named Pipe or any other
protocols.
Open "Server Network Utility” from Microsoft SQL Server folder. Open "Enabled protocols“.
Make sure there is an entry for “Named Pipes”.
Logger Initialization Assert
Symptom:
During Logger initialization, the process asserts with the following message:
Database Schema Handbook Cisco ICM/IPCC Enterprise & Hosted Editions 7.2(2)
517
Chapter 6: ICM/IPCC Database Troubleshooting