on 02-28-2006 4:05 PM
I'm having difficulty getting our Lotus Notes repository manager running successfully. I keep getting a portal exception when trying to view the repository within KM. The following exception is logged:
#1.5#00085402C3D6004B00000070000008B800040DDC52C43D54#1141139839399#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#WILLF#365##ep6sb3.whirlpool_SB3_13076150#WILLF#50d59580a86c11daa45100085402c3d6#SAPEngine_Application_Thread[impl:3_12##0#0#Error#1#/System/Server#Java###Exception ID:10:17_28/02/06_0002_13076150
[EXCEPTION]
#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal
Component
Component :
pcd:portal_content/administrator/super_admin/super_admin_role/com.sap.portal.content_administration/com.sap.portal.content_admin_ws/com.sap.km.AdminContent/com.sap.km.AdminContentExplorer/com.sap.km.AdminExplorer
Component class : com.sapportals.wcm.portal.component.base.ControllerComponent
User : WILLF
at
com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:969)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at
com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at
com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at
com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at
com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:95)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Caused by: com.sapportals.wdf.WdfError
at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:678)
at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.htmlb.Container.preRender(Container.java:118)
at com.sapportals.portal.htmlb.PrtContext.render(PrtContext.java:413)
at com.sapportals.htmlb.page.DynPage.doOutput(DynPage.java:237)
at
com.sapportals.wcm.portal.component.base.KMControllerDynPage.doOutput(KMControllerDynPage.java:130)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:129)
at
com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at
com.sapportals.wcm.portal.component.base.ControllerComponent.doContent(ControllerComponent.java:73)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at
com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at
com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more
Does this look like a problem with permissions? Just knowing the general problem area would be helpful, but this logged error description doesn't help me much at all. We're running EP6 SP14, and our Lotus Domino server is on version 5.11. Any guidance at all would be appreciated. Thanks so much!
hi Will
have you solved the problem.
I miss the same error,too.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
With Michael Sambeth's help, we've come to the realization that the SAP-provided Lotus Notes Repository Manager is too buggy and simply isn't a good solution for what we need. So we're going to start the process of upgrading (or replicating) our R5 servers to R6, and then use Conet's business package for Lotus Domino connectivity.
We haven't yet accomplished this, but this is what I recommend. Hope this helps!
Cheers,
Fallon
Hello Will,
are you using the SAP Repository Manager (R5 only) or the Conet Repository Manager (R6.5 and onwards)?
Thanks & regards
Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Fallon,
based on my experience with the Domino Java connectivity I would suggest to use Domino R6 for SAP Repository Manager Integration. The R6 Java interface is more reliable than the R5 Java interface and has better performance.
You could use Domino replication to replicate the data between R5 and R6.
Regards
Michael
Thanks for your input, Michael. It's much appreciated. One more request for your expertise: The Conet business package... Would the business package work if our Domino servers were at a version older than 6.5? I'd like to get your opinion on using the Conet business package in combination with Domino 5.x servers. Is this a feasible option?
Thanks again,
Fallon
Hello Vivek
It is my understanding that the Lotus Notes repository manager provided out of the box from SAP is compatible with Domino servers versions 5.x. For Domino versions 6.x the Conet business package would be required.
However, as you can see, I haven't yet been successfully able to get the Lotus Notes RM provided by SAP working, but it's looking like it's due to us having the wrong version of the Lotus Domino toolkit.
For some good documentation on setting up the default Lotus Notes repository manager, go here: <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/ba/8bccaef0dac945a4177797f4e29aa0/frameset.htm">http://help.sap.com/saphelp_nw2004s/helpdata/en/ba/8bccaef0dac945a4177797f4e29aa0/frameset.htm</a>
Hope this helps!
Cheers,
Fallon
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.