Error when create client proxy in ABAP

hi all
when I tried to create a client proxy through wsdl: http://www.webservicex.net/geoipservice.asmx?wsdl , I got and error message "Exception occurred in library handler", what's the really matter with this error ?
thanks very much!

You need to copy the WSDL file to a local file and edit it. The WSDL file contains non-SOAP bindings and that's what the generator is choking on. Use the 'Local file' option to generate the proxy class after editing the file.

Similar Messages

Creating client proxy in ABAP failed

Hello,
I tried to create a client proxy for a WebService and got the same error like in this thread: [Error when create client proxy in ABAP; "Exception occured in library handler".
I've got only a little of knowledge about SOAP that's why I cannot edit the WSDL File. But I think there is no mistake in the WSDL. I used one in Visual C# and it works.
Is it possible to change settings of the proxy generator to ignor non-SOAP bindings?
Thanks for your help.
Frank
Edited by: Frank Staudte on Jan 20, 2009 9:17 AM

Hi,
Search in SDN you can find many links.
Client Proxy -
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
Regards,
Phani

Error when creating a Proxy Object from WSDL

Hi,
when creating a proxy object in abap based on the [WSDL|http://download.mapandguide.com/EN/dev/xserver/XLocate-1.6.0.3.wsdl] i get the error 'Incorrect value: Unknown Type Referencens0:ArrayOfString'.
1- Is there a conflict with the type 'String' that's also a type in ABAP
<complexType name="ArrayOfString">
<sequence>
<element name="String" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="true" />
</sequence>
</complexType>
2- Is it a name space problem?
xmlns:ns0="http://types.xlocate.xserver.ptvag.com"
type="ns0:ArrayOfString"
3- Something else?
Please Help!
Thank
Fouad

Hi Isaias,
we are working with this versions:
SAP_BASIS 700 0015 SAPKB70015 SAP Basiskomponente
SAP_AP 700 0013 SAPKNA7013 SAP Application Platform
We are not working with developer studio, only with the regular tools of the abap development workbench Transaction SE80.
Thanks,
Fouad

Error while creating Client Proxy from SE80

Hi all,
I am trying to create Client Proxy with WSDL through SE80. There is no involvement of XI to create the Proxy.
I am using the option 'Local file' and uploading the wsdl file.
But I am getting the following errors.
"Proxy-Generierung: Fehler aufgetreten"
"Exception occurred in library handler"
"Illegal syntax: Element header has invalid enhancement attribute
http://schemas.xmlsoap.org/wsdl/:required"
If any one could understand them and worked in a similar scenario, pls help me out.
regards,
teja.

hi,
you might want to post the WSDL in question for us to have a look at.
but actually, the error message tells a lot:
http://schemas.xmlsoap.org/wsdl/:required
the second colon(, the one between wsdl/ and required, makes this expression an illegal one in any kind of a URI-like meaning (namespace, ref-URL, ...)
anton

Error at creating Client Proxy of external webservice (WSDL)

Hi Experts,
I try to create a Client Proxy Object out of an external webservice. Here is the WSDL URL:
[http://www.webservicex.net/CurrencyConvertor.asmx?wsdl]
I try to create it with this URL and then I get the error message
Not implemented
Exception of class CX_SIDL_INTERNAL_ERROR
I found two other threads with a similar problem:
cunsuming external webservice in ABAP
Problem while consuming external webservice
But there is no solution that worked for me. In the first thread it is mentioned, that the code between
<wsdl:binding name="XXXXHttpGet" type="tns:XXXHttpGet">
and it's closing brackets should be removed in a local file. I tried that and was able to create a client proxy object out of this local wsdl-file. But then I called the webservice with the folling coding for testing:
report z_currency_converter.
data: convert type ref to zzzco_currency_convertor_soap.
try.
 create object convert
exporting
 logical_port_name = 'Z_LP'
catch cx_ai_system_fault .
endtry.
 data: output type zzzconversion_rate_soap_out .
 data: input type zzzconversion_rate_soap_in .
 input-from_currency = 'EUR'.
 input-to_currency = 'USD'.
try.
call method convert->conversion_rate
exporting
 input = input
importing
 output = output
catch cx_ai_system_fault .
catch cx_ai_application_fault .
endtry.
write output-conversion_rate_result.
The same code worked fine in another system. In this "older" system could also create a client proxy, I think because it has a newer Support Pack version.
SAP says the following:
The problem is that this WSDL uses two bindings different from SOAP
binding which is not in conformance with Basic Profile 1.1 -
http://www.ws-i.org/Profiles/BasicProfile-1.1.html#WSDLBINDINGS .
I looked in the document, but I do not know where the problem in the WSDL file exactly is. What have I to change? Or can somebody give me the URL of a free webservice, that you used for creating a client proxy with a new support pack standing? In the "old" system there is not yet the SOAMANAGER but in the one where it doesn't work.
I hope you have an idea.
Thanks a lot in advance!
Best Regards,
Ingmar

I think it is the problem of version.U need to ask SAP to release some patch levels to correct it.
Regards
Snehasish

Namespace Error when generating Client Proxy for Java Web Service

Hi.Experts:
    When I want to generating a Client Proxy for my WSDL file created by JAVA,it seems that some namespace errors occur.
    The error like this:
    "Incorrect value: Unknown Namespace http://sql.java
    Exception of class CX_SLIB "
   I checked all the SOAP runtime,it seems no error.So do I need to create the objects in the Integration Repository??If it is the truth,then how can I do it.
Best Regards
Martin Xie

Hi Martin
I didn't find this options in SAP GUI Create -->Enterprise Service ->Consumer Service ->url/http
Maybe my version is different.
You say that you can select the file ou url.
Did you select the file or url?
If was file, open this file, find the tag that you have the wrong namespace and eliminate this tag.
If was url, access this url, copy the xml and same in one file, then select this file in the step above.
I don't know if works, its only a suggestion.
regards
Marcos

Unknown Namespace when creating Client Proxy

Hi,
I'm trying to generate a client proxy using Local File.
It gives error
Incorrect value: Unknown Namespace urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2
The wsdl file does not give any error.
This error seems to be coming from XSD file named UBL-CommonAggregateComponents-2.0.xsd
Below is part of this XSD file.
Can you tell me what is the problem here.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
 xmlns="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
 xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
 xmlns:udt="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
 xmlns:ccts="urn:un:unece:uncefact:documentation:2"
 xmlns:qdt="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
 targetNamespace="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
 elementFormDefault="qualified"
 attributeFormDefault="unqualified"
 version="2.0"><xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2"
 schemaLocation="UBL-CommonBasicComponents-2.0.xsd"/>
 <xsd:import namespace="urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2"
 schemaLocation="UnqualifiedDataTypeSchemaModule-2.0.xsd"/>
 <xsd:import namespace="urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2"
 schemaLocation="UBL-QualifiedDatatypes-2.0.xsd"/>
Thanks
Girishkumar

Hi ,
Make sure no restriction from firewall on proxy settings.
Namespace you are using for client proxy may not be available for consumption/not published.
Also , Try to check connection.
OSS note 944029 will give you SAP restrictions on name space.
Regards
Nagaraju

Need some help in creating client proxy to call webservice

Hi experts,
I am new to ABAP so couldnt understand the SAP ABAP jargons.
On of my colleague has written one search help exit function and i need to use that and have to write client proxy to establish connection to webservice.
I never worked on proxy or webservice so, struggling to understand the concept and steps.
I am following second part i.e Release 640 part of /people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap weblog.
I couldnt find "To get the process started, we turn to our old friend SE80. From the Enterprise Services Tab, we are going to select Client Proxy and then hit create"
when i go to transaction se80 ObjectNavigator, i could see two dropdown lists after some tabs.
in first list, I have selected, "Application Hierarchy", and in second I am selecting "Package".
Not sure whether its correct or not.
Once i do this i could see long list of Object name and its description.
Now, what should i do ? where should i go for "Enterprise Services Tab" to create my proxy.
Any help would be appreciated.
Please send me PDF, having detailed steps to create client proxy.
Thanks,
Pranav

Right click on the package and select Proxy object. In the Wizard select Service Consumer.
then give the url of the WSDL file you want to access or path if u have a local file.
then give the package for client proxy.
then complete the wizard. the client proxy will be create in that package.
Next step will be creating a Logical Port using the transaction "lpconfig". Give the proxy name of the service interface created under client proxy. and set the configuration as follows.
1. Make as a default port.
2. in the URL, give the url of the webservice (.asmx)
3. select "State Enabled" and "Message ID"
and after creating a logical port, set the proxy settings as in your webbrowser.
(Http proxy server and port).
then simply execute your webservice from SE80.

Error when creating files for transport request SAPK-700BGINPLMWUI

Hello experts,
We're upgrading our 46c System to ERP 6.0 EHP4.
In Phase EHP_INCLUSION we get the following error Message: Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"
We've already checked the SAINT version; Upgrade Fix, SAPCAR version. We've checked our TMS as well and everything seems O.K.
Any help would be really appreciated!!!
Complete Error message:
EhP component PLMWUI, 700
Looking for SAINT package for 'PLMWUI' ...
R3upReadNewPackages:
patchType='U', langVect='DEC'
RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"
RFC Login succeeded
Calling function module "spda_read_new_packages" by RFC
ismovesVersion='0'
R3upReadNewPackages: exit: rc=0
... No matching package found.
R3upReadNewPackages:
patchType='I', langVect='DEC'
RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"
RFC Login succeeded
Calling function module "spda_read_new_packages" by RFC
ismovesVersion='0'
R3upReadNewPackages: exit: rc=0
Found: name = 'PLMWUI', release = '700', package = 'SAPK-700BGINPLMWUI', type = 'AOI'
... Matching package found: 'PLMWUI','700','SAPK-700BGINPLMWUI'
(trc) R3upPatchDisassembleQueue: 1 package queue entries
(trc) R3upPatchDisassembleQueue: force=YES
(trc) R3upPatchDisassembleQueue: 1 packages will be disassembled
Starting disassembling package queue
Date & Time: 20100319133139
Starting RFC Login to: System = "X05", GwHost = "sxt ", GwService = "sapgw00"
RFC Login to: System="X05", Nr="00", GwHost="sxt ", GwService="sapgw00"
RFC Login succeeded
Calling function module "SPDA_DISASSEMBLE_QUEUE" by RFC
Input table IT_PATQ:
"SAPK-700BGINPLMWUI","000","AOI","PLMWUI","700","SAP PLM Web UI","00"
Call of function module "SPDA_DISASSEMBLE_QUEUE" by RFC succeeded
Logging off from SAP system
Date & Time: 20100319133139
Disassembling package queue failed, rc = "2", reason = "Error when creating files for transport request SAPK-700BGINPLMWUI"

Hello Anthes,
Please Check the things in following sequence :
1.Use latest SAPehpi, R3trans and tp versions.
2. users/group authorization issue and/or ownersip limitations (set 777) .Reboot the server to make sure, that the authorisations are updated and there is no lock on a file in the EHPI dir.Repeat the phase.
Folders where permissions should be 777 are Upgrade directory, Data Directory, Cofile directory and .../EPS/in.
3. Source file corruption can be ruled out by execution
R3trans -l /usr/sap/<SID>/..../abap/data/R-700BGINPLMWUI.SAP (The data file corresponding to the Package which is giving error). Check if this ends fine.
Note 2050
4. Confirm that your transport tool is 'healthy' by testing it in STMS. In SPAM in client 000 use the function Disassemble package and enter the package <Package name>.
5. Try to update the kernel if it not helps.
Best Regards
Niraj

Vehicle Scheduling Error:Error when creating transport structures in live C

HI Gurus,
We have one background job defined for Vehicle scheduling, which shows completed successfully but in log it says that :
: Error when creating transport structures in liveCache and Not possible to schedule shipment in the planning horizon.
My planning horizon is for 90 days from current date and demand horizon is for 30 days.
I have checked the VS profile and i dont find any problem with profile.
Can you please help me in finding what exaclty went wrong
Thanks,
AMol

Try This..
1. Open the crystal client on your local machine and import that particular report.
2. Do Database -> Verify Database. Then refresh the report on your PC and make sure that it returns data as expected.
3. Export it back to repository and try scheduling it again. You can verify through CMC for Crystal Reports under " Database Configuration" property to make sure it points to the right ODBC.
Let us know.

Error when creating a folder ,iviews in the portal

Dear sap gurus ,
I m facing a error when creating a Folder or an iview in my portal i'm using EP 7.0 sp11 ,The error is :
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.defaultFolderWizard
Component Name : com.sap.portal.admin.defaultwizards.DefaultFolderWizard
SQLException is not transient, error code = 1654, sql state = 72000 Batch rolled back. Caused by java.sql.BatchUpdateException: ORA-01654: unable to extend index SAPSR3DB.SYS_C004057 by 128 in tablespace PSAPSR3DB at oracle.jdbc.driver.DatabaseError.throwBatchUpdateException(DatabaseError.java:343) at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:10698) at com.sap.sql.jdbc.basic.BasicPreparedStatement.executeBatch(BasicPreparedStatement.java:263) at com.sap.sql.jdbc.oracle.Oracle10gPreparedStatement.executeBatch(Oracle10gPreparedStatement.java:100) at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeBatch(DirectPreparedStatement.java:1129) at com.sap.sql.jdbc.common.CommonPreparedStatement.executeBatch(CommonPreparedStatement.java:991) at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeBatch(StatementWrapper.java:270) at com.sapportals.portal.pcd.pl.AttributeHeadersTable.insert(AttributeHeadersTable.java:259) at com.sapportals.portal.pcd.pl.PlObject.save(PlObject.java:518) at com.sapportals.portal.pcd.pl.PlContext.createSubcontext(PlContext.java:544) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildOnPersistence(XfsContext.java:1374) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChildAndNotify(XfsContext.java:1128) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createChild(XfsContext.java:1087) at com.sapportals.portal.pcd.gl.xfs.XfsContext.createSubcontext(XfsContext.java:843) at com.sapportals.portal.pcd.gl.xfs.BasicContext.createBasicSubcontext(BasicContext.java:190) at com.sapportals.portal.pcd.gl.PcdPersContext.createSubcontext(PcdPersContext.java:191) at com.sapportals.portal.pcd.gl.PcdFilterContext.filterCreateSubcontext(PcdFilterContext.java:254) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:147) at com.sapportals.portal.pcd.gl.PcdGlContext.createSubcontext(PcdGlContext.java:440) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:624) at com.sapportals.portal.pcd.gl.PcdProxyContext.createSubcontext(PcdProxyContext.java:619) at com.sap.portal.admin.wizard.folderwizardpanes.SavePane.doAfterSubmit(SavePane.java:59) at com.sapportals.admin.wizardframework.core.WizardInstance.doPost(WizardInstance.java:356) at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:174) at com.sapportals.admin.wizardframework.core.WizardInstance.doWizard(WizardInstance.java:99) at com.sapportals.admin.wizardframework.AbstractDynamicWizard.doContent(AbstractDynamicWizard.java:98) 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) 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:645) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) 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:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) .
Exception id: 10:50_23/11/07_0005_16892850
See the details for the exception ID in the log file
Thanks and Regards,
sathya

Hi Sathya
The following line in your log tells you what is wrong:
ORA-01654: unable to extend index SAPSR3DB.SYS_C004057 by 128 in tablespace PSAPSR3DB
This is a configuration that you or the dba people need to do. The first thing I would check is if autoextend is on/off on your tablespace PSAPSR3DB. If it's 'off' you either need to put it to 'on' or manually extend the size of your tablespace depending on how much harddrvive space you have to play with. Here is a more detailed solution on how to do it:
Oracle Error : ORA-01654: unable to extend index string.string by string in tablespace string
Cause: Failed to allocate an extent of the required number of blocks for an index segment in the tablespace indicated.
Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
Br
Göran

Error when Creating a ServiceClientFactory instance JAVA API

When invoking Assembling a PDF document quick start I'm having a compilation error when creating a ServiceClientFactory instance:
//Create a ServiceClientFactory instance
ServiceClientFactory myFactory = ServiceClientFactory.createInstance(connectionProps);
The error is: The type com.adobe.idp.Context cannot be resolved. It is indirectly referenced from required .class files
All the required jars are a path.
What esle can be a problem ?
Thanks, Yan

Since you are using SOAP, you need to have the AXIS jars available. They are in the LiveCycle_ES_SDK\client-libs\thirdparty directory:
activation.jar (required for SOAP mode)
axis.jar (required for SOAP mode)
commons-codec-1.3.jar (required for SOAP mode)
commons-collections-3.1.jar (required for SOAP mode)
commons-discovery.jar (required for SOAP mode)
commons-logging.jar (required for SOAP mode)
dom3-xml-apis-2.5.0.jar (required for SOAP mode)
jaxen-1.1-beta-9.jar (required for SOAP mode)
jaxrpc.jar (required for SOAP mode)
log4j.jar (required for SOAP mode)
mail.jar (required for SOAP mode)
saaj.jar (required for SOAP mode)
wsdl4j.jar (required for SOAP mode)
xalan.jar (required for SOAP mode)
xbean.jar (required for SOAP mode)
xercesImpl.jar (required for SOAP mode)

Publish to portal error when creating a iview

hi gurus,
I have done complete BI-EP integration. SSO is also working fine. But when i publish a query from query designer to portal, i am geting a error when creating a iview for the query as show below.
Error:
Java system error: call FM RSRD_X_MAP_TO_PRTL_USERS_PROXY to ProgId EPD_PORTAL_B07 on host epdev with SSO not authorized: Authentication failed.
when i manually create a BI Query iview,its working fine but to create a iview from publish to portal in query designer it is througing me error.
Regards

yes i have used that tool,,,i am getting below error.
RED
Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
RED
Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018) Check Connector Connection of System Object in Portal System Landscape -
RED
Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination 'SAP_EP' Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway. -
RED
Calls from WebAS ABAP to WebAS Java will fail because the certificate of the BI mastersystem is not imported into J2EE ticket keystore Import the certificate to establish a trust relationship -
RED
The issuer DN of the imported ticket 'EPD_certificate' is the same as the issuer DN of SAPLogonTicketKeypair-cert Most likely, you are running an Add-In Installation. See note 917950, section 'Add-In Installation and importing Certificates with identical system ID (SID)' for details Display note 917950
I have checked everything,,but still geting red lights
Regards

Got Error when creating application server connection

Hi Guys...I am using SOA 10.1.3.1.0
I got the following error when creating application server connection
In Step 1:
I selected the Connection type as Standalone OC4J 10.1.3 (Why because I use this one)
In Step 2:
In this step I gave username and password (same username and password to connect to BPEL console)to authenticate connection
In step 3:
It is asking for Hostname, RMI port and URL path. My computer name is gopal-computer. I gave this hostname. RMI port number is 23791 by default. I kept this one as it is and URL path optional I think. I did not give any thing.
In step 4:
When I hit the test connection button its giving the following error
Error while getting remote MBeanServer for url: ormi://gopal-computer:23791/default:
Error reading application-client descriptor: Error communicating with server: Connection refused: connect; nested exception is:
javax.naming.CommunicationException: Connection refused: connect [Root exception is java.net.ConnectException: Connection refused: connect]
Please help me.
Thanks,
Gopal.....

For SOA Suite connection you should choose "Oracle application server 10g 10.1.3"

ESS Payslip : Error when creating a form

Hi Experts,
Please help me on this issue.
The payslip is not getting generated in QA portal. I have checked everything, feature, report variant. The payslip is getting generated from the back end.
But I have not checked from PZ11_PDF, becz of authorisation issue.
Can anyone guess what could be the problem?
thanks
Jay

Here is the error
Critical Error
A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
Please contact your system administrator.
Error when creating the form
Error when creating the form:com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Error when creating the form
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
     at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:122)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.reportBapiRet2Error(FcRepFramework.java:525)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcGetForm(FcRepFramework.java:394)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.processFollowingActions(FcRepFramework.java:484)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:378)
     at com.sap.xss.hr.rep.fcrfw.FcRepFramework.initModel(FcRepFramework.java:292)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFramework.initModel(InternalFcRepFramework.java:256)
     at com.sap.xss.hr.rep.fcrfw.FcRepFrameworkInterface.initModel(FcRepFrameworkInterface.java:136)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface.initModel(InternalFcRepFrameworkInterface.java:198)
     at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface$External.initModel(InternalFcRepFrameworkInterface.java:258)
     at com.sap.xss.hr.rem2.selection.VcRem2Selection.onInit(VcRem2Selection.java:245)
     at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2Selection.onInit(InternalVcRem2Selection.java:249)
     at com.sap.xss.hr.rem2.selection.VcRem2SelectionInterface.onInit(VcRem2SelectionInterface.java:161)
     at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface.onInit(InternalVcRem2SelectionInterface.java:144)
     at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface$External.onInit(InternalVcRem2SelectionInterface.java:220)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:593)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:865)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     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(AccessController.java:219)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Error when create client proxy in ABAP

Similar Messages

Maybe you are looking for