Skip to Content
author's profile photo Former Member
Former Member

Visual Composer - Error with Portal Connection

Hi!

we have an EP 6.0 SP9 and Visual Composer SP4 on Win2000. When I

try to connect Visual Composer to the Portal I get the following

Error Message

<i> Portal Runtime Error

An Expection ocurred while processing a request for:

iview: N/A

Componente Name: N/A

com/sapportals/htmlb/Container.

Exception id: 08:36_04/05/05_0010_8854550

See the details for the Exception ID in the log file</i>

The corresponding part from the log file:

<i>#

#1.5#000D601CB13300510000000300000D980003F64213D4BF0E#1115188591125#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Guest#18####d9cd3250bc6611d9bb67000d601cb133#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server#Java###Exception ID:08:36_04/05/05_0010_8854550

[EXCEPTION]

#1#com.sapportals.portal.prt.component.PortalComponentException: Error in init method

Component : com.sap.portal.guimachine.portalconnector.Login

at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:251)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.refresh(PortalComponentContextItem.java:267)

at com.sapportals.portal.prt.core.broker.PortalComponentContextItem.getContext(PortalComponentContextItem.java:312)

at com.sapportals.portal.prt.component.PortalComponentRequest.getComponentContext(PortalComponentRequest.java:385)

at com.sapportals.portal.prt.connection.PortalRequest.getRootContext(PortalRequest.java:435)

at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:607)

at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)

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:153)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:385)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

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:94)

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

Caused by: com.sapportals.portal.prt.core.broker.PortalComponentInstantiationException: Could not instantiate implementation class com.sap.guimachine.portalconnector.Login of Portal Component com.sap.portal.guimachine.portalconnector.Login because: Linkage error while loading implementation class

at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:234)

at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getComponentInstance(PortalComponentItemFacade.java:160)

at com.sapportals.portal.prt.core.broker.PortalComponentItem.getComponentInstance(PortalComponentItem.java:732)

at com.sapportals.portal.prt.component.PortalComponentContext.getComponent(PortalComponentContext.java:103)

at com.sapportals.portal.prt.component.PortalComponentContext.init(PortalComponentContext.java:242)

... 26 more

Caused by: java.lang.NoClassDefFoundError: com/sapportals/htmlb/Container

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:219)

at com.sapportals.portal.prt.core.broker.PortalComponentItemFacade.getInstanceInternal(PortalComponentItemFacade.java:228)

... 30 more</i>

Any suggestions are greatly appreciated,

Alexander Schulz

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 18, 2005 at 02:09 PM

    Alexander,

    I imagine that this happens to you when you are trying to login to the portal from the Visual Composer. Have you already installed the appropriate add-ons to the portal via the SDM? With the Patch 4 installation you downloaded there is a folder in the archive called add-ons, inside this folder are some archive files:

    BIUDISystems.sda

    com.sap.visualcomposer.BIKit.sda

    com.sap.visualcomposer.BIKitQV.ear

    com.sap.visualcomposer.portalcontent.sda

    com.sap.visualcomposer.sda

    Deploy these files to the portal and try to login to the portal again.

    Cheers,

    Scott

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      hello Scott,

      the problem occured with VC SP4 and EP SP9. This combination doesn't work. We patched the portal to SP11 and re-deployed VC add-ons and now the connection works fine.

      thanks,

      Alexander

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.