SAP EP – Netweaver Portal

Symptom

KM content suddenly becomes unavailable, it is not possible to browse any KM content

Reason and Prerequisites

This note clarifies the possible reasons for KM unavailability.
Solution

It is important first to know some background as to what happened before this issue started to occur.
What is your current KMC SP and patch level? Attach the following pages as html files when opening a message with SAP http://portalHost.domain:port/sap/monitoring/SystemInfo http://portalHost.domain:port/sap/monitoring/ComponentInfoWere there any upgrades performed recently? If so, what component and what version/SP/patch did you upgrade from/to?Were there any other configuration changes made in your portal landscape recently which may have impacted on this issue?Check the KM component monitor for any errors and attach screenshots if they existGive exacts steps to reproduce the error and attach screenshotsAttach a copy of the default trace which includes the KM startup sequence(after a J2EE restart). Make sure the trace is taken from the server node on which the issue was reproduced.

There are various reasons which may cause KM unavailability, below are some of the most common issues which should be checked before opening a message with SAP.

Hot-Deployment

The most common reason for this to occur is Hot-deployment of a KMC component without restarting the surrounding container which loaded these components(PRT).
This can impact in different ways:
All KM content may be suddenly unavailableKM content on certain nodes may be unavailable while it is available on other nodesUnexpected behaviour of KM iviews which is resolved directly after a restart of the J2EEThere might be a decrease in performance of the systemYou may find the following default trace entries:
Error Plain Repository framework startup was not triggered by knowledgemanagement portal service. (Either because hot-deployment occurred or because a faulty custom KM component triggered the startup)The component monitor may show more than one startup entry as described in SAP note 894884

Please note that not all of these symptoms occur at the same time, they are just an indication that Hot Deployment has taken place.

Solution

Hot Deployment is not supported as documented in SAP note 894884 and should not be carried out in a Production environment. This topic is discussed in detail in the following SDN article,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bb1f18be-0801-0010-ffa0-e3495f7401bc
A restart of the J2EE will resolve the issue.

KM content is unavailable after an upgrade

This normally happens due to an incomplete deployment during a Patch or SP upgrade.
Symptoms may vary however common issues would be:
KM content being completely unavailable directly after an upgradeComponent monitor is unaccessibleCertain KM functionality is no longer working properly or menus or buttons are no longer available directly after an upgradeThe default trace contains entries such as:
“No repository manager found for prefix: /documents”
“Error during Knowledge Management startup! Please contact your system administrator”The config_audit.*.log may contain deployment errors, see SAP note 895523.

Solution

A redeployment of the last KM components which were upgraded as per SAP note 895523 can often resolve such issues however it is better to get this checked by SAP support before doing this.
Before any redeployment takes place ensure that you have backup of you KM as per SAP note 1000150(ideally you should have a backup from before the initial upgrade took place also).

Node specific issues/synchronisation issues

KM Content is not completely unavailable however certain content is not available one one specific node or there is no synchronisation between content on different nodes.

Solution

Check that the Cluster flag is set in the System Landscape Service. Go to Sys Admin > Sys Config > KM > CM > Global Services > System Landscap Definitions.
If you have more than one CM system defined here then you must set the Cluster Installation flag at Global Services > (Show Advanced Options) System Landscape service
Check also that you have the FQDN(including port number) entered in the ‘Host’ parameter of the URL Generator service. If you are using a loadbalancer then the loadbalancer URL should be used. See the following documentation for more information.
http://help.sap.com/saphelp_nw70/helpdata/EN/7d/236cfa17034a37a439dc392ec59eb0/frameset.htm