I have tried to install ICM on Lab machine and every time I received exactly the same error, when I was attempting to run administration workstation's configuration manager :" Please reload AWDB. Run Initialize Local Database" When I was trying to do as pointed, Programm "Initialize Local Database" hangs...
Yes, I did so when installing SQL : "Collation to Latin1-General and the search order to Binary"
And, I found yet another error concerning SQL:
"From Event Viewer - Warning:
SQL Server User Error: 911, State 1, Severity: 16, Message: Could not locate entry in sysdatabases for database 'ic_sideA'. No entry found with that name. Make sure that the name is entered correctly. "
On this forum I found that this may be bug "CSCma27239" May be you know what is it? I have not access to bug's information on cisco.com
Did you create the Central db using the ICMDBA tool? The AWDB is created for you by Setup (though it is still very small - it often needs to be expanded), but none of the other dbs are - sideA/B or HDS. These must be created manually with ICMDBA.
It is not really required to use the HDS if this is a lab environment.
When you open ICMDBA, expand the tree and select the Logger component. By default, there is nothing under it. With the Logger selected, you can right-click and select "Create" - this will bring up the familiar dialog you used to expand the AWDB. Do this to create the Logger database and you should at least be able to get up and running.
The problem was really, that I didn't create Logger's
Now everything works, but may I ask another question?
Is there any way to change size of configuration manager's windows? The problem is that I run win2000 server in VMware program on notebook and there only 640*480 screen's resolution and so I can't see entire
configuration manager's window (I haven't video card drivers for my note that work inside VMware...).
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...