topic this error message generally in Unified Communications Infrastructure

IM & Presence Installation Issue

Jefferson Islan Silva — Tue, 19 Mar 2019 16:42:42 GMT

I'm trying to install the IM & Presence version 10.5.(2) and getting the following error message after the installation.

" A Cisco DB may have encountered a known issue - If services are not starting please run 'utils service restart Service Manager'"

Do you have any idea how to fix that?

Hi Jefferson,Is it the first

Manish Gogna — Thu, 18 Jun 2015 01:54:03 GMT

Hi Jefferson,

Is it the first node in the IM&P cluster?

Are the correct specs configured as per OVA guidelines below?

http://docwiki.cisco.com/wiki/Virtualization_for_Unified_CM_IM_and_Presence

Please ensure the NTP server is working correctly and reachable from IM&P server.

HTH

Manish

Hi Jeff,

asenapat — Wed, 20 Apr 2016 08:44:54 GMT

Hi Jeff,

I am having same issue and encountered same error when I am trying to login to IMP via CLI.

Please let me know what was the issue and how it got fixed.

Hello,

neil wooloff — Thu, 18 Aug 2016 20:39:53 GMT

Hello,

I am getting this message sometimes when access the cli.

checked and all services are started ok

ntp & dns all good

built using a good md5 checked ova also

Did you get a fix or indication of what is causing this?

Neil

this error message generally

Varundeep Chhatwal — Fri, 19 Aug 2016 10:30:15 GMT

this error message generally comes when server is unable to read its own database for some reason. if anything is wrong in database then services refuse to start. i suggest you to check your db replication for cups cluster.

Hello,

neil wooloff — Thu, 25 Aug 2016 15:46:27 GMT

Hello,

I have a single cucm & single imp and repl was all good.

i did a clean shutdown and power on and all came up ok.

i also installed the vmtools.cop.sgn file but they still not register as installed, so think a clean buil may be in order.

Thanks for confirming what it does though.

Neil

Hi Manish,

fragni_cisco — Thu, 30 Mar 2017 18:55:10 GMT

Hi Manish,

Thank you for your tip. I faced up the same db issue and the solution was to set up correctly the NTP.