Does anyone know if this service can be deactivated or stopped? Not finding much info on cisco.com on what it is used for or if it is crucial but am seeing it crash often on a few different 10.5 clusters.
The bug is not fixed yet per the bug below,
SOAP Diagnostic Portal Database Service Crash on CUCM
SOAP - Diagnostic Portal Database Service crash
CUCM version 10.0.1.10000-12
Even though the service stopped abruptly, service manager will restart the service automatically. No manual work arounds are required.
Further Problem Description:
We have same problem on 9.1 version also.... is there any bug
114608863 - Problem alert -/SysLog is Critical
Additional Info - Aug 05 2015 12:12:13.705 UTC : %UC_RTMT-2-RTMT_ALERT: %[Name=SyslogSeverityMatchFound][Detail=This a Syslog severity critical alert .#012#012Please do the needfull for resolution.#012#012#012#012 At Wed Aug 05 08:12:13 EDT 2015 on node 10.3.8.10, the following SyslogSeverityMatchFound events generated: #012SeverityMatch : Critical#012MatchedEvent : Aug 5 08:11:41 local7 2 : 635:: Aug 05 2015 12:11:41.345 UTC : %UC_SERVICEMANAGER-2-ServiceFailed: %[ServiceName=SOAP - Diagnostic Portal Database Service][Reason=Service stopped abruptly][AppID=Cisco Service Manager][ClusterID=][NodeID=NJPUB01]: Service terminated.#012AppID : Cisco Syslog Agent#012ClusterID : #012NodeID : #012 TimeStamp : Wed Aug 05 08:11:41 EDT 2015][App ID=Cisco AMC Service][Cluster ID=][Node ID=]: RTMT Alert
Do you know if this bug will also stop the SOAP Real-Time Service API's? I am experiencing the same issue, however with the SOAP Real-Time service.
%UC_SERVICEMANAGER-2-ServiceFailed: %[ServiceName=SOAP -Real-Time Service APIs][Reason=Service stopped abruptly] %UC_SERVICEMANAGER-2-ServiceFailed: %[ServiceName=SOAP -Real-Time Service APIs][Reason=Service stopped abruptly]
Running CUCM version - 10.5.2.10000-5
Any ideas or suggestions will be greatly appreciated.
Thanks in advance!
I've hit this on one of my subscribers. Just stop the service. That stops CUCM from trying to continually restart it. You'll have to stop the service everytime your restart the affected server, though.