ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

SOI Manager not coming online after applying SO15850

book

Article ID: 207734

calendar_today

Updated On:

Products

CA Service Operations Insight (SOI)

Issue/Introduction

SOI Manager not coming online after applying SO15850

In the Manager Debug triage tests page, MANAGER BASE section have FAILED for

Type repository loaded

TopLevelService present 

 

In the soimgr-debug.log, see the following errors

2021-02-01 18:38:49,214 ERROR [localhost-startStop-1] ?.?(?)  - [Fatal Error] :4174:231: Invalid byte 3 of 3-byte UTF-8 sequence.

2021-02-01 18:38:51,608 ERROR [localhost-startStop-1] ?.?(?)  - [Fatal Error] usm-core-200907.xsd:4174:231: Invalid byte 3 of 3-byte UTF-8 sequence.

2021-02-01 18:38:54,343 ERROR [SOICAT] ?.?(?)  - [Fatal Error] :4174:231: Invalid byte 3 of 3-byte UTF-8 sequence.

2021-02-01 18:38:55,253 ERROR [SOICAT] ?.?(?)  - [Fatal Error] usm-core-200907.xsd:4174:231: Invalid byte 3 of 3-byte UTF-8 sequence.

2021-02-01 18:39:03,999 INFO  [ServletInit] ?.?(?)  - Initial SessionFactory creation failed: 
java.lang.Exception: TypeManager sanity test failure. TypeDefinitions are not available.
 at com.ca.sam.manager.typehierarchy.TypeHierarchyRepository.initialize(TypeHierarchyRepository.java:337)
 at com.ca.sam.manager.servlet.ManagerInitServlet.startComponents(ManagerInitServlet.java:230)
 at com.ca.sam.manager.servlet.ManagerInitServlet.initialize(ManagerInitServlet.java:131)
 at com.ca.sam.common.HttpServlet$InitTask.run(HttpServlet.java:231)
 at com.aprisma.util.thread.JobQueue.runJobThread(JobQueue.java:407)
 at com.aprisma.util.thread.JobQueue.access$400(JobQueue.java:43)
 at com.aprisma.util.thread.JobQueue$JobRunnable.run(JobQueue.java:136)
 at java.lang.Thread.run(Thread.java:748)

Cause

Corrupt usm-core-200907.xsd file.

Environment

Release : 4.2

Component : Service Operations Insight (SOI) Manager

Resolution

We did the following to resolve the issue

1) Stopped all SOI services

2) Edited \CA\SOI\tomcat\registry\topology\logical\tenant0\usmschema\usm-core-200907.xsd

3) Looked at line number 4174, compared it with same file from another SOI manager and found weird character's like "xE2 x80?"

4) Deleted the weird character's.

5) Ran registryloader.bat command on the SOI Manager (\SOI\tomcat\registry)

6) Started SOI services

 

 

Powered by Wolken Software