CIPC: Unable to initialize support for Cisco Emergency Responder

Unanswered Question
Mar 4th, 2010

Hi!

CUCM 7.1(3). Latest CIPC sw.Different OS :XP,Vista,Windows 7

Same error message each time when launching IPC: Unable to initialize support for cisco emergency responder.

It then registers and calls works fine.

Error msg:Unable to initalize support for CIsco Emergency Responder"

CER is not configured and we do not want it.

Howc can we avoid getting this error msg?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
William Bell Thu, 03/04/2010 - 11:44

You may be running into this defect, though the defect is only referring to Vista:

CSCsh89047  VISTA: Unable to initialize support for Cisco Emergency Responder

Symptom:

When loading CIPC 2.1.0.89 on Vista Enterprise error occurrs: 'Unable to initialize support for Cisco Emergency Responder. Please consult your system administrator'
CIPC doesn't load - it hangs in blue screen.

Vista Enterprise is installed on Vista enabled laptop (HP Compaq nx7400, 1GB RAM, 1.83GHZ). Vista is licensed. Tested with CCM 6.0.0.9901-109 and 5.0.3.9911-68

Conditions:n/a

Workaround:n/a

Further Problem Description:n/a

This defect is listed as fixed but the release is "pending".  Have you noticed a difference in behavior if you connect CIPC to the back of an IP versus connected the PC directly to a switch port (via your cube/office patch port of course)?  For CIPC to work with CER it needs to exchange CDP messages with the switch.  Typically, connecting to the phone will not allow that negotiation and may be what spawns the error message.   While annoying, this message is cosmetic and won't disrupt normal call processing.

Another defect that you may be running into is this one:

CSCef40483  CIPC: Cisco Emergency Responder fails to initialize if user not admin
Symptoms:
A message is prompted indicating that it is unable to initialize support for
Cisco Emergency Responder service at startup.

Conditions: When an Administrator installs the product without starting the application first.

Workaround: Administrator needs to run the application and configure the settings.

Now this bug is supposedly fixed in later releases (2.1.1 and later) so it may not be applicable.  Though, it probably isn't a bad idea to check the work around.  Sounds like you only need to start the application as an admin level user once to mitigate this defect.

HTH.

Regards,
Bill

Please remember to rate helpful posts.

aeriksson Thu, 03/04/2010 - 12:02

Hi! I have tried already to install CIPC when logged in as Admin, it is the same. As for how it is connected. This customer has only got CIPCs, no hardphones. They are using HP Procurve so we are running LLDP-MED instead of CDP. Can that be related then maybe?

david-lima Thu, 03/04/2010 - 14:48

Hi friend, did you try that:

To disable CDP:

Open registry editor - Run regedit

Get to  the key HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Communicator\  Add EnableCDP as a DWORD value.

Set its value to 0 (To enable it  later change the value to 1. By default, the key doesn't exist and the  default value is 1).

From:

https://supportforums.cisco.com/message/1172847#1172847

hth David

Vaijanath Sonvane Tue, 07/06/2010 - 09:11

Hi Bill,

We are also geting the same error message "Unable to initialize support for cisco emergency responder service. Please consult your system administrator" on Windows XP 64-bit OS. Currently we are using IPC verison 2.1.3. My client want to use the emergency server. They have CER is their network. Is there any solution on this?


-

Vaijanath

Actions

This Discussion