Implementing Business Package for Products 50.3.1

[Former Member]

Hi,

I´m trying to implement the Business package for products version 50.3.1 in EP6 . The migration of all worksets occured sucefully... but when i´m trying to run an iView from the new package i´ve an error, "Error in Source. Message not available..." .I already had created a new alias...someone can tell me what´s wrong?

Regards,

Hugo.

[Former Member · Accepted solution]

Hi

once your WAS connection and Connection Test for Connectors is working properly do the usermapping and then it should work fine

N.B: my EP version is EP 6.0 SP9

Regards

Rajeev

[Former Member · Accepted solution]

I raised the log-level, and there it is:

[code]#1.5#000255AB8B3B004900000085000002A80003FA36AA773849#1119537625271#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#Administrator#638####8940c8f0e3f411d9b855000255ab8b3b#SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#/System/Server#Java###Exception ID:04:40_23/06/05_0001_6364750

[EXCEPTION]

#1#com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component

Component : pcd:portal_content/com.sap.portal.migrated/ep_5.0/roles/com.sap.pct.plm.products_showcase/products_showcase/overview_showcase/com.sap.pct.plm.myobjects.MyMaterialsList

Component class : com.sap.pct.plm.myobjects.MyObjects

User : Administrator

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: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: java.lang.NoClassDefFoundError

at com.sapportals.portal.prt.service.jco.JCOClientService.internalGetJCOClient(JCOClientService.java:445)

at com.sapportals.portal.prt.service.jco.JCOClientService.getJCOClientPoolEntry(JCOClientService.java:1282)

at com.sapportals.portal.prt.service.jco.JCOClientService.getJCOClientPoolEntry(JCOClientService.java:1059)

at com.sapportals.pct.util.pdv.source.PortalAlvSource.executeFunction(PortalAlvSource.java:152)

at com.sapportals.pct.util.pdv.source.PortalAlvSource.getData(PortalAlvSource.java:271)

at com.sapportals.pct.util.pdv.DataViewer.executeSource(DataViewer.java:833)

at com.sapportals.pct.util.pdv.PDVDynPage.doProcessBeforeOutput(PDVDynPage.java:134)

at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:123)

at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)

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[/code]

I already did a search on "Error in service call of Portal Component", it seems to be a very general error message... maybe somthing went wrong with the deployment?

[Former Member · Accepted solution]

Now we're talking! In a portal stack trace the most interesting part is the last "caused by" (chained exception).

Seems like something is wrong with your jco installation.

There should be a jrfc.jar in the folder

\usr\sap\<sid>\JC00\j2ee\cluster\server0\bin\ext\com.sap.mw.jco

Regards, Karsten

[Former Member · Accepted solution]

I searched for it and jrfc.jar is in the folder you described.

Edit: Now even the connection test won't work anymore (it did before) although I didn't change anything...and there's a new error message (well, not that new, but different from before):

#1.5#000255AB8B3B005800000000000009A00003FA448E7C4326#1119
597314389#/System/Server#sap.com/irj#com.sap.portal.connectors.R3#Administrator#499####b5a94850e47f11d9bd64000255ab8b3b#SAPEngine_Application_Thread[impl:3]
_12##0#0#Error#1#com.sap.portal.connectors.R3#Plain###There was a problem to use JCO: java.lang.NoClassDefFoundError#
#1.5#000255AB8B3B005800000003000009A00003FA448E7C5643#1119
597314399#/System/Server#sap.com/irj#com.sap.portal.connec
tors.R3#Administrator#499####b5a94850e47f11d9bd64000255ab8
b3b#SAPEngine_Application_Thread[impl:3]
_12##0#0#Error#1#com.sap.portal.connectors.R3#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000255AB8B3B005800000005000009A00003FA448E7C5980#1119597314399#/System/Server#sap.com/irj#com.sap.portal.ivs.connectorService#Administrator#499####b5a94850e47f11d9bd64000255ab8b3b#SAPEngine_Application_Thread[impl:3]
_12##0#0#Error#1#com.sap.portal.ivs.connectorService#Java###Failed to get connection for system {0}#1#SAP_R3_PLM#

Message was edited by: Gesche Raabe

[Former Member · Accepted solution]

Hmmm, you could check the references.

Open the Visual Administrator,

go to server -> services -> ClassLoader Viewer -> libraries -> com.sap.mw.jco

and look if the following references are present:

[Removed by the moderator.]

Regards, Karsten

[Former Member · Accepted solution]

Jep, they're present.

[Former Member · Accepted solution]

Hmm, strange. I only can make suggestions...

You could use the tool attached to SAP note 785029 to test your backend connection. You can test jco and jcoclientservice connections there.

Regards, Karsten

[Former Member · Accepted solution]

Now thats just great.

I changed my *.dll configuration and the connection tests work again. All of them. There was still an error message about a TaskMonitor class not found. So I added jARM.jar to the J2EE classpath using the config tool, restarted the server, and the error message is gone.

Now, I'm back to "Error in Source. Message not available." showing ín the iView. And a new error message, this time found in dev_rfc.trc:

**** ERROR file opened at 20050627 113013 Westeuropäisch, SAP-REL 640,0,59 RFC-VER 3  MT-SL
T:3604 ======> Syntaxfehler im Programm SAPLPLM_DMS_GENERAL                     .
T:3604 <* RfcReceive [4] : returns 3:RFC_SYS_EXCEPTION
T:3604 <* RfcCallReceive [4] : returns 3:RFC_SYS_EXCEPTION

I'm guessing this is a problem on the R/3 side?

[Former Member]

Hi Hugo

I have done the implementation of

Business Package for Products successfully...

Have u done the system creation correctly...

can you give me the parameters that you gave while system creation

Regards

Rajeev.

[Former Member]

The logfile should give you a hint what went wrong.

We got the Business Package running on SP2 and SP12, so it shouldn't be a general problem.

Regards, Karsten

[Former Member]

I created the system and everything is fine there. The connection tests work and everything.

I checked my logfiles, several times, and there are no errors.

[Former Member]

What portal version are you running?

[Former Member]

It's EP6SP9.

I just tried another JCo configuration and now I have an error message.

Still, it doesn't help me get closer to the problem:

#1.5#000255AB8B3B00470000000300000B500003FA35652309DB#111
9532167143#/System/Server#sap.com/irj#com.sap.portal.porta
l#Administrator#439####06e06f70e3e811d9c7e2000255ab8b3b#SA
PEngine_Application_Thread[impl:3]
_29##0#0#Error#1#/System/Server#Plain###Exception 
ID:03:09_23/06/05_0003_6364750#

[Former Member]

Ok, I guess you have to raise the log levels.

How this can be done is explained here:

The following locations are from BP for Products ( they all can be found in com -> sap -> portal -> ...)

plmdocuments_logger

plmobjectmasterdata_logger

plmobjectbrowser_logger

myobjects_logger

mydocrules_logger

componentloader_r2_logger

After raising the log level from none to all, hopefully there is some more information in the defaultTrace.trc

Hope this helps,

Karsten

[Former Member]

I got the same problem, did you find a solution?

There are a number of topics on this, but no solutions. I've looked through my logfiles and there is nothing. Any ideas what causes this?