Error in creation of client proxy.

Hello all,
I try to consume a webservice in SAP ABAP. When i create the service consumer proxy it is giving an error message llike
"Incorrect value: Unknown QName http://wholesale...........................sendeWholesaleMeldungRequest"
Have anyone come across this error scenario.
I m using SAP ECC 6.0.
Regards
Sandep.

Hi Sandeep,
--->While creating client Proxy object to consume the webservice a pop will raise with 4 radio buttons options,i think you had selected any one of that depending upon your requirement,rite,If not do that and try.
-->If you have the WSDL file in your local system select the Radio Button WSDL and import it into your Client Proxy.
-->Also create the Logical Port.
Thanks

Similar Messages

Error while creating a client proxy for CBR.RU

Hi!
I need to consume web service. Here is the link: http://www.cbr.ru/DailyInfoWebServ/DailyInfo.asmx?WSDL
I tried to make an own client proxy with SE80 transaction. (edit object->enterprise services -> client proxy -> create) After completing wizard an error occurs with text:
Incorrect value: Unknown Namespace http://www.w3.org/2001/XMLSchema
The same schema works perfecrly with this web service:
http://www.deeptraining.com/webservices/wsStrings.asmx?WSDL
In this case proxy class is created with no errors and everything is fine.
Could anybody let me know what's the reason of such bug, please? I'm not competent with XML schemas so it's kind of difficult to understand what's wrong with WSDL file from CBR.RU

Late response I know, but I have solved a similar problem recently and thought I would share.
Firstly, the problem is not with the namespace. The "Namespace ..." part is just stating the namespace the "Incorrect Value" has. So this error is complaining about the value "Unknown" - which isn't very helpful.
It appears the SAP SE80 importer does not like elements like the following because it can't understand <s:element ref="s:schema" />. It appears this is a common thing to be included in .NET generated WSDLs.
<s:element minOccurs="0" maxOccurs="1" name="GetCursDynamicResult">      <s:complexType>          <s:sequence>               <s:element ref="s:schema" />               <s:any />          </s:sequence>     </s:complexType></s:element>
SAP will also not like this example as it does not support mixed content (see: http://www.w3schools.com/schema/schema_complex_mixed.asp)
<s:element minOccurs="0" maxOccurs="1" name="SaldoXMLResult">
     <s:complexType mixed="true">
          <s:sequence>
               <s:any />
          </s:sequence>
     </s:complexType>
</s:element>
You can "Fix" the problem in both cases by removing the offending text in a local copy of the WSDL file so remove line 4 in the first example and change line 2 in the second to <s:complexType> the proxy can then be generated. No idea if the resulting service will be fully operational though!

Error while deploying Java Client Proxy

Hi Experts,
I developed a java client proxy.Since i do not have access to visual administrator, i uploaded the ear file to a folder in the XI box and asked the basis folks to deploy it.
On trying to deploy it on to the server they got the following error.
Details:
========
1) Error loading archive
    /usr/sap/XS1/put/R3Ear.ear
    (server side name is: /usr/sap/XS1/put/R3Ear.ear)
    com.sap.sdm.util.sduread.IllFormattedSduFileException: Error during attribute reading: received exception: invalid stored block lengths
What could be the reason for the error?

Hi
recreate your ear file and try to redeploy it.
it could be a zipping problem
Regards
Vishnu

Error in receiver determination - Client proxy to IDOC using PI-IS

Hi,
I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I am using the standard SAP message interface in the sproxy.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
Thanks,
Menaga

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
The above error occurs due to:
1) You have configured a wrong receiver service in the Receiver Determination
2) You have configured the correct receiver but the cache is not updated
So check if the receiver service exists and the cache is updated.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
be created without DT".
Check if you get any lead from this thread:
Failed to time to generate proxy - TRX SPROXY
Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
Regards,
Abhishek.

Unknown namespace error when generating a client proxy

We are using WAS 7.0 and I'm trying to generate a client proxy for an inhouse webservice via Object Navigator (SE80). When using the Wizard I get an error message from the Librabry Handler saying: "Unknown namespace: http://schemas.xmlsoap.org/soap/encoding".
A check by the colleagues who provide this Webservice says that the wsdl is ok.
Any idea for this error message?
Many Thanks.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:intf="http://saphrmitarbeiterdaten.de.tnt.com" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<wsdl:types>
<schema targetNamespace="http://saphrmitarbeiterdaten.de.tnt.com" xmlns="http://www.w3.org/2001/XMLSchema">
   <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
   <complexType name="SAPHRMitarbeiterDatenMitarbeiter">
    <sequence>
     <element name="Bukrs" nillable="true" type="xsd:string"/>
     <element name="Werks" nillable="true" type="xsd:string"/>
     <element name="Kostl1" nillable="true" type="xsd:string"/>
     <element name="Kostl2" nillable="true" type="xsd:string"/>
     <element name="Persk" nillable="true" type="xsd:string"/>
     <element name="Pernr" nillable="true" type="xsd:string"/>
     <element name="Nachn" nillable="true" type="xsd:string"/>
     <element name="Vorna" nillable="true" type="xsd:string"/>
     <element name="Eintr" nillable="true" type="xsd:string"/>
     <element name="Austr" nillable="true" type="xsd:string"/>
     <element name="Sacha" nillable="true" type="xsd:string"/>
     <element name="Sachn" nillable="true" type="xsd:string"/>
     <element name="IAKen" nillable="true" type="xsd:string"/>
     <element name="IABeg" nillable="true" type="xsd:string"/>
     <element name="IAEnd" nillable="true" type="xsd:string"/>
     <element name="Level" nillable="true" type="xsd:string"/>
     <element name="Stelle" nillable="true" type="xsd:string"/>
     <element name="Abtlg" nillable="true" type="xsd:string"/>
     <element name="Mgr_Pernr" nillable="true" type="xsd:string"/>
     <element name="Mgr_Name" nillable="true" type="xsd:string"/>
    </sequence>
   </complexType>
   <complexType name="ArrayOfSAPHRMitarbeiterDatenMitarbeiter">
    <complexContent>
     <restriction base="soapenc:Array">
      <attribute ref="soapenc:arrayType" wsdl:arrayType="impl:SAPHRMitarbeiterDatenMitarbeiter[]"/>
     </restriction>
    </complexContent>
   </complexType>
</schema>
</wsdl:types>
   <wsdl:message name="ReadDataResponse">
      <wsdl:part name="ReadDataReturn" type="impl:ArrayOfSAPHRMitarbeiterDatenMitarbeiter"/>
   </wsdl:message>
   <wsdl:message name="ReadDataRequest">
      <wsdl:part name="in0" type="xsd:string"/>
      <wsdl:part name="in1" type="xsd:string"/>
      <wsdl:part name="in2" type="xsd:string"/>
      <wsdl:part name="in3" type="xsd:string"/>
   </wsdl:message>
   <wsdl:portType name="SAPHRMitarbeiterDatenRead">
      <wsdl:operation name="ReadData" parameterOrder="in0 in1 in2 in3">
         <wsdl:input message="impl:ReadDataRequest" name="ReadDataRequest"/>
         <wsdl:output message="impl:ReadDataResponse" name="ReadDataResponse"/>
      </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="SAPHRMitarbeiterDatenReadSoapBinding" type="impl:SAPHRMitarbeiterDatenRead">
      <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="ReadData">
         <wsdlsoap:operation soapAction=""/>
         <wsdl:input name="ReadDataRequest">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:input>
         <wsdl:output name="ReadDataResponse">
            <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://saphrmitarbeiterdaten.de.tnt.com" use="encoded"/>
         </wsdl:output>
      </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="SAPHRMitarbeiterDatenReadService">
      <wsdl:port binding="impl:SAPHRMitarbeiterDatenReadSoapBinding" name="SAPHRMitarbeiterDatenRead">
         <wsdlsoap:address location="http://194.55.55.58:7001/SAPHRMitarbeiterDatenWebservice/services/SAPHRMitarbeiterDatenRead"/>
      </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Hi Michael,
the use of soapenc:Array is not supported. There are other ways to declare arrays:
-In a DESCRIPTION, array declarations MUST NOT extend or restrict the soapenc:Array type.
-In a DESCRIPTION, array declarations MUST NOT use wsdl:arrayType attribute in the type declaration.
-In a DESCRIPTION, array declaration wrapper elements SHOULD NOT be named using the convention ArrayOfXXX.
-A MESSAGE containing serialized arrays MUST NOT include the soapenc:arrayType attribute.
So you need to copy the WSDL file to a local file and edit it, afterwards, use it to generate the proxy.
Maybe you should have a look at the following url:
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272
I hope this will help you to solve the problem.
Edited by: Duhan Bernhard on Nov 7, 2008 12:29 PM

Error When Creating Deployable Client Proxy

I've created a WSDL file from the XI Integration Directory (Tools--> Define Web Service). I then tested this with XMl Spy and VB.NET. They worked fine.
I then used NWDS (SP13) to create a deployable client proxy. When building the client definition NWDS returned the error <b>"Problem When Generating the Proxy Definition!".</b>
1. Are there any log files that would be helpful in deciphering the error message?
2. Should I take this one to SAP. The WSDL is rather long and complex but it is based on XSD from a large national project and the other tools seem to be able to handle it fine.
Thanks!

Hi Paul,
What adapter you havwe used in XI for this?
It should be SOAP adapter.
Regards,
Bhavik

Error setting up new client proxy, unknown namespace

Hi all.
I am trying to setup a new client proxy, with SE80.
I am using an WSDL file.
Somehow I get the following error.
Proxy-Generierung: Fehler aufgetreten
Exception occurred in library handler
Incorrect value: Unknown Namespace http://www.mynamespace.com/param
Anyone have any ideas why? Does namespace need to contain specific values?
Thanks!

Hi,
The namespace you are using for creating client proxy might not be available for consumption(i.e. it might not be published) or there is no connectivity to the source system so namespace is not available.
Try checking connection.
Hoping it helps..
Regards,
Komal
Edited by: Komal Lakhwani on Feb 8, 2010 4:31 PM

Creation of client proxy for a WSDL with 2 port types??

Hi,
I am trying to consume an external web service from SAP - ECC6.0. The WSDL file has 2 porttype definitions - one for i/p and one for o/p
When I proceed with SE80 to create a client proxy, it asks me to select any one port type to generate the client proxy. If I select only the input port, it generates proxy for the input port alone.
In this scenario, how do I create proxies and configure logical ports, and call it from a single program to invoke the whole web servie with both i/p and o/p?
TIA,
Regards
Deepthi

Hi,
i. Import your message schemas from external definitions, or RFCs or IDocs from SAP systems. These definitions already contain data types.
ii. Create a message interface and reference the messages of the external definition, or the RFC or IDoc message.
Check this, it may help you
http://help.sap.com/saphelp_nw04/helpdata/en/3f/01623c4f69b712e10000000a114084/content.htm
REgards
Seshagiri

Creation of client proxy out of WSDL?

Hi ,
I need help in creating client proxy out of WSDL. It would be very helpful if someone lets me know the usage of performing this .I'm not much familiar with web services.
Regards,
Christina.

Hi,
right click on your package
create --> Enterprise Service / Web Service --> Proxy Object
-> URL/HTTP destination
-> Specify WSDL URL
Sometimes naming conficts occur.
Save and activate the proxy.
And then you have to call the proxy from a client application
regards

Error in client proxy generation

Hi experts,
                I am trying to consume a web-service from an ABAP progam, to do this I create an Enterprise Service Client Proxy. But creation of the proxy fails with the error message
"Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/ .
      For client confidentiality issues I cannot put the wsdl file or its content on the thread but I can provide certain details of the code which you might wish to see.
Also my wsdl contains messages with miltiple parts.Is this also a trouble while generating the proxies in ABAP ?
Are these two problems related?
Can I find a link precisely which can provide a kind of checklist to see that these steps have to be followed or these conditions have to be met by wsdl for generation of client proxies in ABAP?
Any pointers will be useful.
Thanks and Regds
Abhishek

Hi Anton,
              I will provide you some piece of the file which might help you in analysing the problem....
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="http://www.abc.com"
xmlns:s1="http://www.abc.com/AbstractTypes"
xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="http://www.abc.com"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <s:schema targetNamespace="http://www.abc.com/AbstractTypes">
      <s:import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
      <s:complexType name="StringArray">
        <s:complexContent mixed="false">
          <s:restriction base="soapenc:Array">
            <s:sequence>
              <s:element minOccurs="0" maxOccurs="unbounded" name="String" type="s:string" />
            </s:sequence>
          </s:restriction>
        </s:complexContent>
      </s:complexType>
    </s:schema>
Similarly the WSDL has messages with multiple parts like:
<wsdl:message name="GetReleasedGenericDrawing2DHttpGetIn">
    <wsdl:part name="DocumentNo" type="s:string" />
    <wsdl:part name="SheetNo" type="s:string" />
    <wsdl:part name="ClassName" type="s:string" />
</wsdl:message>
If you need some ther details from the file please let me know. I have cross checked that it is using a Document/literal style so it should not be a problem.
I have gone through the SAP note (944029) for the list some forbidden keywords which were a problem prior to release of SP 16 .We dont have even that problem.
This thing is very new to me ....please let me know if you wnat some other detail for analysis.
Regads
Abhishek

Web Service - Client Proxy generation error

Hi All,
I tried creating a client proxy using an URL provided to me and followed the steps using the wizard. I end up in getting the following error messages. Could anyone throw some light on resolving this? I do not have any idea about what WSDL is. Any help is highly appreciated. Not able to attach the WSDL code here.
Below is the error message upon client proxy creation:
Proxy-Generierung: Fehler aufgetreten
Exception occurred in library handler
Not implemented
Thanks
Srini
Edited by: Srinivasan Karunakaran on Oct 22, 2010 11:11 PM

Resolved through SAP Help. Refer SAP note# 0001403271.

ABAP client proxy create error

Hi,
When I try to create a client proxy web service (se80), I get the error "Error when creating HTTP client: URL: Error:Connection Parameters (Host or Service) Not Availa Message no. SPRX137"
I want to consume a web service (by reading a wsdl from an url) from my own network. the ICM seems to work fine.
Any ideas?
thanks,
Raymond Does

Hi Praveen,
Actualy I am not using XI. I would like to connect to the web service by creating a client proxy and then calling the web service with an ABAP program.
I that case, do I have to do the SPROXY settings as well?
While debugging the creation of the client proxy I saw that the urls to the wsdl and xsd files (my wsdl is refering to them) did not have the complete http://..etc.. text but only the last part (like 'SystemGetInfo.wsdl'). It seems that the client proxy generation program cannot handle this url data.
Please let me know what to do.
Regards,
Raymond

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

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 while generating client proxy

Hi All,
I have got a WSDL file for which I am generating the client proxy. It is giving me a dump saying that, memory is not sufficient while generating the proxy.
I have also contacted the basis team, even after increasing the memory... we are facing the same issue. Can anyone suggest any solution or SAP Note if there are any???
Thanks in advance.
Bhargava.

Hi,
Please find the dump details below:
ST22 DUMP:
Short text
    No storage space available for FORM stack.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Try to find out (e.g. by targetted data selection) whether the
    transaction will run with less main memory.
    If there is a temporary bottleneck, execute the transaction again.
    If the error persists, ask your system administrator to check the
    following profile parameters:
    o ztta/roll_area            (1.000.000 - 15.000.000)
           Classic roll area per user and internal mode
           usual amount of roll area per user and internal mode
    o ztta/roll_extension       (10.000.000 - 500.000.000)
           Amount of memory per user in extended memory (EM)
    o abap/heap_area_total      (100.000.000 - 1.500.000.000)
           Amount of memory (malloc) for all users of an application
           server. If several background processes are running on
           one server, temporary bottlenecks may occur.
           Of course, the amount of memory (in bytes) must also be
           available on the machine (main memory or file system swap).
           Caution:
           The operating system must be set up so that there is also
           enough memory for each process. Usually, the maximum address
           space is too small.
           Ask your hardware manufacturer or your competence center
           about this.
           In this case, consult your hardware vendor
    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each dialog process.
    Parameters for background processes:
    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)
           Restriction of memory allocated to the heap with malloc
           for each background process.
    Other memory-relevant parameters are:
    em/initial_size_MB:         (35-1200)
           Extended memory area from which all users of an
           application server can satisfy their memory requirement
Error analysis
    You attempted to extend a stack, but the required storage spac
    not available.
    Storage request..............: 8450048 bytes.
How to correct the error
    Please check whether uncontrolled recursive calls caused this
    runtime error.
    Try to decide by analysis whether this request is
    reasonable or whether there is a program error. You should pay
    particular attention to the internal table entries listed belo
System environment
    SAP-Release 701
    Application server... "dcr"
    Network address...... "10.1.105.112"
    Operating system..... "AIX"
    Release.............. "6.1"
    Hardware type........ "00C834224C00"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 4

Error in creation of client proxy.

Similar Messages

Maybe you are looking for