EScript.api is crashing on i9 form

[rmiltenb]

Hello.  The latest version of Acrobat DC Pro (17.012.20093) is crashing while opening the i9 form.  Per the event the log, it's crashing on EScript.api.  When JavaScript is disabled in DC, the form does open however there's a warning at the top stating that JavaScript is required for the form.  DC crashes if the form is open from the browser or saved and then open from the desktop.  Is anyone else having the same issue with other fillable forms?

Form: http://www.uscis.gov/sites/default/files/files/form/i-9.pdf

Event log:

Faulting application name: Acrobat.exe, version: 17.12.20093.41392, time stamp: 0x597fa4bb

Faulting module name: EScript.api, version: 17.12.20093.41392, time stamp: 0x597fa25e

Exception code: 0xc0000005

Fault offset: 0x00067806

Faulting process id: 0x824

Faulting application start time: 0x01d3105252f8c2c7

Faulting application path: C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\Acrobat.exe

Faulting module path: C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\plug_ins\EScript.api

Report Id: 7b8fd414-bcc1-4729-ad79-e54153691b9a

Faulting package full name:

Faulting package-relative application ID:

[Bilal Ansari]

Hi rmiltenb,

Thanks for reporting the issue. We are looking into it. Will keep you posted.

--

Regards,

Acrobat team.

[Mr__Polar_Bear]

I can also confirm that all of our forms designed under Adobe LiveCycle Designer 11.0 suffers the same problem.  We have so far determined that the EScript.api problem

• affects Adobe Acrobat/Reader DC 17.12.20093 on both Windows and Mac platform.
• affects Adobe Acrobat 2015 15.006.30352.
• does not affect Acrobat/Reader DC 17.009.20058 on both Windows and Mac platform.
• does not affect Adobe Acrobat 2015 15.006.30306.
• does not affect Adobe Reader XI 10.0.21 on both Windows and Mac platform.
• goes away by simply replacing that file in under ..\plug-ins with one from a prior version.

With the continuous track update mechanism, we will be looking at all of our users on the DC platform being locked out of using our forms, which is a serious issue.

[rmiltenb]

I copied over the older version of the API and it still crashed on me while opening the i9 form.  Do you have JavaScript turned off in Acrobat DC for Windows?

[Mr__Polar_Bear]

We did that to test one of our many forms and therefore it is probably not an exhaustive test, perhaps EScript.api is not only problem at play here. 

The only viable option is to downgrade to an earlier version of DC and disable the AdobeARMservice update agent, or downgrade completely to XI and be done with DC. 

The quality of the DC platform is extremely poor, the barcode support on Mac DC has not been working for two years now.

[BluegrassCat]

We are also having this issue.

Can you provide a download link for Adobe Reader DC 17.009.20058?

We need to revert until this issue is resolved.  We have ~ 60 impacted systems right now.

BC

[Mr__Polar_Bear]

What we did was completely uninstall DC 17.012.20093 and download and install the base release package 15.007.20033 and subsequent 17.009.20058 msp package from http://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotes/index.html#​.  Immediately after that stop and disable the AdobeARMservice to prevent the update from happening.  Another option would be to completely downgrade to Adobe XI.

[AshuMittal]

Hi all,

We have identified the issue, and are actively working on a fix. Will confirm as soon as available.

Thanks,

-ashu

[Mr__Polar_Bear]

The six million dollars question is do we have an ETA and would you publish the root cause of the problem for us to assess potential impact on our forms, and whether there is a need to regression test the forms?

[AshuMittal]

Hi @Mr. Polar Bear

I should have an ETA for you by tomorrow.

Thanks,

-ashu

[Bilal Ansari]

Hi Mr. Polar Bear, BluegrassCat​, rmiltenb,

We have a fix ready at our end. In order to ensure that your issue is resolved, could you send us some more files so that we can validate the fix before releasing it?

[Mr__Polar_Bear]

Link to our forms that were affected by the bug sent via PM.  Thanks!

[rmiltenb]

I haven't heard of any internal forms having any issues.  The big one is the i9 which is required this time of year for many higher education places.

[rjjoshi]

Hi rmiltenb​

The PDF shared is password protected for opening in Adobe LiveCycle Designer . Can you please share the same so as to enable us to evaluate the scripts in it and identify the root cause of the issue.

[rmiltenb]

Hello rjjoshi​

You will have to contact the Department of Homeland Security to obtain the unprotected version of the form.  I work at an university that many departments use the document for students.  Is there any local logs that you need?

[SQNAdministrator]

@Adobe - what's the ETA for the fix?

[AshuMittal]

Hi SQNAdministrator​

We are in the process of certifying the fix and official patch should be available in next week or so (tentatively). I will confirm once I have a firm date.

Thanks,

-ashu

[wrooot]

We are affected also and waiting for an ETA.

[chriss51154714]

We are also affected (thousands of users). At least downgrading and turning off auto-updates should be simpler. We can't tell our users to go hack the registry.

[AshuMittal · Accepted solution]

Hi all,

Adobe Acrobat and Reader official update containing the fix for this issue is now available. This update will be automatically pushed to all existing installations of Acrobat and Reader. If you want, you may also manually trigger the update by opening the application and going to Help > Check for Updates.

More information about this release is here: https://helpx.adobe.com/acrobat/release-note/acrobat-dc-august-11-2017.html

Please try it out and let us know your feedback.

Thanks!

-ashu

[wrooot]

2017.012.20095 indeed fixed the issue for us. Thanks.

[rmiltenb]

Verified that the i9 forms is opening without any issues now.

[chandley92648]

Issue still exists with Acrobat XI Pro 11.0.21.

[Guest]

I got the same error on Acrobat XI pro 11.0.21.

It worked with 11.0.19.

Would you please let us know the ETA for this fix?

Thanks

[AdobeGeek47]

Well now we just updated to 11.0.21 and have the error of can't open the I9.

I guess there is still no fix or ETA...