UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Admiral
Admiral
486 views

Scheduled KM issue (application failed due to error - check msglog for possible messages-KMUpdate)

Hi Expert,

 

We are getting this error message (application failed due to error - check msglog for possible messages-KMUpdate).

 

Everytime we need to rescheduled through scheduled on the KMupdate. How we can monitor background process.

 

Where we can find this error message(application failed due to error - check msglog for possible messages-KMUpdate)

Best Regards,
Tom
0 Likes
2 Replies
Absent Member.
Absent Member.

Reason of frequently down of kmupdate scheduler could be some erroneous record which is leading to termination of background process while building the index.

First try to clear the table 'kmknowledgebaseupdates' and then rebuild the index. If error comes again then check the sm.log or may requires to enable the trace for same for further troubleshooting.

____________________________________
Assign Kudo, if found post useful and mark it accepted if solves the issue.
0 Likes
Micro Focus Expert
Micro Focus Expert

What version are you on? Like one of the posters mentioned if this is occuring during an incremental index then there is probably a bad record in the kmknowledgebaseupdates table. Clearing the table and running a full index could resolve the problem until that specific record is touched again and a new kmknowledgebaseupdates record is created. What you could do - to possibly identify the offending record - is the following.

 

If this system is 7.10, 7.11 or 9.2x do this:

1. Create a ScriptLibrary record named KMUpdate

2. Paste in this code

 

system.library.KMCollection_Update.refreshIndexes();

print("KMUpdate Completed");

 

3. Save

4. Compile

5. When you Execute this you will run the Incremental Update in the foreground. In the messages window of the client you may see the index die.The record that caused the problem is more than likely the one listed just before the error. From there you can look at the source record (Incident, Interaction, Knowlege Document, etc) to see what may be the problem.

 

If this system is 9.3x then:

1. Go to ScriptLibrary

2. Search for KMIndex (this is the same record that you would have created above, but already exists in 9.3x under this name)

3. Execute it.

 

In both cases you may be able to identify the offending record.

 

 

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.