Skip to main content
Known Participant
November 25, 2009
Question

AccessViolationException fatal error, Acrobat 9, AxAcroPDFLib, .NET, Win7

  • November 25, 2009
  • 12 replies
  • 42899 views

How do I work around the following fatal error:  AccessViolationException

Steps to reproduce the error:

1.  In MS VisualStudio 2008, Create a Windows Form Application, add a Panel and a Button components to the form.

2.  Add a Reference to the Acrobat COM component for AxAcroPDFLib

3.  Add the following code to the main form:

    private AxAcroPDFLib.AxAcroPDF ax = new AxAcroPDFLib.AxAcroPDF();

    private void button1_Click(object sender, EventArgs e)
    {
      panel1.Controls.Add(ax);

      ax.LoadFile(@"c:\temp\myfile.pdf");
      ax.setView("Fit");     
    }

4.  Run the application

5.  Click the Button

6.  Press the TAB key on the keyboard.

Result:  The application crashes with an AccessViolationException:  Memory Corrupted error.

Note:  I had been working on an application for about a month now, but had Never pressed the Tab key while the application was running until today!!

Although I did not yet test EVERY key, all other keys and activities inside and outside of the Acrobat component, application, and OS seem to work ok.  I can't deploy an application to production if it will crash on Tab keypress.

Platform:

Windows 7, 32bit, all current updates

Acrobat 9 Standard, all current updates

Microsoft Visual Studio 2008 Professional, all current updates

I'm not an Acrobat SDK developer expert, so this may be some simple configuration setting.

Any assistance is greatly appreciated.

Arnold

This topic has been closed for replies.

12 replies

Known Participant
November 30, 2009

Looks like Acrobat will be dead for us in Windows 7 until this problem is fixed.  I cannot get Acrobat 8 Reader to install in Windows 7, so until Acrobat 9.2.0 is fixed in Windows 7, we have to use a third party PDF viewer.

This was really unexpected!

Attention ADOBE:  Please fix the <TAB> key problem in Acrobat 9.2.0 in Windows 7 and notify me ASAP as soon as the fix is ready.

lrosenth
Adobe Employee
Adobe Employee
November 30, 2009

As I already said, we are aware of the problem and will release a fix as soon as possible in our current update schedule.

New Participant
April 9, 2010

I just tested this with Acrobat 9.3.1 on Windows XP and Windows Vista.  This issue still exists, and has existed since Acrobat 9.0.  There is an untrappable exception thrown when the user attempts to tab out of the AcroPDF control.  Additionally, once a document is opened in the AcroPDF control, all keyboard keystrokes apply to the AcroPDF control, not the main application form.  As a result, users with accessibility requirements cannot tab back to the application main menu or toolbar to continue operating the application once a document is opened.

I am using the AcroPDF control in a Windows executable application written in Visual Basic .NET 2008.  Purchase of Acrobat Standard or better by the client for each PC that will have my application installed is a prerequisite for purchase.

My product cannot pass US Federal Government Rehabilitation Act Section 508 Requirements until this issue is resolved- effectively locking me out of the Federal Government market.

Does Adobe recommend another PDF viewer that developers should use that will allow Accessibility in their applications?

lrosenth
Adobe Employee
Adobe Employee
November 25, 2009

We are aware of the tab issue but I am pretty sure that it was fixed in 9.2 (the current update). Can you verify that you are on 9.2? Also, are you in Acrobat or Reader?

Known Participant
November 25, 2009

I verified Acrobat's Help/About:  Version 9.2.0 Standard

Windows 7 Enterprise (32 bit).

I tried .NET Frameworks 2.0 and 3.5.

I didn't try Acrobat Reader.  Will the Reader behave differently?  The final application is for Viewing/Read Only, so I won't need the features of the Standard edition beyond what the Reader comes with.  My impression was that I needed the Standard or Pro version license to embed the viewer into a workstation application.

Arnold

lrosenth
Adobe Employee
Adobe Employee
November 26, 2009

You don't need Standard or Pro - whatever the user has on their computer is what will be used. No "licensing" involved since you aren't distributing any Adobe parts.