KMC behaves strangely

[Former Member]

Hi all,

I am currently attempting to configure and run the Who Is Who iView. The configuration is straight forward and I have double checked my steps but when I go to use the iView I get something similar to "No results found" even though there are users defined that should be found. I also found the following stack trace in the start up log which may or may not be related:

#1.5#000802FD79F100440000025300001A680004109C74CCE6FF#1144164067375#/Applications/KMC/RF#sap.com/irj#com.sapportals.wcm.repository.runtime.CmSystem#Guest#192####6fed33e0c3ee11dacceb000802fd79f1#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sapportals.wcm.repository.runtime.CmSystem#Plain###CM system is starting ...

java.lang.Exception

at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:191)

at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:162)

at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:867)

at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:167)

at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:208)

at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:867)

at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1081)

at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1563)

at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1518)

at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1469)

at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:406)

at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)

at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)

at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)

at java.security.AccessController.doPrivileged(Native Method)

at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:359)

at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)

at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)

at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:392)

at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:138)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:376)

at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

#

#1.5#000802FD79F100440000025400001A680004109C76C5641D#1144164100452#/Applications/KMC/RF#sap.com/irj#com.sapportals.wcm.repository.runtime.CmSystem#Guest#192####6fed33e0c3ee11dacceb000802fd79f1#SAPEngine_Application_Thread[impl:3]_1##0#0#Info#1#com.sapportals.wcm.repository.runtime.CmSystem#Plain###CM successfully started.#

We are running EP6 SP15.

Any help/comments are appreciated.

Thanks,

Ricky.

[former_member441228 · Accepted solution]

That's just the callstack to the code that triggers the KMC startup that was added to easily identify illegal startups of KMC within wrong classloader hierarchies leading myriads of problem. This callstack is the only correct startup so everything should be fine.

[Former Member]

All,

Thank you for your advice. It turns out the issue was related to the portal version and KMC version being incompatible. The KMC SP did not work and was still on SP9.

Ricky.

Message was edited by: Ricky Symonds

[Former Member]

After further investigation of the logs it appears the crawler task does not run. The stack trace is below.

Date : 04/05/2006

Time : 12:38:03:015

Message : failed to run crawler task INDEXMANAGEMENT_ume.d0aff588-47a5-2810-f39e-892c630b28d8 - com.sapportals.wcm.service.xcrawler.XCrawlerException: The SQL statement "SELECT "XCRW_TASK_INDEX" FROM "KMC_XCRW_TASKS" WHERE "XCRW_TASK_ID" = ?" contains the semantics error[s]: type check error: the expression >>"XCRW_TASK_ID"<< (LONGVARCHAR) is not comparable and must not be used with "="

at com.sapportals.wcm.service.xcrawler.task.TaskPersistence.setTaskData(TaskPersistence.java:226)

at com.sapportals.wcm.service.xcrawler.task.CrawlerTask.<init>(CrawlerTask.java:200)

at com.sapportals.wcm.service.xcrawler.XCrawlerService.createCrawlerTask(XCrawlerService.java:751)

at com.sapportals.wcm.service.xcrawler.RunCrawlerJob.start(RunCrawlerJob.java:106)

at com.sapportals.wcm.service.xcrawler.job.CrawlerJobControl$JobRunnerThread.run(CrawlerJobControl.java:1605)

Severity : Error

Category :

Location : com.sapportals.wcm.service.xcrawler.RunCrawlerJob

Application : sap.com/irj

Thread : Thread[Thread-225,5,SAPEngine_Application_Thread[impl:3]_Group]

Datasource : 1144255149392:E:\usr\sap\DEV\JC00\j2ee\cluster\server0\log\defaultTrace.trc

Message ID : 000802FD79F100740000000D00001A68000410AD74DEC4B4

Source Name : com.sapportals.wcm.service.xcrawler.RunCrawlerJob

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : a434ae80c49811daa601000802fd79f1

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives :

Resource Bundlename :

Session : 192

Source : com.sapportals.wcm.service.xcrawler.RunCrawlerJob

ThreadObject : Thread[Thread-225,5,SAPEngine_Application_Thread[impl:3]_Group]

Transaction :

User : Guest

[Former Member]

Hi Ricky,

what version are you on? If you are running NW'04 SP9 without any patches (aka SR1), installing KMC SP9 Patch 3 should solve your issue.

Hope this helps,

Robert