Re: Error in System Object in Portal

Hi Experts,
I have created a system and have given values for all the property category
1.WAS
2.ITS
3.Connector
1.when I do the connection test for ITS, I'm getting error saying
"User mapping is not valid
HTTP/S connection failed"
2.when I do the connection test for Conectors, I'm getting the error saying
"Connection failed. Make sure user mapping is set correctly and all connection properties are correct."
Help me to resolve the issue.
I guess there is problem in values for ITS and Connector property category so I have the following doubts
1.How to find the ITS host name?
2.How to find the ITS path?
Useful answers will be rewarded.
Thanks in Advance,
Suba

Generally I don't worry about error messages in the test tool! Instead, I try to create a transaction iView and see if that works. That's the important test.
Cheers

Similar Messages

SRM system object within Portal: WAS settings with Webdispatcher

Hello Portal experts,
we have SAP EHP4 ERP system (only ABAP stack).
In order to use some SRM functionality we installed SAP EP (EHP1) and creates a appropriate system object within portal.
We use a Webdispatcher, so we have to replace within WAS area the local address by the address of Webdispatcher and appropriated port (webserver:567).
The tests of this system object looks as follows:
The address of http://webserver:567 can be retrieved
The problem are the results of following tests:
http://webserver:567/sap/bc/ping
http://webserver:567/sap/bc/webdynpro
These errors occured because the both pathes /sap/bc/ping and /sap/bc/webdynpro do not exist on Portal/Java engine.
Questions:
How can we connect ABAP backend to Portal with extra Webdispatcher?
What are the setting within WAS area?
kind regards

Hi Thom,
Is your webdispatcher in front of your portal? or in front of the ICM of your Backend System?
If the applications that you want to enable via your EP are of the type: WD for ABAP, BSP, IAC or ITS then you should also have a webdispatcher in front of your Backend System (in addition to on in front of your portal).
Please check the following link:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/9a9a6b48c673e8e10000000a42189b/frameset.htm
On this page, scroll down to the last example. Although the image is there to explain "High Availability of the SAP Web Dispatcher" it gives you a good view on the request respond steps.
One rule of thumb is that the EP system itself doesn't act as a reverse-proxy. In other words, if an iView points to a WD 4 ABAP application on the Backend then the actual WD4ABAP application is rendered in an iFrame.
From a technical/connection point of view the client (browser) has 2 connections, one to the EP and 1 tot the Backend.
Allot of people do not realize this when they start there project...
Cheers, hope this helps you a bit....
B

BI System Object in Portal

Hi everyone,
I'm trying to to display a BI Report in the Portal. Both systems are on NW04s.
The connection test of the BI system object fails with the following error:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check whether the system can be retrieved
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. WAS_AND_ITS_CONNECTION_TEST_DETAILS_RESOLVE_NAME
6. WAS_AND_ITS_CONNECTION_TEST_PING_SERVER_DETAILS
7. WAS_CONNECTION_TEST_DETAILS_PING_SERVICE
8. Check HTTP/S connectivity to the defined backend application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (hvrz0afa.hvr.sbs.de:8011)
5. WAShvrz0afa.hvr.sbs.deCONNECTION_TEST_HOSTRESOLVE_RESULT_PASS
6. WAShvrz0afa.hvr.sbs.deAND_ITS_CONNECTION_TEST_PING_SERVER_FAIL
I have done all system settings for connector, WAS and ITS.
The test connection with connector was successful.
What could be the problem?

Hi,
Can you please send the values you have set for the ITS related parameters ?
Secondly, the test connection results are not reliable. I would rather request you to create a BW report iview and then use this system and check if you are able to see the report ( or get the username & password screen if the SSO is not configured or user is not mapped). This would atleast confirm that the ITS has been configured properly. If it gives an error, then we can make the necessary changes.
Cheers,
Sunil
PS: Reward points for helpful answers.

How to create a system object in portal that points to a web dispatcher

Hi,
How do we create a system object in the portal for a web dispatcher? The web dispatcher in turn points to an ECC system. The path for communication is EP>Web Dispatcher>ECC
Regards,
Sridevi

Hi,
Connection test for the following succeeded:
1. SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (mtw02spwp02:80)
5. The host name mtw02spwp02 was resolved successfully.
6. The Web AS ping service http://mtw02spwp02:80/sap/bc/ping was not pinged successfully. If the ping service is not activated on the Web AS, you can try to call the ping service manually.
7. An HTTP/S connection to http://mtw02spwp02:80/sap/bc/bsp/sap was obtained successfully.
2. ITS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (mtw02spwp02:80)
6. The host name mtw02spwp02 was resolved successfully.
7. An HTTP/S connection to http://mtw02spwp02:80/sap/bc/gui/sap/its/webgui was obtained successfully.
Next test for SSO failed:
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
Regards,
Sridevi

Defining SID system object in Portal

Hi!
Can some one please tell me how to define a <SID> system object SAP ECC 6.0 ABAP system in Portal?
What are the technical steps (tools and files)?
What are the prerequisite to be met?
Any helpful information will be very appreciated!
Thank you very much!
Thom

Covered many times in the forums, Thom. Please search for note 761917 for examples etc.

Error with response object in Portal Application Module

Hi,
i have a portal application project in NWDS, with a JspDynpage component. I have a jsp that contains this code:
OutputStream os = componentResponse.getServletResponse().getOutputStream();
response.addHeader("Content-Disposition", "attachment;filename=" + sTITLE +".pdf");
response.setContentType("application/pdf");
os.write(contenido);
os.close();
this code open a pdf in new window. In web module project that app runs correctly but in portal application no, it fails in object response. the log (in default trace) doesn´t help me nothing, only sais:
Jun 6, 2011 3:19:55 PM com.sap.portal.prt.runtime.servlet_jsp [SAPEngine_Application_Thread[impl:3]_13] Error: >>> JSPCompiler >>> ERROR in Compiling :JSPFileInfo :314221189
JSP File : /usr/sap/DP4/DVEBMGS40/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.factdist.efact.por/pagelet/inicio.jsp
Class Name: sapportalsjspInicio
Java File : /usr/sap/DP4/DVEBMGS40/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.factdist.efact.por/work/pagelet/_sapportalsjsp_inicio.java
Package Name : pagelet
Class File : /usr/sap/DP4/DVEBMGS40/j2ee/cluster/server0/apps/sap.com/irj/servlet_jsp/irj/root/web-inf/portal/portalapps/appl.factdist.efact.por/work/pagelet/_sapportalsjsp_inicio.class
Is out dated : false [email protected]bbc2b
In addition, i can use the request object perfectly
somebody knows what's happening??
Thank you,
Fernando

Hi,
You shouldn't use the response object directly
Instead, create a new HttpServletResponse reference from the componentRequest object.
Try using the following:
long length = file.length(); // where 'file' is a File() object of your sTITLE +".pdf" file
// Create the byte array to hold the data
byte[] bytes = new byte[(int)length];
int offset = 0;
int numRead = 0;
while (offset < bytes.length && (numRead=is.read(bytes, offset, bytes.length-offset)) >= 0) {
offset += numRead;
//The most important part:
HttpServletResponse res = componentRequest.getServletResponse(true);
res.setContentType("application/pdf");
res.addHeader("Content-Disposition", "attachment;filename=" + sTITLE +".pdf");
res.getOutputStream().write(bytes);

Error while creating a system object for R3 in portal

Hi,
I am getting error while trying to create a system object in portal.
Following are the details I used :
Under WAS...
Web AS Host Name :<XXXX>:8001
Web AS path: /sap/bc/bsp/sap/
Web AS protocol : http
Under User management:
Authentication Ticket Type : SAP Logon Ticket
Logon Method :SAPLOGONTICKET
User Mapping Type : admin,user
Under Connector:
SAP Client : <Client NO>
SAP System ID : <System ID>
SAP System No : <System No>
System Type : SAP_R3
While trying with connection test... I am getting like this:
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the server to see if it is alive.
7. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
8. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (<FQDN server name>:8001)
5. The host name <FQDN Server Name> was resolved successfully.
6. The server sapdwh01 could not be pinged successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
It seems that the portal is not able to ping to R3 system. I tried to ping to R3 server from portal server by command prompt. I am able to ping. Also under SICF, I can see ping service as in activated state.
Kindly help.
Regards,
Niraj
Edited by: Niraj Kumar on Dec 11, 2008 10:41 AM

I created a SAP Transactional iView for transaction SE80.
Also, I tried from under System Administration -> Support -> SAP Transaction. It is not working.
Got portal Runtime error :
Portal Runtime Error
An exception occurred while processing your request
Exception id: 12:57_11/12/08_0003_2795650
See the details for the exception ID in the log file.
Regards,
Niraj

Error Java System: unknow error of portal comunication

Hi All!
I get the following error when opening a WAD Template in the WAD Application.
<b>"Error Java System: An unknow portal comunication error has ocurred"</b>
After accept this error, it opens the template and I can work with it, but when I make changes, these are not reflected when executing the template, until I open this template in other machine.
I have reviewed the test integration (between BW and Portal) according with the steps in the spro "Integration into Portal" and the test is successful in all the steps.
So, I dont know what can be wrong.
Thnks a lot for your help!
Yolanda.

Hi,
try this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler
If it does not open
Check for OSS Note 989525
Hope this helps you
Regards
Karthik

Issues while JDBC System Object Creation for accessing MS SQL 2000 Server

Dear Experts,
I am creating system object to connect to MS 2000 server in Ep 7.3
1) created system with all the properties
2) User mapping done
3) permissions ok
but still while testing connection its giving error
"No connection to system DBSQL found:
com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not create JCO connection.
'user' missing"
""" Connection Test for Connectors:
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the back-end application using the connector defined in this system object
Results
Default alias retrieved successfully
Connection failed. Make sure user mapping is set correctly and all connection properties are correct. """"

Dear Mr. Arun,
thanks for the valuable sap note
I have applied the note but same result :
No connection to system DBSQL found:
com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not create JCO connection.
'user' missing
1) i have created JDBC Driver as mentioned in sap note
2) created System object
3) created destination as required in EP 7.1 and above
4) mapped user in user administration
when i am testnig connection its giving above mentioned error
same system object when i am creating for EP 7 its working fine with all 3 jar files and system creating succesfully
plz help

System object with same credentials for all users?

Hi everyone
I would like to create a system object in Portal, which can be used by users in a specific group. However, I want all users to use the same credentials for this system. Is this possible?
I've tried creating systems, but they all seem to require user mapping to work correctly. Is there some way I can create a system object with the credentials as part of the object, and then just assign permissions to it as required?
Please let me know if this raises any questions.
Thanks
Stuart

i dont think it is possible to create a system object for all the users with same credentials.anyways you are trying to create system object for some users who belong to a particular group.so you need to do only one time user mapping for that group
go to user administration-search for the group-go to user mapping tab-give username and password..
reward points if helpful

Error while trying to open Transport Object in portal

Hi,
I want to move some pcd objects from my DEV server to PROD server.
I created a transport object in the pcd but when I try to open it for editing, I get the following exception:
Date : 06/18/2008
Time : 20:01:49:094
Message : Exception ID:05:01_18/06/08_0066_222946050
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
User : MAYAS
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.lang.RuntimeException.<init>(RuntimeException.java:43)
     at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
     at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Error.<init>(Error.java:49)
     at java.lang.LinkageError.<init>(LinkageError.java:36)
     at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
     at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
     at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
     ... 42 more
Severity : Error
Category : /System/Server
Location : com.sap.portal.portal
Application : sap.com/irj
Thread : SAPEngine_Application_Thread[impl:3]_10
Datasource : 222946050:/usr/sap/YED/JC22/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 00145EC6C66B005E00000CED0000997600044FF3D1028EED
Source Name : com.sap.portal.portal
Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
User : MAYAS
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.lang.RuntimeException.<init>(RuntimeException.java:43)
     at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
     at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Error.<init>(Error.java:49)
     at java.lang.LinkageError.<init>(LinkageError.java:36)
     at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
     at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
     at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
     ... 42 more
Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
User : MAYAS
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Exception.<init>(Exception.java:41)
     at java.lang.RuntimeException.<init>(RuntimeException.java:43)
     at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
     at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
     at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
     at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
     at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
     at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
     at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
     at java.lang.Throwable.<init>(Throwable.java:194)
     at java.lang.Error.<init>(Error.java:49)
     at java.lang.LinkageError.<init>(LinkageError.java:36)
     at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
     at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
     at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
     at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
     ... 42 more
Dsr Component : DEVQA.YAFORA_YED_222946050
Dsr Transaction : 144e38f03d5811ddb67400145ec6c66b
Dsr User : MAYAS
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/Server
Resource Bundlename :
Session : 8815
Source : com.sap.portal.portal
ThreadObject : SAPEngine_Application_Thread[impl:3]_10
Transaction :
User : MAYAS
The error occurs only on the DEV server.
My Portal is EP7 SP15.
How do I solve this?
Thanks,
Omri

Solved it on my own by restarting the portal.

Problem Create System Object in the Portal for connecting CRM abap

Hi, i creating system in the portal (JCX) for connecting system ABAP CRM (CRX), after create system try run test connection and show messages error:
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
In the logs the portal (NWA) show messages:
Failed in creating the JCO Connection.
The logs operation system (log Security_audit.log)
Error> occured >Thu Jun 23 11:34:41,278<RfcException: message: 'mshost' missing Return code: RFC_INVALID_PARAMETER(19 Return code: RFC_INVALID_PARAMETER(19)    error group: 101 key: FC_ERROR_PROGRAM
     at com.sap.mw.rfc.api.RfcOptions.checkParameters(RfcOptions.java:438)
     at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:688)
     at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1079)
     at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)
Plase help, any idea?

message: 'mshost' missing Return
During the System Object Creating in System Landscape, there is any entry as Message Server Host: CRM MS HOST
and Message Server Port : sapmsSID and add this entry in etc/services --> bottom samsSID 36NN/tcp where NN is instance number.
Try this and let me know.
Thanks
SM

VC Error: There are no BI systems defined in portal/ no authorization

Hi,
when trying to launch the BI integration wizard on an iview in Visual Composer in the ESA Discovery system I get the follwing error message:
"WARNING 2005: There are no BI systems defined in portal. In order to use BI integration wizard, you must first define at least one BI system based on the BI XMLA, BI ODBO, BI JDBC, or BI SAP Query Connector."
When I click on the "Find data" button in VC I am able to see the names of BI systems in the System drop down box and can search queries and execute them. So the BI must be connected.
I did not change the original configuration of portal or VC.
When trying to launch the MDX editor or SQL editor I get the error message that I am not authorized to do this, but I am logged on as user admin or user j2ee_admin.
Can somebody help me please
Best Regards
Maximilian Lohrer

Question has been sent twice, I close it.

Error while Importing SYSTEM objects into 9.2.0.6

HI,
I got the following error while importing data into 9.2.0.6 DB .
It is related to a SYSTEM object.
. importing SYSTEM's objects into SYSTEM
IMP-00017: following statement failed with ORACLE error 2270:
"ALTER TABLE "DEF$_CALLDEST" ADD CONSTRAINT "DEF$_CALL_DESTINATION" FOREIGN "
"KEY ("DBLINK") REFERENCES "DEF$_DESTINATION" ("DBLINK") ENABLE NOVALIDATE"
IMP-00003: ORACLE error 2270 encountered
ORA-02270: no matching unique or primary key for this column-list
Constarint exists on Composite Primary Key on the parent table.
Can anybody help me out on this.
Regards,
Sumit Singh Chadha

Hi,
don't mentioning why are You importing SYSTEM objects, the error that You have, just looking the message, is due to an export done without the clause CONSISTENT=Y (so all relations parent/child preserved) having the replication (the table in error is one of the replication dictionary table) active (not quisced)
Repeat the export operation using CONSISTENT=Y an stop replication activity.
Hope this helps
Max

Error trying to run SSIS Package via SQL Server Agent: DTExec: Could not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object

Situation:
SSIS Package designed in SQL Server 2012 - SQL Server Data Tools
Windows 7 - 64 bit.
The package (32 bit) extracts data from a SQL Server db to an Excel Output file, via an OLE DB connection.
It uses 3 package variables:
*) SQLCommand (String) to specify the SQL Statement to be executed by the package
Property path: \Package.Variables[User::ExcelOutputFile].Properties[Value]
Value: f:\Output Data.xls
*) EXCELOutputFIle (String) to specify path and filename of the Excel output file
Property path: \Package.Variables[User::SQLCommand].Properties[Value]
Value: select * from CartOrder
*) VarObjectDataSet (Object) to hold the data returned by SQL Server)
Property path: \Package.Variables[User::VarObjectDataSet].Properties[Value]
Value: System.Object
It consists out of 2 components:
*) Execute SQL Task: executes the SQL Statement passed on via a package variable. The resultng rows are stored in the package variable VarObjectDataSet
*) Script Task: creates the physical output file and iterates VarObjectDataSet to populate the Excel file.
Outcome and issue:The package runs perfectly fine both in SQL Server Data Tools itself and in DTEXECUI.
However, whenever I run it via SQL Server Agent (with 32 bit runtime option set), it returns the errror message below.
This package contains 3 package variables but the error stating that a package variable can not be set, pops up for the VarObjectDataSet only. This makes me wonder if it is uberhaupt possible to set the value of a package variable
of type Object.
Can anybody help me on this please ?
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 6:40:20 PM DTExec: Could
not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object. Started: 6:40:20 PM Finished: 6:40:21 PM Elapsed: 0.281 seconds. The package execution failed. The step failed.
Thank you very much in advance
Jurgen

Hi Visakh,
thank you for your reply.
So, judging by your reply, not all package variables used inside a package need to be set a value for when run in DTEXEC ?
I already tried that but my package ended up in error (something to do with "... invocation ...." and that error is anything but clearly documented. Judging by the error message itself, it looks like it could be just about anything. that is why I asked my
first question about the object type package variable.
Now, I will remove it from the 'set values' list and try another go cracking the unclear error-message " ... invocation ...". Does an error message about " ... invocation ..." ring any bells, now that we are talking about it here ?
Thx in advance
Jurgen
Yes exactly
You need to set values only forthem which needs to be controlled from outside the package
Any variable which gets its value through expression set inside package or through a query inside execute sql task/script task can be ignored from DTExec
Ok I've seen the invocation error mostly inside script task. This may be because some error inside script written in script task. If it appeared after you removed the variable then it may because some reference of variable existing within script task.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Re: Error in System Object in Portal

Similar Messages

Maybe you are looking for