Issue
A runtime error occurs when you launch any Acrobat 9.x application:
"Microsoft Visual C++ Debug Library Runtime Error! Program: C:\Program Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe The application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. "
Solutions
Important: These workarounds have the potential to negatively impact other software and existing workflows. Therefore, Adobe recommends that only system administrators perform these steps.
Solution 1
Make sure that all parent folders for Application Data permit read access for the requisite users. Verify that each user has read permissions for each directory in the path and that your GPO policy isn't overriding these permissions. Adobe recognizes that this workaround isn't optimal in some enterprise settings.
Alternative user-provided solutions
Adobe customers provided the following suggestions, and Adobe has not been tested them.
- On Windows 2008 Terminal Server, find AcroRd32.exe, open Properties, and select "Run this program in compatibility mode for: Windows XP (Service Pack 2).
- On Vista, change the HKCU/Software/Microsoft/Windows/CurrentVersion/Explorer/UserShellFolders AppData key value from %USERPROFILE%\Application Data to %USERPROFILE%\AppData.
- On Windows 7, the Application Data folder's "Everyone" account has a special permission of "Deny". Remove the checkmark for Deny.
- Map UNC paths such as \\server\profile\%USERNAME% to a drive letter such as U:\profile\%USERNAME%.
- On Windows 7 and Vista platforms, verify the LocalLow directory exists at C:\Users\<user>\AppData with Read and Write permissions.
Additional information
The Acrobat family of products doesn't support Roaming Profiles. However, certain workflows and configurations can work by default or by using one fo the workarounds above.
This error occurs when the application checks for read permissions for each directory in the path to Application Data. The application is supposed to instead only inspect for permission in the Application Data directory and below. If the requisite permissions are not found, a runtime error occurs.
The 9.4 cumulative update changes this behavior so that the application does not check for permissions on parent folders.