Hang, crash, or GPF in ADOBE Accessibility, Adobe Reader, or ADOBE Flash
User is prompted to install / setup ADOBE Acrobat accessibility controls when opening PDF document
Test to see whether the problem is specifically related to SecureLogin, or if there is an issue between the application and the Microsoft .net accessibility framework. UI Spy can be used for this test, as described below under âadditional information.â
1. If SecureLogin is not used to single sign on for flash or .Net applications, disable dotnetsso or flashsso as discussed in TID 7008895
4. Delete or rename the Adobe Reader Accessibility plugin:
C:\Program Files (x86)\Adobe\Reader 9.0\Reader\plug_ins\Accessibility.api
Note that this file will be reinstalled every time AdobeReader is updated, so you will need to keep deleting the accessibility plugin after each Adobe update.
5. Open a support call with other application vendor.
Instructions on testing with UISpy:
1. Download UISpy from any of several download sites. It is a free download and can easily located by searching on âUISpy download.â
2. Launch UISpy and open the events, Configure menu. Configure as detailed in steps 3-5 below, using the following graphic as a guide:
3. In the âScope Flagsâ section, select the options for âdescendantsâ
4. In the âSelect Eventsâ section chose âAll Events,â âEvents on 'pane,'â and âStructure Changed.â Click OK.
5. Click on Events, Start.
You will see in the Output window that UISpy is active. The events and associated information will be listed in the "output" window when you move to any other window and perform an operation such as clicking a button or opening a menu items. Configured in this manner UISPy is is similar to sldotnetsso listening mode.
6. Close SecureLogin if it is running so that results are not confused.
7. Perform the operation that caused the problem when SecureLogin was running. If the problem occurs with UISpy you will know that the problem is are not caused by SecureLogin.