Hi, I got the exact same error messsage as described in this thread:
http://forums.adobe.com/message/3136286#3136286
I tried all the suggestions in the thread, but nothing worked.
My process is like this:
At the process initiator step, it uses form "A" (and Webservices calls work perfectly there),
the initiator fills up form "A", "Complete"s it,
and it goes to the next person, where it uses form "B",
and Webservices calls fail to work from the form "B".
However, when I replace form "A" with form "B",
that is, use form "B" at the initiator step,
the Webservices calls on form "B" work just fine.
Any idea why this happened?
thanks.
Then I am at a loss to explain it .....
Is the web service a LiveCycle service? If so can you create an LCA file and email it to me so I can see what is happening? Send it to LiveCycle8@gmail.com and include a description of the issue in you r email please.
Paul
Hey guys
Anybody found a solution for this problem?
I'm facing the exact same thing.
Form is ReaderExtended, and when I use it in Workspave I get the error: "Error attempting to read from file".
When I save the form to my PC and try it with Reader X, it does nothing. Just like when there would be no Reader Extension on the form.
Running LC Service Pack Version: 9.0.0.1.20100511.1.236952
Regards
I found a solution to this. The 'DataDescription' elements in the data XML are the cause of the problem. Apparently Acrobat/Reader is not able to handle the elements from form 'A' when loading that data into form 'B'.
My solution was to modify my process to:
1.) Create an xml variable (call it 'xmlData')
2.) Create an XDP "wrapper" by setting the value of xmlData in a 'Set Value' operation. Since my top-level form element is called 'TopLevelFormElement', my "wrapper" (the value for 'xmlData') was:
deserialize('<xdp:xdp xmlns:xdp="http://ns.adobe.com/xdp/" xmlns:dd="http://ns.adobe.com/data-description/"
xmlns:impl="http://adobe.com/idp/services" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xfa="http://www.xfa.org/schema/xfa-data/1.0/">
<xfa:datasets>
<xfa:data>
<TopLevelFormElement>
</TopLevelFormElement>
</xfa:data>
</xfa:datasets>
</xdp:xdp>')
3.) Copy the form data from the original (call it 'originalXmlData') to 'xmlData' by setting this mapping in a 'Set Value' operation:
//process_data/xmlData//TopLevelFormElement = /process_data/originalXmlData//TopLevelFormElement
4.) At this point, you have a set of data (xmlData) that contains all of your form data but is free of the 'DataDescription' elements that cause problems. Pass 'xmlData' into form 'B'.
5.) Data should be processed as expected in form 'B', and web service calls should be operational.
North America
Europe, Middle East and Africa
Asia Pacific