Skip to main content
norm1973
New Participant
November 20, 2018
Question

RaiseError or unhandled exception after a SOAP call

  • November 20, 2018
  • 1 reply
  • 1396 views

Hello everyone. I have experienced the following situation.

I have an interactive form designed with Adobe LiveCycle Designer ES4 which is then executed with Adobe Acrobat Standard DC (Version: 2015.006.30457). The form is utilizing the functionality of the Net.SOAP object for obtaining some data.

When the content-type of the response was "text/xml" or "application/json", for example when requesting SharePoint data, all worked as expected for both synchronous and asynchronous calls.

However, for the response below when the call was made synchronously Adobe Standard generated RaiseError pointing to the Net.SOAP.request() method. If, alternatively, the call was made asynchronously the callback function was not invoked and the rest of the code continued executing as if nothing had happened. In the latter case though upon exiting Adobe Acrobat, "Adobe Acrobat DC has stopped working" and “An unhandled exception occurred in Acrobat.exe [ some number ]” messages were generated.

Response raw data from the server:

HTTP/1.1 200 OK

Server: Apache-Coyote/1.1

Content-Type: multipart/related; boundary="MIMEBoundary_67f476708814c228e21476171933b4c45e524344efdc9e24"; type="application/xop+xml"; start="<0.77f476708814c228e21476171933b4c45e524344efdc9e24@apache.org>"; start-info="text/xml"

Date: Tue, 20 Nov 2018 06:33:57 GMT

Content-Length: 1781

--MIMEBoundary_67f476708814c228e21476171933b4c45e524344efdc9e24

Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"

Content-Transfer-Encoding: binary

Content-ID: <0.77f476708814c228e21476171933b4c45e524344efdc9e24@apache.org>

<?xml version='1.0' encoding='UTF-8'?>?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
< ...
some valid XML content ... ></soapenv:Envelope>

--MIMEBoundary_67f476708814c228e21476171933b4c45e524344efdc9e24--

I have searched on the Internet for any clues but failed to find anything related.

Has anyone experienced an issue like that? I'll much appreciate any suggestion how to resolve it.

Thank you!

This topic has been closed for replies.

1 reply

Thom Parker
Inspiring
November 27, 2018

Does this exact same SOAP call work from another source, such as a web page or server script?

Thom Parker - Software Developer at PDFScriptingUse the Acrobat JavaScript Reference early and often
norm1973
norm1973Author
New Participant
November 28, 2018

Hello Thom, thank you for your question.

​Actually I have created a SOAP project in SOAPUI by importing the relevant WSDL file. I then created two alternative Net.SOAP calls using the "connect" and "response" methods, and one more using the Net.HTTP "request" method. I monitored the calls with Fiddler Web Debugger. For each of the three calls the server responded exactly as it did to the SOAPUI call, and the data returned were identical. I executed the call within a try/catch statement and the thrown Error object parameters are as follows (the values of "lineNumber" and "columnNumber" may vary depending on the call method that was used). 

name : RaiseError

message :

extMessage : RaiseError:

Net.SOAP.request:319:XFA:ProductDocuments[0]:AsyncStore[0]:change

===>

fileName : XFA:ProductDocuments[0]:AsyncStore[0]:change

lineNumber : 319

number : 12

raiseSystem : 255

raiseCode : 65535

columnNumber : 0

Thom Parker
Inspiring
November 28, 2018

Well then, sounds like a problem with Acrobat, either a bug, or possibly an incompatibility with some detail of the transaction. Have you tried this from a regular PDF?  There may be something about the LC JS engine that's an issue.

Thom Parker - Software Developer at PDFScriptingUse the Acrobat JavaScript Reference early and often