I installed Acrobat 9 Pro on one of our systems. The system got a runtime error every time Adobe Acrobat started citing "C:\Program Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe This application has requested the Runtime to terminate it in an unusal way. Please contact the application's support team for more information."
Initially, I thought it was an issue with that system. So, I installed Acrobat Standard on two other systems. Both units get the same error.
Of the 3 units 2 are identical IBM workstations with some different software installed. 1 is an HP system. The OS is a fairly clean Windows XP SP2 otherwise very stable installation.
I searched Adobe forums and here but haven't come across much version 9 questions/comments.
Initially, I was going to fully uninstall Acrobat and try the installation again. However, now that 2 other systems are getting the same error, I feel it would be a waste of time.
Any ideas on what to look for to resolve this issue?
Previous version was the latest v8 which 9 uninstalled.
Thanks in advance!
EDIT: I did come across this for version 8 and tried the same fix with 9, but to no effect:
C++ Runtime error after launching Acrobat or Adobe Reader 8 on Windows
When you launch Adobe Acrobat 8 Standard, Professional, or Adobe Reader 8 on Windows, an error occurs:
Program: C:\Program Files\Adobe\Acrobat 8.0\Acrobat\Acrobat.exe
This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information.
Disable the Updater.api plug-in.
Navigate to where Acrobat or Adobe Reader is installed, usually
C:\Program Files\Adobe\Acrobat 8.0\Acrobat\plug_ins
or C:\Program Files\Adobe\Reader 8.0\Reader\plug_ins
Rename the Updater.api plug-in to Updater.api.old
Relaunch Acrobat or Reader.
Since posting the original message I have tried completely uninstalling Adobe 8. Then I installed just the Acrobat 9 Reader.
I got the same runtime error with the reader executable.
I tried disabling NAV Corporate services and the results are the same.
I have installed Acrobat 9 Pro using a different user account. It made no difference.
Open to any ideas. I have a post on experts-exchange as well.
The runtime error- is it a general conflict between the adobe executable and *some* piece of software on our systems?
Did you try Eric's suggestion?
I installed the application on drive D:, not C:-- I may try to uninstall and put it on C: as I've noticed at times Adobe's apps seem very unhappy not in their absolute default locations.
I am SO glad someone else has this issue. Well, not glad you have issues- but glad to see it's not all that unique.
I suspect you won't have any success installing on C: as I installed on C:.
That problem is that Acrobat 9 takes quite a while to install and time is money.
I spoke with Adobe tech support and it took 30 minutes of the women reading her script and me saying "I did that but will try again."
I told my Manager I thought we were better off sticking with v8 until some patch is released for v9.
I am simply not confident that I will get a resolution with level 2 tech support at adobe. But I am confident it WILL take over 1hr of my time at least.
These systems are fairly vanilla IBM workstations with updated BIOS and not too many apps installed.
Too much of an uphill battle IMO to make v9 work.
But I may attempt to call Adobe again if I have downtime.
Acrobat 9 (reader and pro) do not play well with Redirected Folders in an Active Directory environment. More specifically... a redirected "Application Data" folder.
Any of my users which do NOT have roaming profiles (aka redirected folders) have no problems running acrobat 9. In other words, users who have their "Application Data" folder in "C:\Documents and Settings\username\Application Data" are fully functional and do not receive the C++ Runtime error.
Perhaps the Acrobat developers will have a fix for users of the new millenium who use UNC paths...
Hope this helps
~I was starting to think that may have something to do with it, but have no control over user accounts.
I run a computer lab with about 40 machines for 300 students-- we have to use roaming profiles, so if this bug is tied to that, well.. I guess we don't use Acrobat 9 until it's fixed.
Thanks for finding that out...
==== THIS IS WITH ROAMING PROFILE CRASHES! ====
Adobe's program iterates the network path from left to right, skipping the first word: \\Server\Folder1\Folder2\Folder3\APPLICATION DATA as it searches a user's profile for the APPLICATION DATA folder.
So starting at FOLDER1 it checks to see if it can "create" a folder. It doesnt do it, but it tries to check its access. If your not in the users profile at this point, the program MOST LIKELY cannot because its a directory NOT owned by the user. THe previous folders is something you wouldn't give NORMAL users access to.
After the program FAILS to "create" its folder because it cannot -
The program Crashes:
*R6025 - Pure Virtual function call
* The exception unknown software exception (0x40000015) occurred in the application at location 0x2e80f5e3
* C++ runtime error
* WINDOWS NAME Collision error.
=== ITS ALL OF THESE! Same error, different points in the crashing ===
I create a network drive DIRECTLY to the profile, then I update the registery to make that the WINDOWS APPDATA path. ALL of this is done on the user logon scripts. So it was just "solved" one day, except for a new drive letter appearing.
(Added to login script)
net use l: \\SERVER\USER PROFILE TREE\USER PROFILE
REG ADD "HKEY_CURRENT_USER\software\Microsoft\windows\CurrentVersion\Explorer\User Shell Folders" /v AppData /t REG_EXPAND_SZ /d "l:\Application Data" /f
For our work we use: \\SERVER\USER PROFILE TREE\%USERNAME%\%COMPUTERNAME% - so each user has SEPERATE data per computer they are on.
ADOBE - PLEASE update your code so it doesnt iterate like this! If it does RESUME on error, to see if its recoverable before the END of the interation. These are simple mistakes...
THIS will also fix the SIMILAR / SAME(?) BUG in ROXIO products.
Daniel Gorman - 7:00am Jul 22, 08 PST (#13
The issue is indeed with Folder Redirection. Mapping the profile and modifying the registry to point at the new 'Application Data' directory fixes the problem with Adobe Acrobat 9.0 Standard for me.
I have created a batch file that runs on each workstation that must run Adobe applications, and have not had any more crashes. The file executes from the following location on the local machine:
C:\Documents and Settings\All Users\Start Menu\Programs\Startup
Using this fix avoids having to create unnecessary local admin accounts.
Earlier threads in this forum incorrectly blamed this crash on the Macromedia Activation service:
C:\Program Files\Common Files\Macrovision Shared\FLEXnet Publisher\FNPLicensingService.exe
I included both a description of the problem and the workaround.
Has this problem been fixed?
Anyone know of a way to make it work in Vista?
If you want to contact Adobe either use their official tech support or
file a bug/feature request.
The one that is "more" correct but would suck to do manually on large user bases would be to give each user a hidden share ($ share).
So if before your absolute path to profile was:
Create the share \\servername\profile_directory\username$
so update folder redirection to:
The trick here is MAKE SURE you disable EVERYONE from read on the share A DEFAULT setting, and ADD that user to read. THIS IS ONLY if your structure is like mine with computer name directory PAST username.
If its just username, READ/Write/full access.
This also works for me...
Also in my tinkering to look for more elegent solutions, and maybe I was tired, I even tried "subst" with hiding drive letters. Since a subst on a network drive, always sayd "disconnected" network drive.
This is all if you cannot use the HOMEDIRECTORY feature of active directory, and such a home directory also contains their profile.
My network is quite legacy in some regards, and we actually have a homedirectory that is linked to a personal storage place for computers, not allowing home profiles to be stored there.
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders]
NEVER NEVER NEVER use %username% / %computername% in here, but you can REFERENCE it!
IN STARTUP SCRIPT (example):
-- THIS IS ONE COMMAND --
REG ADD "HKEY_CURRENT_USER\software\Microsoft\windows\CurrentVersion\Explorer\User Shell Folders" /v AppData /t REG_EXPAND_SZ /d "v:\Application Data" /fREG_EXPAND_SZ /d \\servername\%username%$\%computername%\"Application Data" /f
-- END COMMAND --
if that helps.
This fix does not work when you redirect the Application Data directory with Group Policy. The folder redirection happens as part of the logon processor before the script processes... You simply do not use a drive letter with this option in group policy - and you can't change it (to the same location) later as it resets back to the GP applied UNC path immediately.
In other words - Adobe needs to fix this, these work around solutions are not acceptable, nor functional in many situations.
My fix is to go back to Acrobat Pro 8.0, and copy the Objects, Templates and Samples directories from '%ProgramFiles%\Adobe\Acrobat 8.0\Designer 8.0\EN' to '%APPDATA%\Adobe\Designer\8.0\EN' for the user with %APPDATA% redirected to a UNC path... Which gets the LiveCycle Designer 8.0 to run with out the same basic error.
BUT now when I would like to create an new link on the desktop, he don't refresh. I have to klick on F5 to refresh. Does anybody has the same or a simular problem?
This is absolutely horrible customer service. There was nobody I could talk to besides a level 1 tech and this forum, there was nobody to even tell me if and when a fix may be released. How am I supposed to go back to the business and tell them I cant upgrade our terminal service environment because of Acrobat? That is ridiculous. I cant even go to back to 8.0, because the PDF printer doesnt work on x64 systems, which is what I am using.
All in all Adobe pinned me against a wall with no forseeable outcome. Thanks.
In fact; as juvenile as it sounds I think that this is going nowhere unless you have all your end users who are also impacted by this bug also fill out the bug form.
After some research I found that for only this user the value App Data in the key:
HKCU\Software\Microsoft\windows\Current Version\explorer\shell folders and User shell folders was set to %USERPROFILE%\Application Data. In Windows Vista the folder Apllication Data does not exist as a folder. the App data value should be set to %USERPROFILE%\App Data\Roaming.
After changing this value the runtime error was gone.
Yesterday I was messing around with NTFS file permissions. When I used my PC today I opened acrobat to view my pdf and it brought up the Visual C++ runtime error and closed right away. I rebooted, troubleshooted, did research, rebooted... I figured I could unistall it, I couldnt even do that..
Well to make a long story short... I denied my user to the C drive. Yes I actually allowed it on one NTFS permission and had deny on a special permission... Deny outweighs Allow... Well once I allowed the user access to the C drive.
Adobe works fine again!!! Check your NTFS permissions, make sure your user has access to the drive where Adobe is installed.
Not very promising. Has anyone who ran into this issue with roaming profiles before tried 9.1? Any differences in how it runs? It implies it may work better now. That said, I don't feel like messing with it if someone else has already tried it and it doesn't work.
I cannot believe for a "professional" level application that Adobe isn't supporting roaming profiles in Windows. That's only been a standard Windows way of doing business for what now, 10-15 years? And it worked fine as recently as Acrobat 8? I would hope they mean next major release as being 9.2, but I am afraid they mean 10.0.
Unacceptable. Unless this is fixed soon I don't see myself pushing to upgrade our Adobe licenses again.
Again, these issues have been addressed in Acrobat and Reader 9.1.