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

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!

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

Mobile Account Error Setting Up Leopard Client, createmobileaccount error.

Hi all. I posted this discussion under Portable Home Directories, but that is unfortunately a subcategory of Max OS X Server v10.4 Tiger and this is strictly a Leopard issues, so I'm reposting here.
Just following up on an earlier thread regarding mobile home accounts. Thought I'd post a new entry as the other one has been "answered".
I've just recently upgraded a slew of clients and a server to Leopard and have been trying to enable mobile accounts on existing network home accounts. When I set this as a Preference using Workgroup Manager, nothing happens on the clients. When I try to create a mobile account directly on the client while logged in as the network user, I get a standard error (The mobile account could not be created.) every time after it asks to log out and enter the user password in order to create the mobile account.
So, I followed the steps in this thread: http://discussions.apple.com/thread.jspa?threadID=1234051&tstart=0
For the account "leedale" logged in using a network home directory, entered the Terminal command as follows:
/System/Library/CoreServices/ManagedClient.app/Contents/Resources/createmobileac count -vsn leedale -h /Users/leedale
createmobileaccount built Oct 2 2007 22:44:49
verbose output on.
user name = "leedale"
home path = "/Users/leedale"
user password = "(null)"
prompt for password = FALSE
encrypt new home = FALSE
create as external account = TRUE
home sync new account = TRUE
sync URL = "(null)"
MCXCCacheMCXRecordAndGraph(): existingMCXRecord record setValues:forAttribute:dsAttrTypeNative:cachedauthpolicy == -14120 (Unable to set value(s) for dsAttrTypeNative:cachedauthpolicy in record leedale.)
MCXCCreateMobileAccount failed to create account. Error = -14120 (MCXCCacheMCXRecordAndGraph failed). Cleaning up mobile account record.
2007-11-18 17:15:19.831 createmobileaccount551:10b ### Error:-14120 File:/SourceCache/Admin/Admin-423/DSRecord.m Line:484
mobile account could not be created: -14120 (Unable to set value(s) for dsAttrTypeNative:cachedauthpolicy in record leedale.)
Any suggestions?

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

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

Error while creating new client

Hi,
recently i installed sap 4.7 in my system .
to create new client i copy the standard one and i assigned password .
While i am trying to login in to new client i am getting error "password is not right even though it is passsword given while creating new one.
can any explian me how to resolve this
regards
babu

Hi. welcome.
dont worry. cool.
some times due to eror uploads in data base theese type of error happens. put a mail to basis people of your company. they will solve ur issue/
thanks
karthik

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.

ORA-19202: Error occurred in XML processingLSX-00023: unknown namespace URI

Hi there
I am trying to register an XSD document as an XML schema on the database. I am using Oracle 9i release 9.2.0.5.0 and using the dbms_xmlschema.registerSchema method in PL/SQL.
I am getting the following error when trying to register:
ORA-19202: Error occurred in XML processing LSX-00023: unknown namespace URI
The problem seems to be caused by a local simpleType declared outside of the root element. If I remove the simpleType from the xsd, I can register it successfully as a schema on the database. However, we need the simpleType there as it defines valid values for one of the elements in the xsd.
The xsd follows the structure:
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema targetNamespace="http://www.oracle.com/VFLOC.xsd"
xmlns:vfloc="http://www.oracle.com/VFLOC.xsd"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xdb="http://xmlns.oracle.com/xdb">
     <xsd:element name="VisionDataExchange">
          <xsd:complexType>
               <xsd:sequence>
                    <xsd:element name="Credentials">
...... etc. etc.
               </xsd:element>
               </xsd:sequence>
          </xsd:complexType>
     </xsd:element>
     
     <xsd:simpleType name="TrueFalseType">
          <xsd:restriction base="xsd:string">
               <xsd:enumeration value="1"/>
               <xsd:enumeration value="0"/>
               <xsd:enumeration value="True"/>
               <xsd:enumeration value="False"/>
          </xsd:restriction>
          
     </xsd:simpleType>
</xsd:schema>
Does anyone know how I can register a schema with a targetNamespace and the local simpleType below?
Any help would be much appreciated.
Thanks!
Sonya

Hi
I wanted to know
1)Hw to register a schema
2) Associate xml files with the schema
3) hw to do read the xml files
If you could provide a small exampl, shall appreciate
Thanks for your help in advance
Sushil

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 Managed System in SMD

Hi,
we get the following error after trying to setup a new (Java)-System:
DataCollect Initial Data Collect ERROR for host xyz
Step DataCollect Details
Initial Data Collect ERROR for host xyz
!! Exception : An error occurred while uploading the Configuration Data from host [xyz] !(cause=java.lang.Exception [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz])
Exceptions
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: An error occurred while uploading the Configuration Data from host [xyz] !
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:72)
at com.sap.sup.admin.scheduler.config.DataCollect.execute(DataCollect.java:138)
at com.sap.sup.admin.setup.AppCfgTasks.runInitialDataCollect(AppCfgTasks.java:57)
at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:348)
at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:304)
at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:736)
at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:28)
at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:1000)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: [DataCollectorClientUtil_xyz] Error collecting initial configuration files on host [xyz]
at com.sap.smd.agent.plugins.datacollector.util.DataCollectorClientUtil.collectInitialConfigurationData(DataCollectorClientUtil.java:315)
at com.sap.sup.admin.scheduler.task.remote.config.InitialConfigGatherTask.process(InitialConfigGatherTask.java:67)
... 8 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: [DataCollector] Error during collectInitialConfigurationData() on host [xyz]; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:684)
at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
... 1 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
... 5 more
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
... 7 more
in file SMDAgentApplication.0.log of the server, that hosts the system and the SMD agent, I get:
Nov 27, 2008 2:22:57 PM [Thread[Thread-25,5,main]] Error      DataCollectorService@40c5f303: collectInitialConfigurationData()
[EXCEPTION]
com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: Error installing template files in the working directory; nested exception is:
     com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:792)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:710)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.collectInitialConfigurationData(DataCollectorService.java:654)
     at com.sap.smd.agent.plugins.datacollector.DataCollectorServicep4_Skel.dispatch(DataCollectorServicep4_Skel.java:290)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.DispatchImpl.run(DispatchImpl.java:716)
     at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.smd.agent.plugins.datacollector.exc.RemoteDataCollectException: No cca_systemlandscape.xml file found
     at com.sap.smd.agent.plugins.datacollector.DataCollectorService.installTemplateFiles(DataCollectorService.java:766)
     ... 7 more
Nov 27, 2008 2:23:03 PM [Thread[Thread-35,5,main]] Warning    com.sap.smd.wily.hostagent.action.SapOsColAction - launchDaemon(): launchDaemon: saposcol exited with -1
the mentioned cca_systemlandscape.xml that should be located in usr\sap\SMD\J98\SMDAgent\applications.config\com.sap.smd.agent.application.datacollector is 0 byte.
where should this file be generated/has its source?
kr, achim

Helpfull notes:
987835 - How to define Solutions in SMSY for Diagnostics
986350 - SM Diagnostics: "Monitored setup" fails during data collect

Exchange 2010 - Error setting a new transport rule for email disclaimer

Hi
Trying to setup some additional email disclaimer rules on Hub transport under Org Config on exchange 2010. We allready have a few and they work ok, however we are trying to replace this woth some alternate ones and are getting the error
The length of the property is too long. the maximum length is 8192 and the length of the value provided is 8522.
Most of this length comes from the html code we are inserting into the disclaimer. I've reduced it by about as much as i can but it's still too large. Does anybody have any suggestions or know if it;s possible to increase the 8192 sixze limit ?
Regards
Roger

Hi Roger,
For AD replication packet the ideal size is 8K. Or the above error may occur due to build/design issues.
You can eliminate this size related issue by splitting the large rule into multiple rules. This size limit is Per Rule and does not add up for all rules.

Client proxy generation in NWDS with external web service

Hello,
- I try to generate a client proxy in NWDS (7.0 SP12) from a wsdl which includes a complexType and which is non-SAP.
Wizard Procedure in NWDS: New client proxy definition > i select WSLD source = URL (it is same symptom with local file) > Then i fill URL > Proxy definition window: i see URI and package filled with value of complexType in wsdl file.
When i click on Finish, wizard generates some file on OS but there is error pop-up "Problems while generating the Proxy Definition".
NB.
Same procedure with a similar wsdl without complexType works well .
Objective is to use this proxy at SAP portal level.
- Main errors in NWDS logs:
Caused by: java.lang.Exception: WSDL part points to unavailable type with qname:
so, does anyone has encoutner this issue ? and also does complex type is supported ?!
(Notes that wsdl format is correct and if i remove "wsdl:type" portion and references, client proxy is correctly
created in NWDS.)
Thanks for help! Regards, Frédéric

Hi,
Complex types are supported but I am not sure if complextype with sequence is supported. See note: Incorrect field sequence with group SAP Note Number: 813545 (not sure if it is applicable to you as you are on NWSD 7.0 SP12).
Another note: SAP Note Number: 1266761
I suggest try to remove "sequence" and then try again.
Regards,
Gourav

Client Proxy(WSDL file) via Se80

Hello
We have a client proxy created against a WSDL file (http/url) in SE80 and we are using it currently it.
Now the WSDL file is going to change a little. I want to use the same client proxy and only change the WSDL file with the new WSDL file? How can i acheive this?
I can create a new client proxy and associate WSDL file but i need to change a lot of place in code where we create instances of this abap proxy class.Hence i want to reuse the same client proxy while changing the WSDL file alone.
Any guidance or pointers will be greatly appreciated.
Thanks
Abishek

Hi Stuart,
Cool. This solves my issue. If I choose the "regenerate" button(see attached image) then I am prompted to enter a new WSDL URL or file.
Thanks!
Regards, Yashu

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

Error setting up new client proxy, unknown namespace

Similar Messages

Maybe you are looking for