HTTP/1.1 500 Internal Server Error

[Former Member]

I have created a service on our ECC Dev system, however, I'm having problems calling it. I am passing in the following:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ukms="http://det.nsw.edu.au/FI/COMMON/UKMS">
   <soapenv:Header/>
   <soapenv:Body>
      <ukms:LookupValues>
         <!--1 or more repetitions:-->
         <Values>
            <SourceScheme>F0401.A6AN8</SourceScheme>
            <SourceAgency>JDE.VENDOR</SourceAgency>
            <SourceValue>1001</SourceValue>
            <TargetScheme>LFA1.LIFNR</TargetScheme>
            <TargetAgency>SAP.VENDOR</TargetAgency>
            <!--Optional:-->
            <TargetValue>?</TargetValue>
         </Values>
      </ukms:LookupValues>
   </soapenv:Body>
</soapenv:Envelope>

And getting the following response:

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
   <soap-env:Header/>
   <soap-env:Body>
      <soap-env:Fault>
         <faultcode>soap-env:Server</faultcode>
         <faultstring xml:lang="en">CX_ST_MATCH_ELEMENT:XSLT exception.System expected end of element '{http://det.nsw.edu.au/FI/COMMON/UKMS}LookupValues'</faultstring>
         <detail>
             ns:SystemFault xmlns:ns="http://www.sap.com/webas/710/soap/runtime/abap/fault/system/">
               <Host>undefined</Host>
               <Component>APPL</Component>
               <ChainedException>
                  <Exception_Name>CX_SOAP_CORE</Exception_Name>
                  <Exception_Text>CX_ST_MATCH_ELEMENT:XSLT exception.System expected end of element '{http://det.nsw.edu.au/FI/COMMON/UKMS}LookupValues'</Exception_Text>
               </ChainedException>
               <ChainedException>
                  <Exception_Name>CX_SXMLP</Exception_Name>
                  <Exception_Text>XSLT exception</Exception_Text>
               </ChainedException>
               <ChainedException>
                  <Exception_Name>CX_ST_MATCH_ELEMENT</Exception_Name>
                  <Exception_Text>System expected end of element '{http://det.nsw.edu.au/FI/COMMON/UKMS}LookupValues': Main Program:/1SAI/TXS2D61C2F956CD2F49B6C2| Program:/1SAI/TXS2D61C2F956CD2F49B6C2| Line:187| Valid:X</Exception_Text>
               </ChainedException>
            </ns:SystemFault
 
            ...

         </detail>
      </soap-env:Fault>
   </soap-env:Body>
</soap-env:Envelope>

[Former Member · Accepted solution]

How you are testing?

Try passing following:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ukms="http://det.nsw.edu.au/FI/COMMON/UKMS/">

<soapenv:Header/>

<soapenv:Body>

<ukms:LookupValues>

<!1 or more repetitions:>

<Values>

<SourceScheme>F0401.A6AN8</SourceScheme>

<SourceAgency>JDE.VENDOR</SourceAgency>

<SourceValue>1001</SourceValue>

<TargetScheme>LFA1.LIFNR</TargetScheme>

<TargetAgency>SAP.VENDOR</TargetAgency>

<!Optional:>

<TargetValue>?</TargetValue>

</Values>

</ukms:LookupValues>

</soapenv:Body>

</soapenv:Envelope>

Note additional "/" after "http://det.nsw.edu.au/FI/COMMON/UKMS"

Regards,

Gourav

[Former Member]

Hey guys,

It's been a while since I last replied but this issue was temporarily put on hold.

I've tried everything that has been suggested without any luck.

Is there something Im missing?

I must admit, we started to get this problem following the upgrade to our ECC Dev system. The same service on our ECC test system works fine.

Here is a quick comparison of the main components on our two systems:

ECC DEV:

SAP_ABA 701 6 SAPKA70106 Cross-Application Component

SAP_BASIS 701 6 SAPKB70106 SAP Basis Component

PI_BASIS 701 6 SAPK-70106INPIBASIS Basis Plug-In

ST-PI 2008_1_700 2 SAPKITLRD2 SAP Solution Tools Plug-In

SAP_BS_FND 701 6 SAPK-70106INSAPBSFND SAP Business Suite Foundation

SAP_BW 701 6 SAPKW70106 SAP Business Warehouse

SAP_AP 700 19 SAPKNA7019 SAP Application Platform

WEBCUIF 700 6 SAPK-70006INWEBCUIF SAP WEBCUIF 700

SAP_APPL 604 6 SAPKH60406 Logistics and Accounting

SAP_HR 604 21 SAPKE60421 Human Resources

...

ECC TEST

SAP_ABA 701 3 SAPKA70103 Cross-Application Component

SAP_BASIS 701 3 SAPKB70103 SAP Basis Component

PI_BASIS 701 3 SAPK-70103INPIBASIS Basis Plug-In

ST-PI 2008_1_700 0 - SAP Solution Tools Plug-In

SAP_BS_FND 701 2 SAPK-70102INSAPBSFND SAP Business Suite Foundation

SAP_BW 701 3 SAPKW70103 SAP Business Warehouse

SAP_AP 700 15 SAPKNA7015 SAP Application Platform

WEBCUIF 700 2 SAPK-70002INWEBCUIF SAP WEBCUIF 700

SAP_APPL 604 2 SAPKH60402 Logistics and Accounting

SAP_HR 604 5 SAPKE60405 Human Resources

...

Thanks,

Krishneel

[Former Member]

Check your system proposed endpoint URL.

You will get something like: http:/<hostname>:port/path suffix.

Now go to txn SICF in ECC and check in the path suffix. drill down to the last node and see if the service is active there.

[Former Member]

Hi Trevor,

Yep I dont think the problem is with the SOAP request as it works fine when I call the same service on our QA system.

I did create an endpoint using SOAMANGER and am using the URL I get from the window that opens up when I click on "Open WSDL document for selected binding"

Krishneel

[Former Member]

Are you not perhaps running a different ECC version in the QA environment?

Check if SAP Note 1229799 doesn't apply in your case.

Regards, Trevor

Also, would it be possible to put the contents of your WSDL here, I can maybe test it from my side?

Edited by: Trevor Naidoo on May 27, 2010 10:38 AM

[Former Member]

Hi Praveen, the Web Service is on our ECC system. There is no WebService Navigator since the ECC system has no Java Engine.

[Former Member]

Hi Krishneel,

You can configure Java Engine of PI and use in the ECC.

From ECC, trasaction SOAMANAGER, goto Technical Configuration tab>System Global Settngs>Access Information J2EE server tab. Add hostname and port of PI system java engine.

Regards,

Praveen.

[Former Member]

Hi Krishneel,

I don't thing the issue is with your SOAP request as such, that looks fine. Did you configure an endpoint for the webservice using TCode SOAMANAGER?

If you didn't, do that & use the URL/WSDL of the binding you've created to test through SoapUI. If you can access WS Navigator & test it, it should work fine. If it's not working through SoapUI it could be because of an endpoint binding.

Regards, Trevor

[Former Member]

I'm testing the web service using SOAP UI.

Gourav, I tried what you suggested but I still get the same error:

Edited by: Krishneel Goundar on May 26, 2010 9:30 AM

[Former Member]

Hi Krishneel,

Could you please check the same in WebService Navigator tool .. http://<hostname>:<portno>/wsnavigator

Some times in SOAP UI, it may through this error if variables are not initialised properly.

Hope this will help.

Regards,

Praveen