Cisco Self Care Portal Login Username or Password Is Incorrect Updated FREE
Cisco Self Care Portal Login Username or Password Is Incorrect
This certificate describes how the Jabber Log in and how to troubleshoot information technology when the login fails on an Internal or corporate Network.
Jabber Log in comprises of two stages namely Cisco Unified Communications Manager server (CUCM) Log in and IM and Presence server (IM&P) Log in.
- CUCM Log in involves Service discovery to place the CUCM server to which Jabber must log in.
- Jabber user Hallmark with CUCM to think the Service profile details which contains IMP server, Voicemail, Conferencing, CTI server details and also Device Configuration file for Phone services.
- In one case the CUCM Log in is successful, Jabber logs in to the IM&P server to authenticate and recollect the contact list and other IM services.
- The IM&P Log in has two stages namely: SOAP Log in which deals with user authentication, and and so XMPP Log in which deals with XMPP session creation and Stream Management.
Primarily, clear the cache on the PC and collect the clean Jabber Problem Report (PRT). These are the steps to practise the same
Step 1. Sign out and leave the Jabber application.
Step 2. Delete all the logs located at
%AppData%\Local\Cisco\Unified Communications\Jabber\
%AppData%\Roaming\Cisco\Unified Communications\Jabber\
Step three. Restart Jabber and recreate the trouble.
Step four. Collect the Problem study (From the Jabber Help card, select Written report a problem option to launch trouble reporting tool and follow instructions).
Follow these links:
- How to collect a Jabber Trouble Report
- How to collect logs from Expressway (When Jabber is over MRA)
Keywords to Search in Logs
IMPStackCap::Log in::OnLog inError
ServiceDiscoveryHandlerResult
@CupSoapCli: log in loving cup succeeds - shows when the Lather log in was successful.
[CTriTPConnectionClient::OnConnectSuccess] - @XmppSDK: - shows when the XMPP log in was successful.
LERR - shows the Log in Errors when the Jabber fails to log in to the IM&P Server.
Stage 1. CUCM Service Discovery
| Mistake on screen | Cause | What to check in Jabber log |
| Cannot find your services automatically. Click Advanced settings to ready up manually | This error is seen when the_cisco-uds or _cuplog in SRV records are non configured in the DNS server | csf::dns::mapFromWindowsDNSResult |
Sample Log Snippet
017-03-xix 17:55:00,422 WARN [0x000050ac] [src\dnsutils\win32\win32DnsUtils.cpp(52)] [csf.dns] [csf::dns::mapFromWindowsDNSResult] - *-----* DNS query _cisco-uds._tcp.appslab.com. has failed : DNS name does non exist. (9003).2017-03-19 17:55:00,438 WARN [0x000050ac] [src\dnsutils\win32\win32DnsUtils.cpp(52)] [csf.dns] [csf::dns::mapFromWindowsDNSResult] - *-----* DNS query _cuplogin._tcp.appslab.com. has failed: DNS proper name does not exist. (9003).
Steps to Resolve
Step ane. Get-go the command prompt (on a Windows Client) so enter nslookup.
Stride 2. Next ready the query type to SRV
set blazon = SRV
Pace 3. After that insert the SRV tape we demand to check
_cisco-uds._tcp.example.com
Step 4. This returns the DNS A records which betoken to the CUCM servers. This is an example of the Successful _cisco-uds SRV record. If no records are returned, contact your DNS administrator to configure the SRV records
| Error on screen | Cause | What to check in Jabber log |
| Cannot find your services automatically. Click Avant-garde settings to set upward manually | This error is seen when the Jabber is unable to call up the UDS or TFTP Servers to assemble its log in information and configuration settings. | HTTP response lawmaking 503 for request #29 to https://cucm.domain:8443/cucm-uds/ HTTP response code 503 for request #29 to https://cucm.domain:6972/ |
Steps to Resolve
Step 1. Validate that the CUCM nodes configured equally TFTP Servers are up and running.
Step two.Restart these services on all the CUCM nodes.
- Cisco TFTP
- Cisco UDS Service
Stage 2. CUCM User Authentication
| Error on screen | Cause | What to check in Jabber log |
| Your username or password is non correct | This error is seen when the credentials entered is wrong or the user is locked in CUCM/LDAP | "FAILED_UCM90_AUTHENTICATION" |
Sample Log Snippet
2017-01-09 08:59:10,652 INFO [0x00001740] [vices\impl\DiscoveryHandlerImpl.cpp(460)] [service-discovery] [CSFUnified::DiscoveryHandlerImpl::evaluateServiceDiscoveryResult] - ServiceDiscoveryHandlerResult return code FAILED_UCM90_AUTHENTICATION Steps to Resolve
Footstep i. Ensure that the User you endeavour to log in is configured as an enduser in CUCM. Navigate to CUCM Administration > Enduser page.
Step 2. Verify if credentials are correct and the user is active. Log in to the CUCM Cocky-care Portal. This image refers to the scenario where the LDAP is unable to authenticate the user either because the user is not a valid user or the password supplied is wrong.
Footstep 3. If this effect is seen for all users you need to verify if the LDAP synchronisation and LDAP Authentication settings on CUCM Administration > Arrangement > LDAP is correct.
Tip: From the LDAP Server perspective, ensure that theaccount is not locked, that thepasswords are not expired and that all theusers are synchronized with the CUCM server.
| Error on screen | Cause | What to cheque in Jabber log |
| Cannot communicate with the server | Jabber is unable to resolve/achieve the CUCM FQDN/HOSTNAME that it received during the Service discovery | "FAILED_UCM90_CONNECTION" |
Sample Log Snippet
2017-08-28 12:04:00,282 INFO [0x00004290] [vices\impl\DiscoveryHandlerImpl.cpp(452)] [service-discovery] [CSFUnified::DiscoveryHandlerImpl::evaluateServiceDiscoveryResult] - ServiceDiscoveryHandlerResult render code FAILED_UCM90_CONNECTION Steps to Resolve
Stride 1. Examination if y'all are able to open this URL in the browser on the PC https://<CUCM IP/FQDN> :8443/cucm-uds/version
Unsuccessful
Successful
Step 2. If the response is unsuccessful, verify if the DNS is configured correctly to resolve them and also if no Network Elements like Firewall/ASA block the port 8443.
Step 3. This URL must be tested for all CUCM Servers in the cluster. In guild to know the list of Servers, navigate to CUCM Administration > Arrangement > Server.
| Fault on screen | Crusade | What to check in Jabber log |
| Cannot communicate with the server | This error is seen when the userid entered in Jabber does not match with the userid configured in CUCM | "FAILED_USER_LOOKUP" |
Sample Log Snippet
2016-08-18 13:14:49,943 INFO [0x000036e4] [vices\impl\DiscoveryHandlerImpl.cpp(367)] [service-discovery] [DiscoveryHandlerImpl::evaluateServiceDiscoveryResult] - ServiceDiscoveryHandlerResult render code FAILED_USER_LOOKUP Steps to Resolve
Footstep 1. Test if you are able to open this URL in the browser on the PC https://CUCM:8443/cucm-uds/clusterUser?username=<userid>
Step 2. Check if the userid that is entered in Jabber matches the userid on CUCM Finish-user page.
Tip: Jabber has UPN discovery enabled by default and hence become the userid prepopulated from the LDAP UPN field. Bank check if UPN is the same as configured in CUCM, if you need to disable UPN discovery,set UPN_DISCOVERY_ENABLED=false during installation
Stage 3. SOAP Log in (IM and Presence Log in)
| Error on screen | Cause | What to bank check in Jabber log |
| Your username or password is not correct | This error is caused due to user Authentication failure | "LERR_CUP_AUTH" |
Sample Log Snippet
2017-01-14 15:55:09,615 INFO [0x00000dc0] [ts\adapters\imp\components\Login.cpp(99)] [imp.service] [IMPStackCap::Login::OnLoginError] - ****************************************************************
2017-01-fourteen 15:55:09,615 INFO [0x00000dc0] [s\adapters\imp\components\Login.cpp(100)] [imp.service] [IMPStackCap::Login::OnLoginError] - OnLoginError: (data=0) LERR_CUP_AUTH <12>:
201-01-xiv xv:55:09,615 INFO [0x00000dc0] [s\adapters\imp\components\Login.cpp(101)] [imp.service] [IMPStackCap::Login::OnLoginError] - **************************************************************** Steps to Resolve
Stride 1. Bank check if the user is assigned to a Presence node and at that place are no duplicates for the user (IM and presence Administration > Diagnostics > System troubleshooter).
Step ii. Check if the High Availability (HA) state is Normal and no Failover has occurred. If you have tried to assign the user during an aberrant HA state, Users are not assigned to any IMP node and log in fails and at present you need to recover the HA state first and re-assign the user.
Pace 3. Ensure that the credentials are valid.
- In the case of an LDAP user, verify if the user is able to log in to the CUCM Selfcare portal.
- If ccmenduser page log in fails, check the LDAP Hallmark settings in CUCM and also verify the aforementioned settings are replicated to IMP
run sql select * from ldapauthentication
run sql select * from ldapauthenticationhost - Bank check if the business relationship is non locked in LDAP
- If the user was recently enabled for Presence, restart the Cisco Sync Agent service on IMP Publisher.
Stride four. Check the server has high TOMCAT CPU consumption
- bear witness process load
- utils diagnose test
Step 5. Set these services log to DEBUG and and then recreate the Log in effect and collect the logs
- Client Profile Agent
- Cisco Tomcat
- Event Viewer-Application Log
- Event Viewer-Organization Log
| Error on screen | Cause | What to check in Jabber log |
| Invalid Credentials | This fault is acquired when the user is not active or in the database. | LERR_CUP_AUTH <10> |
Sample Log Snippet
[IMPServices] [CSFUnified::IMPStackCap::Log in::OnLog inError] - ****************************************************************
[IMPServices] [CSFUnified::IMPStackCap::Log in::OnLog inError] - OnLog inError: LERR_CUP_AUTH <10>:
[IMPServices] [CSFUnified::IMPStackCap::Log in::OnLog inError] - ****************************************************************
[http-bio-443-exec-15] handlers.Log inHandlerAbstract - preLog in:PRELOGIN reasoncode=FAILURE. User either non CUP licensed or not found in database.
Tip: For this error, it is besides recommended to take hold of the Cisco Tomcat logs from the CUCM and IM&P servers.
From the Cisco Tomcat logs
2019-10-27 eighteen:33:forty,373 DEBUG [http-bio-443-exec-5] impl.LDAPHostnameVerifier - check : inside check with X509 cert
2019-10-27 xviii:33:xl,373 DEBUG [http-bio-443-exec-5] impl.Certificates - getCNs :
2019-ten-27 18:33:40,373 DEBUG [http-bio-443-exec-5] impl.LDAPHostnameVerifier - check : cns = [ldap.ciscolab.com]
2019-10-27 18:33:40,373 DEBUG [http-bio-443-exec-5] impl.Certificates - getDNSSubjectAlts :
2019-10-27 18:33:40,374 DEBUG [http-bio-443-exec-5] impl.LDAPHostnameVerifier - check : subjectAlts = [ldap.ciscolab.com, ldap2.ciscolab.com]
2019-x-27 eighteen:33:twoscore,374 ERROR [http-bio-443-exec-5] impl.AuthenticationLDAP - verifyHostName:Exception.javax.net.ssl.SSLPeerUnverifiedException: hostname of the server 'ldapdc.ciscolab.com' does not match the hostname in the server's certificate.
2019-10-27 18:33:xl,374 DEBUG [http-bio-443-exec-five] impl.AuthenticationLDAP - value of hostnameverifiedfalse
2019-x-27 eighteen:33:twoscore,374 INFO [http-bio-443-exec-5] impl.AuthenticationLDAP - verifyHostName: Endmost LDAP socket
Steps to Resolve
Two situations are encountered here if the Cisco Tomcat logs do not prove whatever document fault, this requires to exist validated.
Step 1. Validate that the user is associated with an IM&P server
- Navigate to the CUCM Assistants webpage > User Management >User Management > Assign Presence Users > Look for the userid and Click Find
Stride ii. If the user is associated with an IM&P server, bounce the user from the Home Node cluster
- Navigate to the CUCM Assistants webpage > User Direction > End User > Expect for the end-user and Click Find> UnderService Settings, uncheck theHome Cluster checkbox> Click Relieve> checktheHome Cluster checkbox andClick Save
In instance the Cisco Tomcat logs show the error from the Snippet previously showed, perform these steps:
Step 1. Confirm if the Cisco Jabber is configured to use Secure LDAP
Step ii. If Secure LDAP is in use, confirm the certificates' information associated with them like the Fully Qualified Domain Name (FQDN), Hostname and Common Proper name (CN).
Footstep 3. Validate how the CUCM and IM&P are configured, if with IP accost or FQDN, and compare that with the information contain within the certificate
- Navigate to the CUCM Administration webpage > Arrangement > Server
Step 4. If the servers are configured with IP accost and the LDAP certificates are configured with FQDN, the next control requires to be executed on all the CUCM and IM&P nodes
- utils ldap config ipaddr
- Or the definition of the servers requires to be changed equally FQDN. Follow the Alter CUCM Server Definition from IP Accost or Hostname to FQDN guide.
| Error on screen | Cause | What to check in Jabber log |
| Cannot communicate with the server | This fault is acquired due to Bug with IMDB or TCP connectivity to IMP | "LERR_CUP_UNREACHABLE" , "LERR_CUP_TIMEOUT" |
Sample Log Snippet
2017-11-08 16:03:20,051 DEBUG [0x00003a0c] [south\adapters\imp\components\Login.cpp(127)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - ************************************************
2017-xi-08 16:03:xx,051 INFO [0x00003a0c] [s\adapters\imp\components\Login.cpp(128)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - OnLoginError: LERR_CUP_UNREACHABLE
2017-11-08 16:03:20,051 DEBUG [0x00003a0c] [s\adapters\imp\components\Login.cpp(129)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - ************************************************* Steps to Resolve
Footstep 1. Check if IMP FQDN/Hostnames are resolvable from the client'due south PC.
Footstep 2. Check if y'all can open this URL in browser https://<IMP SERVER FQDN/IP>:8443/EPASSoap/service/v105
Successful
Unsuccessful
Pace 3. Verify that firewall/VPN does non block the connectivity to IMP server ( Port 8443,5222)
Footstep 4. Verify if this service runs in IMP server: Cisco Customer profile Agent
Step v. Fix these services log to DEBUG, recreate the Log in issue and and then collect the logs if the previous steps exercise not resolve the trouble.
- Cisco XCP Router
- Cisco XCP Connection Managing director
- Cisco XCP Authentication Service
- Client Contour Amanuensis
Tip: If the problem persists for just ane user, yous can try to unassign and re-assign the user for presence in CUCM. If it's a arrangement-wide problem, collect the logs and check the status of the services
| Error on screen | Cause | What to check in Jabber log |
| Cannot communicate with the server | Usually, this error is acquired due to Issues with IMDB | "LERR_CUP_INTERNAL_ERROR" |
Sample Log Snippet
2017-11-08 xvi:03:20,051 DEBUG [0x00003a0c] [s\adapters\imp\components\Login.cpp(127)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - ************************************************
2017-11-08 16:03:twenty,051 INFO [0x00003a0c] [s\adapters\imp\components\Login.cpp(128)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - OnLoginError: LERR_CUP_INTERNAL_ERROR
2017-11-08 sixteen:03:20,051 DEBUG [0x00003a0c] [due south\adapters\imp\components\Login.cpp(129)] [IMPServices] [CSFUnified::IMPStackCap::Login::OnLoginError] - ************************************************* Steps to Resolve
Stride 1. Perform Mandatory checks
Step two. Verify that these services are running in the IM&P server
- Cisco XCP Router
- Cisco XCP Connection Manager
- Cisco XCP Hallmark Service
- Cisco Log in datastore
Step 3. Bank check if this Field notice is applicable
Field Detect: FN - 64267 - Cisco Unified Communications Manager IM & Presence causes Cisco Jabber log in failures - Software Upgrade Recommended
Footstep iv. Set these services log to DEBUG, recreate the Log in issue and so collect the logs if the previous steps exercise non resolve the problem.
- Cisco XCP Router
- Cisco XCP Connection Director
- Cisco XCP Hallmark Service
- Client Profile Amanuensis
- Cisco Log in Datastore
- Event Viewer-Application Log
- Outcome Viewer-System Log
Step five. Reboot the cluster to recover the situation.
Phase 4. XMPP Log in (IM and Presence Log in)
| Error on screen | Cause | What to check in Jabber log |
| Cannot communicate with the server | Commonly seen when Jabber fails to connect over MRA and cannot found a TLS session with the IM&P | LERR_JABBER_AUTH <14>: Hallmark error with server due east.m. resource bind, TLS, create session or SASL error |
Sample Log Snippet
2019-05-03 15:19:32,225 DEBUG [0x0000000109732f80] [s/adapters/imp/components/Log in.cpp(128)] [IMPServices] [OnLog inError] - ****************************************************************
2019-05-03 15:19:32,225 INFO [0x0000000109732f80] [s/adapters/imp/components/Log in.cpp(129)] [IMPServices] [OnLog inError] - OnLog inError: LERR_JABBER_AUTH <14>: Authentication error with server eastward.k. resources bind, TLS, create session or SASL error
2019-05-03 15:xix:32,225 DEBUG [0x0000000109732f80] [due south/adapters/imp/components/Log in.cpp(130)] [IMPServices] [OnLog inError] - ****************************************************************
Steps to Resolve
Step 1. Check if port 5222 is opened between the IM&P servers and the Expressways.
Step 2. Verify if these services are running in the IM&P server and restart them once.
- Cisco XCP Router
- Cisco XCP Connection Manager
- Cisco XCP Authentication Service
Pace iii. Disable the High Availability from the CUCM Presence Back-up Groups.
Step 4. Restart theCisco XCP Router serviceon all the IM&P nodes, first with the IM&P Publisher and so in the Subscribers.
- utils service restart Cisco XCP Router Service
Step 5. Reenable the High Availability from the CUCM Presence Back-up Groups.
| Error on screen | Crusade | What to bank check in Jabber log |
| Cannot communicate with the server | Commonly seen when Jabber cannot create a session and bind itself in IMP server | LERR_JABBER_AUTH <17>: Hallmark error with server e.g. resources bind, TLS, create session or SASL mistake" |
Sample Log Snippet
2017-10-27 10:56:47,396 DEBUG [0x00007fff8b3d7340] [s/adapters/imp/components/Login.cpp(127)] [IMPServices] [OnLoginError] - ****************************************************************
2017-10-27 10:56:47,396 INFO [0x00007fff8b3d7340] [south/adapters/imp/components/Login.cpp(128)] [IMPServices] [OnLoginError] - OnLoginError: LERR_JABBER_AUTH <17>: Authentication error with server e.g. resource demark, TLS, create session or SASL fault
2017-ten-27 10:56:47,396 DEBUG [0x00007fff8b3d7340] [s/adapters/imp/components/Login.cpp(129)] [IMPServices] [OnLoginError] - **************************************************************** Steps to Resolve
Step ane. Check if the loving cup-xmpp Certificates are valid.
Step ii. Check if Port 5222 is open.
Footstep 3. Set up these services log to DEBUG so recreate the Log in effect and collect the logs before step iv if Root crusade to be identified as Reboot of the server is the only set known so far
- Cisco XCP Router
- Cisco XCP Connexion Manager
- Cisco XCP Authentication Service
- Client Contour Amanuensis
- Event Viewer-Application Log
- Event Viewer-System Log
Stride 4. Reboot the server to resolve the effect.
| Fault on screen | Crusade | What to check in Jabber log |
| Cannot communicate with the server | Seen when IMP is not resolvable or reachable due to Network issues like firewall | "LERR_JABBER_UNREACHABLE " |
Sample Log Snippet
2014-12-xv 12:07:31,600 INFO [0x00001670] [ts\adapters\imp\components\Login.cpp(96)] [imp.service] [IMPStackCap::Login::OnLoginError] - ****************************************************************
2014-12-15 12:07:31,600 INFO [0x00001670] [ts\adapters\imp\components\Login.cpp(97)] [imp.service] [IMPStackCap::Login::OnLoginError] - OnLoginError: (data=0) LERR_JABBER_UNREACHABLE <xvi>:
2014-12-xv 12:07:31,600 INFO [0x00001670] [ts\adapters\imp\components\Login.cpp(98)] [imp.service] [IMPStackCap::Login::OnLoginError] - **************************************************************** Steps to Resolve
Stride ane. Check if IMP FQDN/Hostnames are resolvable.
Stride 2. Verify that the firewall/VPN does non block the connectivity to the IM&P server ( Port 8443,5222).
Step three. Verify if these services are running in the IM&P server and restart them once.
- Cisco XCP Router
- Cisco XCP Connection Manager
- Cisco XCP Hallmark Service
Step 4. Perform Mandatory checks.
Stride five. Gear up these services log to DEBUG, recreate the Log in outcome and so collect the logs if the previous steps do non resolve the problem.
- Cisco XCP Router
- Cisco XCP Connexion Manager
- Cisco XCP Authentication Service
- Client Profile Amanuensis
- Issue Viewer-Application Log
- Event Viewer-Organization Log
Step 6. In case of all users experience the same error, a server Reboot tin be done for quick recovery.
| Mistake on screen | Cause | What to check in Jabber log |
| Cannot Sign in your account. Contact your ambassador. | Ordinarily seen when the Jabber is log in with SSO, either on-prem or over Expressways (Mobile Remote Access (MRA)) | "Log inErrortoErrorCode: 27 mapped to: UnknownLog inError " |
Sample Log Snippet
2020-03-12 19:55:01,283 DEBUG [0x000000010b71d800] [apters/imp/components/Log inUtils.cpp(96)] [IMPServices] [Log inErrortoErrorCode] - Log inErrortoErrorCode: 27 mapped to: UnknownLog inError
2020-03-12 xix:55:01,283 DEBUG [0x000000010b71d800] [isteners/Log inEventListenerImpl.cpp(148)] [IMPServices] [OnLog inError] - errCode: UnknownLog inError
2020-03-12 xix:55:01,283 INFO [0x000000016b61f000] [ers/imp/lifecycle/Log inExecutor.cpp(314)] [IMPServices] [signOn] - logged in using User ID: 35309769, failed
2020-03-12 19:55:01,478 INFO [0x000000010b71d800] [pp/tahiti/ui/log in/YLCLog inBaseVC.m(500)] [UI.Activeness.System] [- [YLCLog inBaseVC getPresenceErrorMessgaWithCode:] ] - Jabber log in failed and testify errorcode:200 string: Cannot Sign in your business relationship. Contact your administrator.
Steps to Resolve
Step 1. Validate that the user is assigned to the IM&P.
Step 2. Validate that the certificates are correctly exchanged betwixt the nodes and the Jaber.
Stride 3. Validate the OAuth Signing and Encryption keys are correctly configured on all the nodes. See this certificate under Verify section.
Pace 4. Perform Mandatory checks.
Step 5. Set these services log to DEBUG, recreate the Log in issue and then collect the logs if the previous steps exercise not resolve the trouble.
- Cisco XCP Router
- Cisco XCP Connection Managing director
- Cisco XCP Authentication Service
- Client Profile Agent
- Event Viewer-Awarding Log
- Event Viewer-System Log
- Cisco SSO
- Cisco Tomcat
- Cisco Tomcat Security
Step 1. Check if the user is assigned to a Presence node (navigate to IM and Presence Administration > System > Topology) and there are no duplicates for the user(navigate to IM and Presence Assistants > Diagnostics > System troubleshooter)
Step two. If High Availability is enabled, navigate to CUCM Assistants > Server > Presence Redundancy Group and check if they are in Normal land. This is the paradigm of how Normal state looks. For more than data about High Availability tin be found here.
Abnormal State
Note: These services are used by the Jabber to log in: Cisco Tomcat, Cisco Tomcat Security, Cisco Client Profile Agent, Cisco XCP Connection Manager, Cisco XCP Router and Cisco XCP Authentication.
Normal State
Pace 3. Check High Availability Replication status.
a.utils dbreplication runtimestate
If you encounter bug on the database replication, follow this link.
b.run pe sql ttlog in select count(*) from typesysreplication
or utils imdb_replication status ( x.5.2 SU2a and later)
The three datastores demand to showPASSED,and the control needs to be run on all the IM&P nodes, as sometimes on i node all the datastores' replication can bear witnessPassed, but on another node, it can testifyFailed.
The implications if the IMDB (In-memory Database) replication is not correct can imply that some or all the users are unable to log in or that their presence condition cannot exist shown correctly.
The steps to resolve the IMDB replication issues are:
Stride i. Disable the Loftier Availability (HA) for the IM&P Subcluster that is affected.
Step two. Cease the Cisco Presence Engine on all nodes
utils service stop Cisco Presence Engine
Step three.Verify all the Datastore Services are running: Cisco Log in Datastore, Cisco Route Datastore, Cisco Presence Datastore, Cisco SIP Registration Datastore.
utils service list
Step 4. Restart Cisco Config Agent on each node one at a time.
utils service restart Cisco Config Agent
Step 5. Start Cisco Presence Engine.
utils service outset Cisco Presence Engine
Footstep 6. Enable HA for the Sub-cluster.
Step 1 Choose Navigation > Unified serviceability > Trace > Configuration.
Step 2 From the Server driblet-downwards list, choose the server ( i.e IMP node) that runs the service for which you want to configure trace and so, click Become.
Step three From the Service Group drop-downwards list box, choose the service group for the service that you lot want to configure trace; then, click Go.
Step 4 From the Service driblet-downward list box, choose the service for which you want to configure trace; so, click Go.
Step v Check box 'Apply to All Nodes' and select the trace level to 'DEBUG'
Step half dozen To save your trace parameters configuration, click the Save button
For more than information on how to gear up trace levels refer to the Cisco Unified Serviceability Administration Guide.
Helpful videos:
- Configuring Service Trace levels
- Collect logs from the RTMT
| RTMT | Admin CLI |
|---|---|
| Cisco Client Contour Amanuensis | file go activelog tomcat/logs/epassoap/log4j/* |
| Cisco Log in Datastore | file get activelog epas/trace/imdb/sdi/ttlog in/ |
| Cisco Tomcat Security Logs | file become activelog tomcat/logs/security/log4j/* |
| Cisco XCP Authentication Service | file become activelog epas/trace/xcp/log/auth* |
| Cisco XCP Connection Manager | file get activelog epas/trace/xcp/log/client-cm-ane*.log |
| Cisco XCP Router | file get activelog epas/trace/xcp/log/rtr-jsm-one |
| Event Viewer-Application Log | file get activelog syslog/CiscoSyslog* |
| Event Viewer-System Log | file go activelog syslog/letters* |
Cisco Self Care Portal Login Username or Password Is Incorrect
DOWNLOAD HERE
Source: https://www.cisco.com/c/en/us/support/docs/unified-communications/jabber/212471-jabber-login.html
Posted by: abbyvervang.blogspot.com
Comments
Post a Comment