Reader 9.0 AcroRd32.exe caused Microsoft Visual C++ Runtime Library error

Hello

I am very dissapointed to discover that in Adobe CS4 the acrobat reader bug still exists.

The only solution is to either map the share to a drive letter and modify the registry so the profile is directed there (as above) but I have found that this causes serious problems with other programs and can cause profiles to not be loaded properly due to the drive not getting mapped in time.

I then created a more elaborate shortcut script which would modify the profile path and then open the program and modify it back but this also caused problems with other programs.

This problem has occured ever since Acrobat Reader Pro/Standard were released. It is surprising how difficult it is for Adobe to create an application for viewing pdfs which does not instantly crash when you open it.
Surely a major bug like this should not take many months to fix and when you have to remorgage your house to buy the CS4 Master Collection I feel you should at least be able to view pdfs without getting "This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information". So can you give me more information and/or possibly fix this sometime?

My only real solution which was also the same in CS3 is to avoid installing the Acrobat program and use Foxit Reader or to install Acrobat 8 which does not suffer from this problem/or 6 Pro to edit pdfs which I still have a licence for.

Thanks
Robin

I have created some Special GPO that links the Appdatafolder to %userprofile%\Appdata and applied the GPO only to the Users of Acroread/Acrobat. I'm very unhappy with this solution/wordaround, but it is working.

Still waiting for a Hotfix.

Hi all
After I finished the workarround with changing the APPDATA path to a hidden network drive, Adobe Acrobat 9 is now working.

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?

To change the AD GPO to use drive letter in folder redirection instead of UNC path is not possible, as it reverts to \\ unc path in the GPO...

So here is another company that is waiting for the fix for reader 9.0

I am wondering if there is a way to get adobe to use the application data in the all users profile stored on the local machine instead of the app data in the redirected folder. I have in the mean time decided to not redirect the app data folder. I am still able to redirect all other folders. This will require a little more time for users to log in, however it should not be too bad (I hope). If adobe would just use the AppData folder in the all users profile, then they would not need to worry about UNC paths, all though I don't know why a company today would not support UNC's.

If anyone has any ideas about how to make this work or if it would work, please let me know.

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.

Edit: I've cross-posted this in a few of the threads so far... There should be a way for the 15 or so active threads on this to be brought together...

Has Adobe coming up with a scheduled date for a fix?

One of our customers stopped the rollout of Reader 9 and therefor stopped the complete Adobe Forms Project.
The described "workaround" is not accepted by our customer.

Regards

Martin

I've had my support case for this open for more than 2 months now. I emailed them last week asking for an update.

More than a week later, they haven't even bothered replying.

Why Doesn't adobe do anything about this?
I can't believe that Support is so... not supportive on this incident.
We spent about 45 minutes trying to figure out if there was a way to customize this in adobe customization wizard.

I would think that there should be a way to customize it in the registry..
like change the path of the application data folder?
or maybe statically map it always or somthing.

Has any one had any better response from support on this issue?

It looks like this is a big snag for Citrix and RDP Terminal Servers as well.
http://www.adobeforums.com/webx/.59b5f923?@@