Soap runtime error

Hi All,

Anyone can help us on these error message during ADS testing.

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Message no. FPRUNX001

Diagnosis

An error occurred when Adobe Document Services (ADS) was launched.

System Response

Error message

Procedure

When troubleshooting, follow the steps described in SAP Note 944221.

First check the connection to ADS. You can use the program FP_PDF_TEST_00 to do this. From SAP NetWeaver Release 7.0, the program FP_CHECK_DESTINATION_SERVICE must also run successfully (both with and without the checkbox selected on the selection screen). If this program does not run successfully, there is a error in the configuration.

We try the note 944221 and also this link procedure on how to activate Adobe Document Services

http://scn.sap.com/community/netweaver-administrator/blog/2014/03/12/ads-installation-and-configuration-in-nw73-or-higher

The error message appear during our test the following via SA38

FP_TEST_00

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Message no. FPRUNX001

Diagnosis

An error occurred when Adobe Document Services (ADS) was launched.

System Response

Error message

Procedure

When troubleshooting, follow the steps described in SAP Note 944221.

First check the connection to ADS. You can use the program FP_PDF_TEST_00 to do this. From SAP NetWeaver Release 7.0, the program FP_CHECK_DESTINATION_SERVICE must also run successfully (both with and without the checkbox selected on the selection screen). If this program does not run successfully, there is a error in the configuratio

Here’s also the other error message during performing the program test

FP_PDF_TEST_00

SYSTEM ERROR: SOAP Framework error: SOAP Runtime Exception: CSoapExceptionTransport : HTTP receive failed with exception communicati

on_failure (100.101).

Exception of class CX_FP_RUNTIME_INTERNAL

And also the other programs test

FP_CHECK_DESTINATION_SERVICE

FP_TEST_IA_01

Anyone can help us on this?

Appreciate your help.

Thank you in advance.

Erwin

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Anyone can help us on these error message during ADS testing.

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Message no. FPRUNX001

Diagnosis

An error occurred when Adobe Document Services (ADS) was launched.

System Response

Procedure

When troubleshooting, follow the steps described in SAP Note 944221.

First check the connection to ADS. You can use the program FP_PDF_TEST_00 to do this. From SAP NetWeaver Release 7.0, the program FP_CHECK_DESTINATION_SERVICE must also run successfully (both with and without the checkbox selected on the selection screen). If this program does not run successfully, there is a error in the configuration.

We try the note 944221 and also this link procedure on how to activate Adobe Document Services

The error message appear during our test the following via SA38

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Message no. FPRUNX001

Diagnosis

An error occurred when Adobe Document Services (ADS) was launched.

System Response

Procedure

When troubleshooting, follow the steps described in SAP Note 944221.

First check the connection to ADS. You can use the program FP_PDF_TEST_00 to do this. From SAP NetWeaver Release 7.0, the program FP_CHECK_DESTINATION_SERVICE must also run successfully (both with and without the checkbox selected on the selection screen). If this program does not run successfully, there is a error in the configuratio

Here’s also the other error message during performing the program test

Источник

ADS: SOAP Runtime Exception: CSoapExceptionTransport :(100101)

Popular Topics in SAP

Have you set Destinations services at Java Visual Admin.

Did you configure ADS correctly ?

Hi
Try the adobe document configuration guide
Hilik

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

Print or Display PDF Based Forms within Preview

You want to activate or output a PDF form and receive an error message. You cannot print or display forms in the preview or generate or edit interactive forms, or these processes are defective.

It may occur becuase of:

Possible causes are that the configuration of Adobe document services is incorrect, there are errors in the form or the printer configuration is incorrect.

Solution:

For the printing or the print preview of PDF-based forms, you require a PCL-Postscript printer or a ZPL printer and you must use a relevant device type (for example, POST2, HPLJ4, HP9500, PDF1, AZPL203, AZPL300).

For more information, see 685571 and under «Printing PDF-Based Forms» in the SAP Print Handbook (BC-CCM-PRN). See SAP Help Portal under:

www.help.sap.com/saphelp_nw70/helpdata/de/25/6fa8fd27837846990a7a6813b06f80/frameset.htm

If you want to use a printer with the device type SAPWIN/SWIN, read 1444342.

To generate interactive forms, you require a credential, which you must register as described in the Adobe Configuration Guide.

Contents

In order to find the cause of the error, proceed as follows (depending on the scenario that you use): Note that you require administration authorization for some steps.

I ABAP:

1. Test program FP_TEST_00
2. Test program FP_PDF_TEST_00, RFC connection to ADS
3. Testing the user and password
4. Test destination service
5. Interactive forms: Test program FP_TEST_IA_01 (credential test)
6. Generated PDF with additional information
7. Activating ADS trace on the J2EE Engine

II Web Dynpro for ABAP

1. Test program FP_TEST_00
2. Test program FP_PDF_TEST_00, RFC connection to ADS
3. Testing the user and password
4. Test destination service
5. Interactive forms: Test program FP_TEST_IA_01 (credential test)
6. Generated PDF with additional information
7. Activating ADS trace on the J2EE Engine

II Web Dynpro for Java

1. Testing the user and password
2. Check whether the credential is installed and configured.
3. Generated PDF with additional information
4. Activating ADS trace on the J2EE Engine

I ABAP:

The following test steps are also described on SAP Help Portal in the chapter «Configuration Check for PDF-Based Forms in ABAP»
of the Adobe Document Services Configuration Guide:

SAP NetWeaver 7.0, 7.01, 7.02:

www.help.sap.com/saphelp_nw70/helpdata/en/43/f31e3082221595e10000000a1553f7/frameset.htm

SAP NetWeaver 7.1 and higher:

www.help.sap.com/saphelp_nw73/helpdata/en/4b/94e945ea576e82e10000000a421937/frameset.htm

1. Use transaction SA38 to execute the program FP_TEST_00.

If the FP_TEST_00 form is displayed in the print preview, the ADS configuration is correct.

-> If you use scenarios with an interactive PDF, proceed with point 5. Otherwise, proceed with the test under point 6.

If the system displays an error message instead of a form, the configuration of ADS is incorrect.

-> Carry out the additional tests from point 2 onwards.

2. Use transaction SA38 to execute the program FP_PDF_TEST_00.

This enables you to check the RFC connection to ADS .

If the system displays the version number of ADS, the configuration of the RFC connection is correct.

-> Proceed to point 4.

You receive one of the following error messages:

2.1. If the system displays dialog fields for user and password instead of the version number, the entries for user and password in the RFC connection do not match the entries in user management.

-> Check the user and the password. Continue with point 3.

2.2. The system displays a «SYSTEM ERROR» with the following text:

«ERROR CODE: 100.101»

«ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code»

«ERROR MESSAGE : SOAP Runtime Exception: CSoapExceptionTransport : HTTP receive failed with exception communication_failure»

-> Contact your system administrator and ask them to check or correct the details for target device, service number and path prefix in the RFC connection (transaction SM59).

If all of these entries are correct and the problem still persists, you should check whether the J2EE Engine is started correctly. Read 1587941 also.

2.3. If the system displays an error message stating that there is no valid HTTP connection, then there is no RFC connection to ADS.

-> Contact your system administrator and ask them to correct or create the RFC connection (transaction SM59).

2. 4 The system does not respond.

-> Follow the instrcutions in s 783185 and 1587941.

3. Check the user and password of ADS

Prerequisite: To perform this test, you must know the user and password for ADS. If you do not know this information, contact your system administrator and ask them to carry out the test.

Note the following: These instructions can be found in the documentation for the Adobe Configuration Guide in the chapter «Checking the User and Password».

For SAP NetWeaver 7.0, 7.01, 7.02 , proceed as follows:

1. In your Web browser, enter the following URL:

: are the name and port of the J2EE Engine on which the Adobe Document Services run.

2. The Web page of the Web service Adobe Document Services is displayed. Choose «Test».

3. Choose rpdata(test..)

4. Choose «Send». No further parameter entries are required.

5. Enter «ADSUser» for the user and enter the relevant password.

6. Choose «Submit».

As of SAP NetWeaver 7. 1 and higher, the test occurs via the Web Service Navigator, which you call with http://:/wsnavigator. Caution: You require the user and password for the WS Navigator.

In Netweaver 7.10, you filter according to the service «com.adobe/AdobeDocumentServices_com.adobe_AdobeDocumentServicesVi» and execute the operation rpData similar to as described above.

As of NetWeaver 7.11 and higher, enter «Provider System» and «Local AS Java» as the search type to search for the service interface.

Choose «AdobeDocumentServicesVi» from the list of service interfaces. Choose «Continue» — no further parameter entries are required — until the system displays the dialog box for the user and password. Then enter «ADSUser» and the relevant password.

Result of the test for user and password:

If the system displays the version number of ADS, the configuration of the user and password is correct.

-> Proceed to the next point (4).

If the system does not display a version number (the page in the Web browser does not change, and submit continues to be displayed), the configuration of ADS is incorrect.

-> Contact your system administrator and ask them to correct the configuration for the user and password.

4. Check the settings for the destination service

To use the destination service on AS Java, settings are required on AS ABAP and AS Java. Therefore, this test contains several steps.

4. 1 In your ABAP system (transaction SA38), execute the following programs in succession:

2. FP_CHECK_HTTP_DATA_TRANSFER (this program only if you bundle your forms).

a) First of all, execute the program without selecting the option «With Destination Service».

The system processes a test form in the background and displays the size of the generated PDF. It does not use the destination service in the process.

Caution: If the system issues an error message here, read 1587941.

b) Now select the option «With Destination Service» and execute the program again. The system processes the test form, using the destination service.

If the system displays the same message (file size of generated PDF) as it does in a), the configuration of the destination service is correct.
-> If you use scenarios with an interactive PDF, proceed with point 5. For print forms, proceed with point 6.

If the system issues an error message, the configuration of the destination service is incorrect.
-> If an error message is issued when you execute FP_CHECK_DESTINATION_SERVICE, execute the following tests 4.2 to 4.4.

-> If an error message is issued when you execute FP_CHECK_HTTP_DATA_TRANSFER, you require the ADS runtime information (trace files) for further troubleshooting. You can find out how to determine this runtime information under point 6. After you have made the settings, call the program again. The system saves the runtime information locally on your front-end PC.

Create a customer message under the component BC-SRV-FP, describe the problem, and attach the trace file with the runtime information to the message.

4. 2 Check whether the following ICF services are active (transaction SICF):

If this service is not active, activate it. Note: You requre the ICF service fpads as of NW7.0 Support Package Stack 12 for bundling forms in distributed systems.

4. 3 Check the settings for the ICF service «fp».

a) Enter the following URL in your Web browser:

www.sap/bc/fp/form/layout/fp_test_00.xdp

is the AS ABAP, is the HTTP port of the AS ABAP. (you can determine this information using transaction SICF).

b) In the dialog box for the user, enter ADS_AGENT and the relevant password.

If the ICF service settings are correct, the browser displays the layout information of the FP_TEST_00 form in XML format.

-> Proceed with point 4.4.

If the browser displays an error message instead of the aforementioned XML file, a configuration error occurred.

-> Check whether the user ADS_AGENT exists on the AS ABAP, and if the user has the required authorizations and roles (SAP_BC_FP_ICF or SAP_BC_FPADS_ICF).

Note the following: Make sure that the relevant traffic lights for the status of the the profile comparison are green.

4.4. Check the settings for the destination service on AS Java (J2EE Engine)

a) Call Visual Administrator and navigate to Services -> Destinations

(You can also find detailed instructions in the Adobe Document Services Configuration Guide in the chapter «Creating or Changing the Destination Service»,)

b) Extend the setting in field URLunder Connection Settings to:

http://:/sap/bc/fp/form/layout/fp_test_00.xdp

(The and that are already available refer to the AS ABAP.)

c) Choose ‘Save and Test’

d) The system calls the ABAP system that stores the form templates.

If the settings are correct, the system issues the message: «HTTP GET response code 200 Content Type/xml.»

-> If you use scenarios with an interactive PDF, proceed with point 5. For print forms, proceed with point 6.

If the system issues an error message, the configuration of the destination service is incorrect.

-> Contact your system administrator and ask them to correct the settings for the destination service.

e) Do not forget to change the URL back to http://:.

5. Check whether the credential is configured.

You must perform this step only if you use interactive scenarios. If you only use print scenarios, proceed with point 6.

Use transaction SA38 to execute the program FP_TEST_IA_01.

If the system displays the form, the ReaderRights credential is installed and configured.

-> Proceed with point 6.

If you receive an error message, for example,

ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)

-> Check whether you have installed and registered a credential. See Note 736902 and the Adobe Configuration Guide at:

SAP NetWeaver 7.0

SAP NetWeaver 7.1 and higher

www.help.sap. com/saphelp_nwpi711/helpdata/en/56/f2c94a069f44a785b85748e11f82a0/frameset.htm

6. Generated PDF with additional information

Call your form and save the generated PDF with additional information locally. You receive a PDF with attachments, which enable you to analyze the problem in detail.

Information about the PDF with additional information is available in the problem analysis guide (PAG) for SAP NetWeaver (TM) at:

http://help.sap.com/saphelp_nw70/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm ->Usage Type Application Server Java -> Problem Analysis Scenario for Adobe Document Services -> Adobe Rendering Error

The following information about the procedure when setting this function can also be found in the documentation on SAP Interactive Forms by Adobe on the Help Portal under:

You have the following options:

Setting using transaction SFP

1. Call the Form Builder (transaction SFP).

2. Choose «Utilities -> Settings».

3. In the dialog box, choose the option «Very Detailed Trace» for «Trace Level» under «Runtime Information».

4. Enter a file name under which the runtime information is to be saved locally as a trace file on your front-end PC. This file is useful for subsequent troubleshooting.

5. Set the indicator «PDF with Additional Information» and specify a file name if a PDF display or preview is not possible in your application. With this option, the generated PDF with additional information is then saved locally to your front-end PC.

Setting using user settings

You can also use the user settings to activate the function «PDF with Additional Information». Proceed as follows:

1. Call transaction SU3 (‘Maintain User Profile’) or SU01 (‘User Maintenance’).

Note that you require the relevant authorization for the user maintenance of other users.

2. Choose the tab page ‘Parameters’, and enter the required parameters and values:

FPTRACELEVEL = 04
Setting the trace to the value required for the local saving of runtime information and for the generation of the PDF that contains additional information.

File for the local saving of runtime information This specification is optional.

The system generates a PDF that contains additional information.

File for locally saving the PDF that contains additional information

Caution: Local saving is possible only for applications that have a GUI connection, and therefore, this is not supported for Web Dynpro ABAP.

3. These values then have a fixed assignment to the user.

You must reset these settings after troubleshooting is completed.

After you have made these settings, call your application for creating forms. The displayed PDF now contains the additional information that can be used for further troubleshooting. Save the displayed PDF.

Attach these files (PDF with attachment) to a message under the component BC-SRV-FP with a precise description of the problem.

If you cannot generate a PDF, save the trace files and attach them to your problem message as described above.

7. Activating ADS trace on the J2EE Engine

If you cannot determine the cause of the problem with the aforementioned steps or cannot create a PDF with additional information, we recommend that you activate the ADS trace on the J2EE Engine. Reproduce the problem. All actions relating to the Adobe Document Services are then logged on the J2EE Engine.

Create a customer message under the component BC-SRV-FP with an exact description of the problem and attach the trace files to the message.

You can find out how to activate the ADS trace in 846610.

II Web Dynpro for ABAP

To analyze problems with interactive forms, which are integrated in Web Dynpro for ABAP, you will find detailed information in 999998.

To determine whether the ADS configuration is correct, execute steps 1 to 5 that are described under I ABAP:

1. Test program FP_TEST_00
2. Test program FP_PDF_TEST_00, RFC connection to ADS
3. Test user and password
4. Test destination service (only FP_CHECK_DESTINATION_SERVICE)
5. Interactive forms: Test program FP_TEST_IA_01, credential test

6. Generated PDF with additional information

Call your form in the Web Dynpro application and save the PDF with additional information that is generated by Adobe Reader. If the toolbar does not contain the save icon, use the F8 key to display it. You receive a PDF with attachments, which enable you to analyze the problem in detail.

Setting using user settings

You can only use the user settings to activate the function «PDF with Additional Information». Proceed as follows:

1. Logon to the corresponding ABAP system.

2. Call transaction SU3 (‘Maintain User Profile’) or SU01 (‘User Maintenance’).

Note that you require the relevant authorization for the user maintenance of other users.

3. Choose the ‘Parameters’ tab page and enter the required parameter and value:

Sets the trace to the necessary value for generating the PDF with additional information.

4. The assignment of the value to the user is now fixed.

5. Exit the Web Dynpro application and logon again so that the user parameter configured previously takes affect.

Reset these values after troubleshooting is completed.

> Attach these files (PDF with attachment) to a message with the component BC-SRV-FP, including a precise description of the problem.

7. Activating ADS trace on the J2EE Engine

See descrption under I ABAP and 846610.

II Web Dynpro for Java

1. Check the user and password of ADS

The procedure is the same as in chapter I ABAP «3. Test user and password».

This information can also be found in the Adobe Document Services Configuration Guide in the Help Portal under:

http://help.sap. com/saphelp_nw70/helpdata/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm -> Adobe Document Services Configuration Guide -> Configuring the Web Service -> Securing Access to the Web Service ->Configuration Check -> Configuration Check for Interactive Forms in Web Dynpro for Java

2. Check whether the credential is configured.

Check whether you have installed and registered a credential. See Note 736902 and the Adobe Configuration Guide at:

SAP NetWeaver 7.0

SAP NetWeaver 7.1 and higher

3. Generated PDF with additional information

As of SAP NetWeaver 7. 0 Support Package 06, you can generate a PDF with attachments that enable detailed troubleshooting. The procedure depends on the Support Package level of SAP NetWeaver 7.0.

SAP NetWeaver 7. 0 Support Package 06/07/08

• Extend your application URL with the «sap-wd-adsTrace=4» addition.
  Note that there will then only be a display if the system can create a PDF. If this is not the case, follow the instructions that are contained in Notes 742674 and 846712.
  SAP NetWeaver 7. 0 Support Package 09 and higher
• Set the Trace Level for Web Dynpro to ‘ALL’. You can find detailed information about setting the Trace Level in Note 742674.
• Call your form and save the generated PDF with additional information locally. This PDF with attachments is required later for detailed error analysis. Attach these files to a message with the component BC-WD-JAV, including a precise description of the problem.
• Reset the Web Dynpro Trace level.
  SAP NetWeaver ’04
• In these versions, the system does not display any PDFs with additional information, however, the trace files contain the notes that you require regarding the cause of the problem. Set the Trace Level for Web Dynpro to ‘ALL’. You can find detailed information about setting the Trace Level in Note 742674.
• Call your form and save the trace files locally. These are required later for detailed error analysis. Attach these trace files to a message with the component BC-WD-JAV, including a precise description of the problem.
• Reset the Web Dynpro Trace level.
  Information about the PDF with additional information is available in the SAP NetWeaver Problem Analysis Guide (PAG) at:
  http://help.sap.com/saphelp_nw70/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm ->Usage Type Application Server Java -> Problem Analysis Scenario for Adobe Document Services -> Adobe Rendering Error

4. Activating ADS trace on the J2EE Engine

Источник

You’re viewing Apigee X documentation.
View
Apigee Edge documentation.

SourceMessageNotAvailable

Error Code

steps.messagevalidation.SourceMessageNotAvailable

Error response body

{
  "fault": {
    "faultstring": "source_var_name message is not
     available for[policy_name]",
    "detail": {
      "Errorcode":
       "steps.messagevalidation.SourceMessageNotAvailable"
     }
  }
}

Example Error response body

{
  "fault": {
    "faultstring": "request message is not available for MessageValidation: SOAP-Message-Validation-1",
    "detail": {
      "errorcode": "steps.messagevalidation.SourceMessageNotAvailable"
    }
  }
}

Cause

This error occurs if the message variable specified in the <Source> element of the SOAPMessageValidation policy is either:

• Out of scope (not available in the specific flow where the policy is being executed) or
• can’t be resolved (is not defined)

For example, this error occurs if the <Source> element in the SOAPMessageValidation policy is set to a variable that doesn’t exist in the flow where the policy is executed.

Diagnosis

1. Identify the SOAPMessageValidation policy name where the error occurs and the
   name of the source variable from the fault string. For example, in the following fault string, the SOAPMessageValidation policy name is SOAP-Message-Validation-1and the source variable is request:

   "faultstring": "request message is not available for MessageValidation: SOAP-Message-Validation-1"
   

2. In the failed SOAPMessageValidation policy XML, verify that the name of the variable set in the <Source> element matches the variable name identified in the fault string (Step 1 above).

   For example, the following SOAPMessageValidation policy specifies a variable named request in the <Source> element, which matches what’s in the fault string:

   <MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
       <DisplayName>SOAP Message Validation-1</DisplayName>
       <Properties/>
       <Element namespace="http://schemas.xmlsoap.org/soap/prices">GetPriceResponse</Element>
       <SOAPMessage/>
       <Source>request</Source>
       <ResourceURL>xsd://Script-1.xsd</ResourceURL>
   </MessageValidation>
   

3. Determine if the variable used in the <Source> element is defined and available in the flow in which the SOAPMessageValidation policy is being executed.

   If the variable is either:

   • out of scope (not available in the specific flow where the policy is being executed) or
   • can’t be resolved (is not defined)

   then that’s the cause of the error.

   As an example, let’s say the SOAPMessageValidation policy shown above executes in the response flow. However, the request variable used in the <Source> element example above is only available in the request flow.

   Because the request variable does not exist in the response flow, you receive the following error:

   "faultstring": "request message is not available for MessageValidation: SOAP-Message-Validation-1"
   

Resolution

Ensure that the variable set in the <Source> element of the failed SOAPMessageValidation policy is defined and exists in the flow where the policy executes.

To correct the example shown above, you could modify the <Source> element to use
the response variable, which exists in the response flow:

<MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
    <DisplayName>SOAP Message Validation-1</DisplayName>
    <Properties/>
    <Element namespace="http://schemas.xmlsoap.org/soap/prices">GetPriceResponse</Element>
    <SOAPMessage/>
    <Source>response</Source>
    <ResourceURL>xsd://Script-1.xsd</ResourceURL>
</MessageValidation>

NonMessageVariable

Error Code

steps.messagevalidation.NonMessageVariable

Error response body

{
  "fault": {
    "faultstring": "Variable var_name does not resolve to a Message"
    "detail": {
      "errorcode": "steps.messagevalidation.NonMessageVariable"
    }
  }
}

Example Error response body

{
  "fault": {
    "faultstring": "Variable message.content does not resolve to a Message",
    "detail": {
      "errorcode": "steps.messagevalidation.NonMessageVariable"
    }
  }
}

Cause

This error occurs if the <Source> element in the SOAPMessageValidation policy is set to a variable which is not of type Message.

Message type variables represent entire HTTP requests and responses. The built-in Apigee flow variables request, response, and message are of type Message. To learn more about message variables, see the Variables reference.

Diagnosis

1. Identify the name of the variable that does not resolve to a Message type from the fault string. For example, in the following fault string the name of variable is message.content:

   "faultstring": "Variable message.content does not resolve to a Message"
   

2. Examine all the SOAPMessageValidation policies in the specific API Proxy where the failure has occurred. There could be one or more SOAPMessageValidation policies. Identify the specific SOAPMessageValidation policy or policies in which the variable specified in the <Source> element matches the variable name identified in the fault string (Step 1 above).

   For example, the following policy sets the <Source> element to a variable named message.content, which matches what’s in the fault string:

   <MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
       <DisplayName>SOAP Message Validation-1</DisplayName>
       <Properties/>
       <Element namespace="http://schemas.xmlsoap.org/soap/prices">GetPriceResponse</Element>
       <SOAPMessage/>
       <Source>message.content</Source>
       <ResourceURL>xsd://Script-1.xsd</ResourceURL>
   </MessageValidation>
   

   Because the variable message.content is not of type Message, you get the error:

   "faultstring": "Variable message.content does not resolve to a Message"
   

Resolution

Ensure that the <Source> element in the failed SOAPMessageValidation policy is set to a Message type variable that exists in the flow where the policy executes.

To correct the policy, you can modify the <Source> element to specify a variable that is of type Message. For example, in the failed SOAPMessageValidation policy,
you could specify the <Source> element as request:

<MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
    <DisplayName>SOAP Message Validation-1</DisplayName>
    <Properties/>
    <Element namespace="http://sample.com"> sampleObject</Element>
    <SOAPMessage/>
    <Source>request</Source>
    <ResourceURL>xsd://Script-1.xsd</ResourceURL>
</MessageValidation>

Failed

Error Code

steps.messagevalidation.Failed

Error response body

{
  "fault": {
    "faultstring": "Variable var_name failed with reason: "reason [Line varline_num
    "detail": {
      "errorcode": "steps.messagevalidation.Failed"
    }
  }
}

Example Error response body

{
  "fault": {
    "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expecting a child element but found none [Line 9]"",
    "detail": {
      "errorcode": "steps.messagevalidation.Failed"
    }
  }
}

Cause

This error occurs if the SOAPMessageValidation policy fails to validate the input message payload against the XSD schema or WSDL definition. It will also occur if there is malformed JSON or XML in the payload message.

Here are some of the possible causes that can lead to this error:

Cause: Mismatching XML payload

This error occurs if the input XML payload does not adhere to the XSD schema
specified in the <ResourceURL> element of the SoapMessageValidation policy.

Example Error Message

{
  "fault": {
    "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expecting a child element but found none [Line 9]"",
    "detail": {
      "errorcode": "steps.messagevalidation.Failed"
    }
  }
}

Diagnosis

1. Identify the SOAPMessageValidation policy name, the reason for the failure and the line number at which the XML payload does not match the XSD schema. All of this information is in the fault string. For example, in the following fault string, the SOAPMessageValidation policy name is SOAP-Message-Validation-1,the reason for the failure is Expecting a child element but found none [Line 9]: and the line number is 9.

   "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expecting a child element but found none [Line 9]""
   

2. Examine the SOAPMessageValidation policy and confirm that it uses an XSD schema definition file to validate messages. For example, the following SOAPMessageValidation policy has an XSD resource file in the<ResourceURL> element:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
       <DisplayName>SOAP Message Validation-1</DisplayName>
       <Properties/>
       <SOAPMessage/>
       <Source>request</Source>
       <ResourceURL>xsd://Script-1.xsd</ResourceURL>
   </MessageValidation>
   

3. Examine the input payload on the line number identified in Step 1 above to understand what caused the failure.

   Sample Input XML payload

   <?xml version="1.0"?>
   <soap:Envelope
   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding">
   <soap:Body>
       <shipOrder
       xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
       <shipTo>
           <name>Karl Kalckstein</name>
       </shipTo>
       <items>
           <item>
               <title>I love APIs</title>
               <quantity>1</quantity>
               <price>2.90</price>
           </item>
       </items>
   </shipOrder>
   </soap:Body>
   </soap:Envelope>
   

   In the example shown above, line 9 has the </shipTo> end tag.

4. Examine the XML schema definition file, Script-1.xsd, used in the SOAPMessageValidation policy to see how the <shipTo> element should look:

   ...
   <xsd:element name="shipTo" type="shipAddress"/>
   ...
   <xsd:complexType name="shipAddress">
   <xsd:sequence>
   <xsd:element name="name" type="xsd:string"/>
   <xsd:element name="street" type="xsd:string"/>
   <xsd:element name="address" type="xsd:string"/>
   <xsd:element name="country" type="xsd:string"/>
   </xsd:sequence>
   </xsd:complexType>
   ...
   

   According to the sample XSD used for validation, the <shipTo> element must
   have the child elements <name>, <street>, <address> and <country>. However, the input XML payload has only one child element, <name>. As a result, you get the error:

   "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expecting a child element but found none [Line 9]""
   

Resolution

There are two ways to resolve this validation error:

Solution #1

If you determine that the XSD schema definition imposes unnecessary limitations and only the <name> child element is required under the <shipTo> element, you can modify the Script-1.xsd used in SOAPMessageValidation policy. To validate the payload example above, you can modify the XSD file as follows:

...
<xsd:element name="shipTo" type="shipAddress"/>
...
<xsd:complexType name="shipAddress">
<xsd:sequence>
<xsd:element name="name" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>

Solution #2

If the XSD definition file is correct, then the input XML payload can be changed to match the xsd. For example, you could modify the payload to comply with the xsd as follows:

<?xml version="1.0">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding">
<soap:Body>
    <shipOrder xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
    <shipTo>
        <name>Karl Kalckstein</name>
        <street>1020 Parkway</street>
        <address>Mountain View, CA 94043</address>
        <country>USA</country>
    </shipTo>
    <items>
        <item>
            <title>I love APIs</title>
            <quantity>1</quantity>
            <price>2.90</price>
        </item>
    </items>
</shipOrder>
</soap:Body>
</soap:Envelope>

Cause: Mismatching SOAP payload

This error occurs if the input SOAP payload does not adhere to the WSDL definition specified in the <ResourceURL> element of the SoapMessageValidation policy.

Example Error Message

{
  "fault": {
    "faultstring": "SOAP-Message-Validation-1 failed with reason: "Element name mismatch. Wildcard? [Line 11]"",
    "detail": {
      "errorcode": "steps.messagevalidation.Failed"
    }
  }
}

Diagnosis

1. Identify the SOAPMessageValidation policy name, the reason for the failure and the line number at which the SOAP payload does not match the WSDL definition. You can find all this information from the fault string. For example, in the following fault string, the SOAPMessageValidation policy name is SOAP-Message-Validation-1, the reason for the failure is "Element name mismatch. Wildcard? [Line 11]"" and the line number is 11:

   "faultstring": "SOAP-Message-Validation-1 failed with reason: "Element name mismatch. Wildcard? [Line 11]""
   

2. Examine the SOAPMessageValidation policy and confirm that it uses a wsdl schema to validate messages. For example, the following SOAPMessageValidation policy has an wsdl resource file in the<ResourceURL> element:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <MessageValidation async="false" continueOnError="false" enabled="true" name="SOAP-Message-Validation-1">
       <DisplayName>SOAP Message Validation-1</DisplayName>
       <Properties/>
       <SOAPMessage/>
       <Source>request</Source>
    <ResourceURL>wsdl://SOAP-Message-Validation-1.wsdl</ResourceURL>
   </MessageValidation>
   

3. Examine the input payload on the line number identified in Step 1 to understand what caused the failure.

   Sample Input SOAP Payload

   <?xml version="1.0"?>
   <soap:Envelope
   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
   soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding">
   <soap:Body>
   <shipOrder
   xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
     <shipTo>
       <name>Karl Kalckstein</name>
       <street>1020 Parkway</street>
       <address>Mountain View, CA 94043</address>
       <country>USA</country>
     </shipTo>
     <items>
       <item>
         <title>I love APIs</title>
         <quantity>1</quantity>
         <price>2.90</price>
       </item>
     </items>
   

   In the example shown above, line 11 has the child element <country> under the <shipTo> element.

4. Examine the WSDL Definition file, SOAP-Message-Validation-1.wsdl, used in the SOAPMessageValidation policy to see what could be wrong with the child element <country> under the <shipTo> element:

   <?xml version="1.0" encoding="ISO-8859-1"?>
   <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
       <wsdl:types>
         <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <xsd:element name="shipOrder" type="order"/>
   <xsd:complexType name="order">
   <xsd:sequence>
   <xsd:element name="shipTo" type="shipAddress"/>
   <xsd:element name="items" type="cdItems"/>
   </xsd:sequence>
   </xsd:complexType>
   <xsd:complexType name="shipAddress">
   <xsd:sequence>
   <xsd:element name="name" type="xsd:string"/>
   <xsd:element name="street" type="xsd:string"/>
   <xsd:element name="address" type="xsd:string"/>
   </xsd:sequence>
   ...
   

   According to the WSDL definition used for validation, the <shipTo>element does not have a <country> child element. As a result, you get the error:

   "faultstring": "SOAP-Message-Validation-1 failed with reason: "Element name mismatch. Wildcard? [Line 11]""
   

Resolution

There are two ways to resolve this validation error:

Solution #1

If you determine that the WSDL definition used is incorrect, you can change the SOAP-Message-Validation-1.wsdl used in SOAPMessageValidation policy. To validate the payload example above, you can modify the file as follows:

...
<xsd:complexType name="shipAddress">`
...
<sequence>
    <element name="name" type="xsd:string"/>
    <element name="street" type="xsd:string"/>
    <element name="address" type="xsd:string"/>
    <element name="country" type="xsd:string"/>
</sequence>

Solution #2

If the WSDL definition is correct, then the input SOAP payload can be changed to match the WSDL definition.

For example, you can modify the input SOAP payload as follows:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding">
<soap:Body>
<shipOrder xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
    <shipTo>
        <name>Karl Kalckstein</name>
        <street>1020 Parkway</street>
        <address>Mountain View, CA 94043</address>
    </shipTo>
    <items>
        <item>
            <title>I love APIs</title>
            <quantity>1</quantity>
            <price>2.90</price>
        </item>
    </items>

Cause: Malformed JSON or XML

This error occurs if the input SOAP payload does not adhere to the WSDL definition specified in the <ResourceURL> element of the SoapMessageValidation policy.

Example Error Message

{
  "fault": {
    "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expected </title> at line 15(possibly  around char 420)"",
    "detail": {
      "errorcode": "steps.messagevalidation.Failed"
    }
  }
}

Diagnosis

1. Identify the SOAPMessageValidation policy name, the reason for the failure and the line number of the XML payload that does not match the WSDL definition. You can find all this information in the fault string. For example, in the following fault string, the SOAPMessageValidation policy name is SOAP-Message-Validation-1, the reason for the failure is Expected </title> at line 15(possibly around char 420): and the line number is15.

   "faultstring": "SOAP-Message-Validation-1 failed with reason: "Expected </title> at line 15(possibly  around char 420)""
   

2. Examine the input payload on the line number identified in Step 1 above to understand what caused the failure.

   Sample Input SOAP Payload

   <?xml version="1.0"?>
   <soap:Envelope
   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
   soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding">
   <soap:Body>
   <shipOrder xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance">
     <shipTo>
       <name>Karl Kalckstein</name>
       <street>1020 Parkway</street>
       <address>Mountain View, CA 94043</address>
       <country>USA</country>
     </shipTo>
     <items>
       <item>
         <title>I love APIs</titles>
         <quantity>1</quantity>
         <price>2.90</price>
       </item>
     </items>
   </shipOrder>
   </soap:Body>
   </soap:Envelope>
   

   In the example shown above, line 15 of the input XML has the element <title> but is not closed with a </title> end tag.

Resolution

To resolve the error, ensure that the input payload is valid and formed correctly.

For example, you could modify the input XML payload as follows:

...
</shipTo>
<items>
  <item>
    <title>I love APIs</title>
    <quantity>1</quantity>
    <price>2.90</price>
  </item>
</items>
...