Unable to start ICM Configuration Manager in ICM 8.5

Question

Hi,
We are in the midst of setting the unified contact center 8.5.2 on windows server 2008 R2.
We are using CUCM 8.5. As for the icm 8.5.2, the servers are as follows:
1. Router A & logger A & CMPG A & VRU PG A on 1 mcs 7845
2. Router B & logger B & CMPG B & VRU PG B on 1 mcs 7845
3. Administration/ Data server with HDS on 1 mcs 7845
All servers are running ms SQL server 2005 with sp2. When the instance and all components
were created, I could start all services on these 3 servers. But when I tried to open the
Configuration Manager, it showed an error "(-9959) The AWDB needs to be reloaded before
any operations may be attempted. Please run Initialize Local Database."
Then I tried to start the process in the Initialize Local Database windows, it threw out
another error saying "the pipe has ended" following by another message "the process is
completed".
Then I tried o start the configuration manager or the script editor again, the same
problem still persists. I tried to recreate the Administration server & data server component again, but it
doesn't help. I also tried to delete the AWDB but it said the database in current in use.
Did I miss out any important steps here? Appreciate your help to rectify this issue ASAP.
I also noticed version 8.x and 7.5 is so much different. How do I check the each icm
process like the process window in version 7.5?
Thanks & regards,
Eric

Answer 1

Geoff is correct...and I would agree with David as well.
I will try to be more specific and answer both questions:
On Windows Server 2003, SQL Server 2005 Service Pack 3 or higher is the requirement.
On Windows Server 2008 R2, SQL Server 2005 Service Pack 4 or higher is the requirement.
The validation should be enforced in ICM Installer 8.0(1a).
Specifically, if SQL Server 2005 is detected on a machine and if the service pack is not minimally correct, when ICMCCInstaller version 8.0(1a) is run, the following severe error will be displayed to the user as well as being logged in the ICMInstall.log:
"[Error] Microsoft SQL Server 2005 installation does not have a high enough service pack.  Cisco Unified ICM/Contact Center Enterprise & Hosted requires Microsoft SQL Server 2005 with Service Pack or greater."
where is 3 when running on Windows Server 2003 and 4 when running on Windows Server 2008 R2.
didn't you see this message when installing it?
The 8.0(1a) full installer contains the same file set as the 8.0(1) FCS version. The difference is in the InstallShield installer, which allows customers to install the product on Windows 2003 or Windows Server 2008 R2 (whereas the FCS version did not allow W2k8). Release 8.0(1a) completely replaces 8.0(1). End user documentation still just refers to 8.0(1) (i.e. you will not see reference to 8.0(1a)).
Note: 8.0(1a) does not have the complete working solution for Windows Server 2008 R2. You must apply the 8.5(2) or higher maintenance release in addition to 8.0(1a) to have a working solution. The MR contains bug fixes specific to Windows Server 2008 R2.
Now, how to see processes...well...say goodbye to that one as it is used to be
No UCCE Process Windows
In Windows Server 2008 R2, session 0, where Windows services run, has no desktop. No user can login to session 0 as previously known as console. And since there is no desktop, no visible object of any type can be displayed. Among such objects are the UCCE process windows. Customers and TAC have long relied on the process windows to diagnose the system and provide a feel good indicator that the system is running. The title bars of some windows are critical for determining things like which side is active. The tracing provided in some windows sometimes made it easier to diagnose or monitor certain conditions, especially in reproduction during a maintenance window. The goal was to make this same information available in another way.
Diagnostic Framework Portico: Process Status Info (title bar)
The status of the UCCE processes is used to be shown in the title bar of the corresponding process window.  Since all UCCE process windows no longer show up in the taskbar, users are not able to use the process windows to check the status of the UCCE processes anymore.  As a result, process status information was added to the Diagnostic Framework Portico.
The Diagnostic Framework Portico is a web-based GUI that list the current running UCCE processes.
You can also access the Diagnostic Framework Portico by choosing All Programs > Cisco Unified CCE Tools > Diagnostic Framework Portico.
Note that the process status information is now displayed.  Additionally status changes and low uptime is highlighted. Uptime will be red if uptime is less than 10 minutes and yellow less than 30 minutes. These will also be underlined. This will help to identify cycling services. Status changes will be highlighted and made bold when a process's status changes. This highlighting will last for 10 minutes or until the status returns to its original state. Also as compared to the original page, the vertical space has been used more efficiently to fit more processes on a single page without scrolling. There is also a refresh checkbox which when checked will refresh the page every 5 seconds. It is checked by default.
EMSMon: Process EMS Messages
In Release 8.5(2), for Windows 2008, process windows for ICM processes are no longer available. The title bar status information is available in the Diagnostic Portico; however, real time data does not appear there. To address this, Cisco recommends that partners and TAC use EMSMON as a replacement.
EMSMON has been with UCCE/ICM since the earliest versions of ICM. EMSMON displays logged messages from a process as they are logged. It displays the same content as the former process windows. The two exceptions are the title bar and stdout and stderr output. Events are logged for all processes and appear in EMSMON. However, rare error condition messages (shelled processes, and so on) that go to stdout do not appear in an EMSMON window.
You can start EMSMON while the process is up or down. If the process is down, EMSMON displays messages from the process when the process starts. EMSMON does not end when the process ends. To end EMSMON, press CTRL+C or close the window.
Note: To prevent ICM processes from queueing too many EMSMON messages and exceeding the system memory, ICM processes may drop queued EMSMON messages. If this happens, EMSMON clients display a message indicating one of the clients fell behind and there is a gap. This message is also logged in the processes event log. This can happen if a particular EMSMON client is too slow or paused by quick edit or ctrl/s for example.
How to run EMSMON
EMSMON has the same parameters as procmon:
*Instance/Customer Node process,[process] [System]
The System parameter is optional. You can use it to run EMSMON from a machine remote from where the process is running.
For example, if the Instance/Customer Node is ?ucce and you want to monitor the JTAPI gateway on PG1A, type the following:
EMSMON ucce PG1A jgw1
If you are remote and the machine name is UCCEPG1A, type:
EMSMON ucce PG1A jgw1 UCCEPG1A
Note: A trust relationship must exist between the two machines. (Use the “NET USE” command or something similar).
The following list includes some EMSMON facts:
EMSMON (like DUMPLOG) can monitor multiple processes. The use of EMSMON to monitor multiple processes is not discussed here.
A single EMSMON can monitor multiple processes and merge their output (for example, (jgw1 and pim1).
Multiple EMSMONs can watch a single process. For example, you can have a local (on box) EMSMON and a remote EMSMON. Cisco recommends that you use one EMSMON only for each process.
To reserve system resources for ICM processes, it is recommended that you run the EMSMON client on a remote machine that does not host ICM processes. For example, running EMSMON client on side A of a PG and connecting it to a process on side B of a PG is not recommended.
To run EMSMON on a remote machine, copy emsmon.exe, emsmon.pdb, and icrmessages.dll from c:\icm\bin and place them on a remote machine.
You can cut and paste just as in the command windows but it is safer in EMSMON.
You can start EMSMON at anytime, even when the process is not running. (You can have a batch file on a machine to start sessions.)
For history (events prior to EMSMON starting), use DUMPLOG.
To change the number of lines each EMSMON window retains, modify the command window parameters.
With EMSMON, you can have one local connection and five remote connections per process. When the number of connections is exceeded, the oldest session is disconnected with the following message ?You are being disconnected because another user has connected to this named pipe.
If your system is running a heavy call load, your EMSMON connections may disconnect and the following message appears: ? You are being disconnected because the system is running a heavy call load; this connection may impact the performance of the system. It is recommended that you do not reconnect your EMSMON sessions until your system returns to a normal call load
Thanks,
Goran
Please rate with 5 stars if you find this post useful.