Invalid folders: Repository Managers in KM Configuration Post Patch 34

[Former Member]

Our Internal Test Portal is clustered across 2 physical servers. Patch34 was installed on the primary node

successfully. The Seconday Node was then started so that it would sync up with the Primary and get the patch installed. Everything seemed to work ok on the sync. However when you click on KMContent in the seconday node portal you get a message that says "<i><b>Item not found

/

The item you are attempting to access is not available. Check that the

name or link is correct. You might also check whether the associated

repository is currently accessible. "</b></i>

When trying to investigate what was causing this problem we discovered

the following error in the Knowledge Management Configuration.

When you click on System Admin - System Config - Knowledgement Mgmt -

Configuration - Content Managemnet you get an error at the top of the

screen that reads <i><b>Invalid folders: Repository Managers</b></i>

When you click on Repository Managers you get the following error at

the top of the screen. <i><b>Invalid classes: User Management Repository,

Taxonomy Repository, Content Exchange Repository, Virtual Root

Repository, User Management Engine (UME 4.0) Repository Manager,

Calendar Repository, Reporting Repository, File System Repository</b></i>

Any ideas?

Thanks,

Keith

[Former Member]

Keith,

Check the config_local.properties file under the KM application folder

...\irj\root\web-inf\portal\portalapps\com.sap.km.application\lib

if it is going to a share like

server\sapprt\j2ee...

then it may not work for you, so in order to resolve just map the network drive on cluster to primary node C drive

in to Z or Y drive.

and place the directory as

Z:\usr\sap\ep6q\global\config\cm

then restart the cluster.

Try and let me know it worked or not.

Ravi

[Former Member]

Ravi,

We are running on Unix so our path looks like the following

/usr/sap/ep6q/global/config/cm

Thanks,

Keith