Comments on: Careful with Form Compatibility Settings http://forms.stefcameron.com/2009/02/11/careful-with-form-compatibility-settings/ Building intelligent forms using Adobe LiveCycle Designer Fri, 10 Sep 2010 11:50:02 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Justin http://forms.stefcameron.com/2009/02/11/careful-with-form-compatibility-settings/comment-page-1/#comment-70348 Justin Thu, 06 May 2010 05:48:26 +0000 http://forms.stefcameron.com/2009/02/11/careful-with-form-compatibility-settings/#comment-70348 Hi Stefan, Since the inception of a livecycle form into production, I’ve continually had an issue with the interaction of the livecycle form with our web service. The web service call appears to be working properly around 75-80% of the time but randomly fails to be executed. I have stress tested the web service and have not been able to replicate the error we’re experiencing in production. Recently we’ve put some low level debugging on the form to try and determine exactly what could be causing this issue however we don’t seem to be having a lot of luck. The error that occurs is very generic. The code that calls the web service is as follows try{ xfa.data.Submission.Common.SignaturesRequired.value ="true"; debug.traceLog("DivisionalOffice.DetermineDivisionalOfficeWSAddress - About to call AECDivisionalOfficeWSProd service."); xfa.connectionSet.AECDivisionalOfficeWSProd.execute(false); debug.traceLog("DivisionalOffice.DetermineDivisionalOfficeWSAddress - Returned from call AECDivisionalOfficeWSProd service without exception."); } catch(err){ debug.errorLog("DivisionalOffice.DetermineDivisionalOfficeWSAddress - Exception thrown during call to AECDivisionalOfficeWSProd: " +err); webservicecalled ="false"; xfa.data.Submission.Common.SignaturesRequired.value ="true"; Submission.FlowedPage.Checklist1.returnDivisionalAddress.rawValue =DefaultStateAddress.value; Submission.FlowedPage.PrintSubform.Subform21.DivisionalAddress.rawValue =postSubmissionMessage +DefaultStateAddress.value; } The resulting trace shows the following; [trace] DivisionalOffice.DetermineDivisionalOfficeWSAddress - About to call AECDivisionalOfficeWSProd service. 2010:04:04, 13:05:55:051[error] DivisionalOffice.DetermineDivisionalOfficeWSAddress - Exception thrown during call to AECDivisionalOfficeWSProd: GeneralError: Operation failed. ||2010:04:04, 13:05:55:051[trace] StructuredPostCode.exit - Returned from call to DivisionalOffice.DetermineDivisionalOfficeWSAddress It looks to me as though the actual execute command is failing immediately. Do you know why this could be happening? It's something we've been looking into for a couple of months but it is impossible to reproduce I'm wondering, coult it be a platform/reader version issue? I have a check to ensure the reader version is at least 8.2. Regards Justin Hi Stefan,
Since the inception of a livecycle form into production, I’ve continually had an issue with the interaction of the livecycle form with our web service. The web service call appears to be working properly around 75-80% of the time but randomly fails to be executed. I have stress tested the web service and have not been able to replicate the error we’re experiencing in production. Recently we’ve put some low level debugging on the form to try and determine exactly what could be causing this issue however we don’t seem to be having a lot of luck.

The error that occurs is very generic. The code that calls the web service is as follows

try{
xfa.data.Submission.Common.SignaturesRequired.value =”true”;
debug.traceLog(“DivisionalOffice.DetermineDivisionalOfficeWSAddress – About to call AECDivisionalOfficeWSProd service.”);
xfa.connectionSet.AECDivisionalOfficeWSProd.execute(false);
debug.traceLog(“DivisionalOffice.DetermineDivisionalOfficeWSAddress – Returned from call AECDivisionalOfficeWSProd service without exception.”);
}
catch(err){
debug.errorLog(“DivisionalOffice.DetermineDivisionalOfficeWSAddress – Exception thrown during call to AECDivisionalOfficeWSProd: ” +err);
webservicecalled =”false”;
xfa.data.Submission.Common.SignaturesRequired.value =”true”;
Submission.FlowedPage.Checklist1.returnDivisionalAddress.rawValue =DefaultStateAddress.value;
Submission.FlowedPage.PrintSubform.Subform21.DivisionalAddress.rawValue =postSubmissionMessage +DefaultStateAddress.value;
}

The resulting trace shows the following;
[trace] DivisionalOffice.DetermineDivisionalOfficeWSAddress – About to call AECDivisionalOfficeWSProd service.
2010:04:04, 13:05:55:051[error] DivisionalOffice.DetermineDivisionalOfficeWSAddress – Exception thrown during call to AECDivisionalOfficeWSProd: GeneralError: Operation failed.
||2010:04:04, 13:05:55:051[trace] StructuredPostCode.exit – Returned from call to DivisionalOffice.DetermineDivisionalOfficeWSAddress

It looks to me as though the actual execute command is failing immediately. Do you know why this could be happening? It’s something we’ve been looking into for a couple of months but it is impossible to reproduce I’m wondering, coult it be a platform/reader version issue? I have a check to ensure the reader version is at least 8.2.

Regards

Justin

]]>