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

Currently Being Moderated

40. (its_privacy),

Oct 20, 2008 1:50 AM in reply to (AndrewLippett)

Report

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.

|

Mark as:

Currently Being Moderated

41. (Robin_Wilson2),

Oct 20, 2008 1:04 PM in reply to (AndrewLippett)

Report

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

|

Mark as:

Currently Being Moderated

42. MichaelKazlow,

Oct 20, 2008 3:59 PM in reply to (Robin_Wilson2)

Report

Robin,

It naive to think that Acrobat and/or Reader would be changed with the
release of CS4 if it was not fixed before it was released. The version
in CS 4 includes the same version of Acrobat as was included in CS 3.3
and the technical suite interim update as well. When/If it is fixed it
will be distributed via the update mechanism for all running versions of
Acrobat and Reader 9.

Mike

|

Mark as:

Currently Being Moderated

43. (RonnyT),

Oct 20, 2008 10:21 PM in reply to (AndrewLippett)

Report

To downgrade to acro reader 8 and install Foxit for those that get ver. 9 pdf documents is our best solution, and more and more people are liking foxit ... so we are contemplating to just start to use foxit for all our pdf needs since Adobe is not willing to fix this... Too bad really, they must be driving alot of customers away...

|

Mark as:

Currently Being Moderated

44. (Robin_Wilson2),

Oct 20, 2008 10:48 PM in reply to (AndrewLippett)

Report

It's just when it costs so much money you would think a major bug like this would be A, discovered by beta testers before the 9 release or B, fixed by now as it has been many months and when every other application was updated in CS4 I would have at least expected a ver 9.000001 that would just fix this very annoying bug as apart from this the program is quite good.

As I understand it, Acrobat looks at the root of the UNC share and then tries to create a folder which alredy exisits consisting of the name of the user. There is no error handling in the code so the program just crashes. The error seems to be in one dll file.

I had to give people log on locally rights just to use this program and this makes the machines less secure as it is harder to apply security.

|

Mark as:

Currently Being Moderated

45. (James_Schlackman),

Oct 21, 2008 9:37 AM in reply to (AndrewLippett)

Report

I called Adobe again today to enquire on the status of my support case for this. It was raised 3 months ago on Saturday.

After 20 minutes on hold, here's how the conversation went after I gave him the case number:

"Oh, this is an old case."

- "Yup"

"Uh, it seems to have been closed for some reason."

- "OK, that's interesting as I specifically agreed with the last guy it would not be closed until a fix was available."

"... the person who closed it does not work here any more."

GREAT.

I then spent the next 10 minutes explaining to this poor guy (who was clearly not near the support level dealing with this kind of problem) why the workarounds that had been previously suggested were completely unsuitable for enterprise implementation. He admitted all he could do is pass that feedback back up as he had no further information. He said he would get back to me ASAP.

I'll keep you posted.

|

Mark as:

Currently Being Moderated

46. (MarTay),

Oct 21, 2008 10:23 AM in reply to (AndrewLippett)

Report

Thank you James,
My case on the issue was closed in a similar way and the work around is not working for us either.

|

Mark as:

Currently Being Moderated

47. (James_Schlackman),

Oct 22, 2008 9:23 AM in reply to (AndrewLippett)

Report

I received an update earlier today:

]There is no solution yet.
]The issue will be fixed by the next Acrobat update. Please make sure your auto updater is active and/or check the Adobe website for updates.

That's all I was given. I have enquired as to if there is an expected timeframe for said update.

|

Mark as:

Currently Being Moderated

48. (James_Schlackman),

Oct 23, 2008 4:36 AM in reply to (AndrewLippett)

Report

Well, we have our answer.
]"We don't know when the next update will be released.
]I am very sorry for the inconveniance."

(sic)

I love being an Adobe customer.

|

Mark as:

Currently Being Moderated

49. (MarTay),

Oct 23, 2008 6:30 AM in reply to (AndrewLippett)

Report

Awesome?

|

Mark as:

Currently Being Moderated

50. (Robin_Wilson2),

Oct 25, 2008 2:20 AM in reply to (AndrewLippett)

Report

Oh well maybe it will be fixed in a few years.

|

Mark as:

Currently Being Moderated

51. (AlessandroB),

Oct 27, 2008 10:45 AM in reply to (AndrewLippett)

Report

It's incredible. Such a fatal bug in a final version... I wonder which kind of testing they have at Adobe...
I'm a "free version" Reader user, I haven't paid for Acrobat Reader so I cannot complain that much.. but I imagine how pleased should be Pro version users...
In this forum, I discovered the existence of Foxit. I've just installed it, I think this is definitely the best "fix" at the moment...

|

Mark as:

Currently Being Moderated

52. (MarTay),

Oct 27, 2008 11:16 AM in reply to (AndrewLippett)

Report

"In this forum, I discovered the existence of Foxit. I've just installed it, I think this is definitely the best "fix" at the moment..."

For the reader this is true, but acrobat pro still has the problem..

|

Mark as:

Currently Being Moderated

53. (DDave_Sawyer),

Oct 30, 2008 7:15 PM in reply to (AndrewLippett)

Report

You have been heard! In case your support rep hasn't contacted you, this bug "Crash on launch if domain user APPDATA folder has been redirected." has been fixed. It will go out in the first patch to 9.0.

|

Mark as:

Currently Being Moderated

54. (Ethan_Connor),

Oct 30, 2008 7:23 PM in reply to (AndrewLippett)

Report

When?!?!

|

Mark as:

Currently Being Moderated

55. (James_Schlackman),

Oct 31, 2008 12:10 AM in reply to (AndrewLippett)

Report

That's the only question that matters, isn't it? (Along with "is it really fixed", I suppose).

|

Mark as:

Currently Being Moderated

56. (MarTay),

Oct 31, 2008 4:54 AM in reply to (AndrewLippett)

Report

And this aforementioned patch... its due to hit the stores... When?
and is it called "version 10"?

|

Mark as:

Currently Being Moderated

57. (john_galloway),

Nov 11, 2008 7:48 AM in reply to (AndrewLippett)

Report

November 11th and the current download of reader V9 from Adobe is still unfixed.

How hard can it be, really?

Hurrah for Foxit.

John Galloway
University of York, UK

|

Mark as:

Currently Being Moderated

58. (Scott_Battaglia),

Nov 11, 2008 8:09 AM in reply to (AndrewLippett)

Report

I gave up waiting... I have migrated the office to Foxit Reader... We just need to be able to view documents. I can not undertand why Adobe has not fixed this issue as I am sure there are many roaming profile user sites out there that would like to use Reader 9.0

|

Mark as:

Currently Being Moderated

59. (Robin_Wilson2),

Nov 11, 2008 10:15 AM in reply to (AndrewLippett)

Report

Yes give us the source code as I'm sure quite a few of us could fix it in our lunch breaks!

It was broken in CS3, CS3.3 and now CS4. Acrobat seems the only program that remains un-updated in CS releases and the one that most needed updating.

|

Mark as:

Currently Being Moderated

60. MichaelKazlow,

Nov 11, 2008 12:04 PM in reply to (Robin_Wilson2)

Report

As users with roaming profiles, it is a very important issue to you.
However, in the scheme of things, it may not be very important to the
overall user base. If this is a problem for your company, have everyone
in your company report the bug in the Adobe Bug report form. The more
users they know are effected, the more likely it will be fixed. Believe
me if IBM, ATT or the DOD had the problem, it would be fixed ASAP. Your
company needs to help make it an important issue to Adobe.

Mike

|

Mark as:

Currently Being Moderated

61. (James_Schlackman),

Nov 19, 2008 1:31 AM in reply to (AndrewLippett)

Report

Adobe sent me an invite to their annual Adobe Customer Engagement Survey.

You had better believe I made my feelings on this known.

|

Mark as:

Currently Being Moderated

62. (memanjack),

Dec 3, 2008 5:04 PM in reply to (AndrewLippett)

Report

For our 2008 terminal server my workaround was to disable browser integration. (So instead PDF's open in a separate window, which is actually wise if your running a terminal server, because when browser integration is enabled, each instance of adobe reader stays open until the browser is closed)

Anyway to achieve this I got a copy of the msi and reinstalled Adobe Reader 9 with the following MSI switch

msiexec.exe /i AcroRead.msi /qn DISABLE_BROWSER_INTEGRATION=YES

|

Mark as:

Currently Being Moderated

63. (buffaloboy),

Dec 10, 2008 7:40 AM in reply to (AndrewLippett)

Report

Well, I downloaded the latest version today (12/10/08) from the web site, and still having the same issue. We are using Folder Redirection, but only for My Documents and Application Data. Approx. 1800 users will be affected if we roll this out through the company.

|

Mark as:

Currently Being Moderated

64. (MarTay),

Dec 10, 2008 8:04 AM in reply to (AndrewLippett)

Report

msiexec.exe /i AcroRead.msi /qn DISABLE_BROWSER_INTEGRATION=YES

Disableing the browser integration does not resolve the issue of application data directory redirection.

|

Mark as:

Currently Being Moderated

65. (Hunter_French),

Dec 17, 2008 8:26 AM in reply to (AndrewLippett)

Report

What a joke. We got burned by this today and the latest downloader does not have any fix that I am aware of. This is horrible Adobe, horrible.

|

Mark as:

Currently Being Moderated

66. (Ethan_Connor),

Dec 17, 2008 10:29 AM in reply to (AndrewLippett)

Report

I guess the question is... Will Acrobat 8 be the last Adobe version we will ever be able to use? And if so... What are your plans to support users once other websites start publishing documents that are incompatible with Acrobat 8?

|

Mark as:

Currently Being Moderated

67. (AlexS),

Dec 21, 2008 5:31 AM in reply to (AndrewLippett)

Report

Same here - ADOBE WE NEED A FIX! - ADOBE ACROBAT 8 WORKED!!!
Grrrr - this post was started in July and it is now Dec!

|

Mark as:

Currently Being Moderated

68. (jmgcg),

Dec 23, 2008 3:08 AM in reply to (AndrewLippett)

Report

I have the same problem but with Photoshop CS4

"Microsoft Visual C++ Runtime Library
Program: C:\Program Files\Adobe\Adobe Photoshop CS4\Photoshop.exe
This application has requested the runtime to terminate in an unusual
way.
Please contact the applications support team for mor information."
It was working, i could open photoshop at least one time, after that,always the same error. CS3 worked well.
Is there any cure for this ?
Thanks

|

Mark as:

Currently Being Moderated

69. (MarTay),

Dec 23, 2008 8:15 AM in reply to (AndrewLippett)

Report

I wonder how hard it would be to get on the phone with developers?

|

Mark as:

Currently Being Moderated

70. (CH!),

Dec 23, 2008 8:33 AM in reply to (AndrewLippett)

Report

by calling Adobe Support...

"I'm sorry, but thats not supported"

:p

|

Mark as:

Currently Being Moderated

71. (laceyerik),

Dec 31, 2008 3:31 PM in reply to (AndrewLippett)

Report

With this adobe has completely lost my business. Foxit for reader and docudesk for writer... Doesn't get any simpler that that. Cheaper and more reliable!!!!!!! Don't have time to waste on "Premuim" crap software!!!!

|

Mark as:

Currently Being Moderated

72. (Captain_Cook),

Jan 3, 2009 12:38 PM in reply to (AndrewLippett)

Report

Since Adobe still has not posted a fix for this bug after about 6 months, I will.

Look at PDF-Xchange (http://www.pdf-xchange.com), Foxit Software (http://www.foxitsoftware.com/products), and CutePDF (http://www.cutepdf.com).

CutePDF is a free PDF generator that works very well. I install it on most systems.

I guess Adobe is going to give up on selling Acrobat to corporate entities who redirect the Application Data folder in Windows domains.

I'm guessing no one in Adobe's corporate offices are looking at the seemingly inevitable downward trend in sales numbers.

|

Mark as:

Currently Being Moderated

73. (Ethan_Connor),

Jan 6, 2009 1:02 PM in reply to (AndrewLippett)

Report

I strongly suggest that everyone who has been impacted by this bug submit the Bug Report Form...

http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

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.

|

Mark as:

Currently Being Moderated

74. (peterson_glenn),

Jan 7, 2009 4:17 PM in reply to (AndrewLippett)

Report

FWIW, I get similar symptoms with a very simple configuration.

Users homed to C: work fine.
Users homed to D: don't work.

Vista Ultimate 64 Bit SP1.

I don't claim this is the same issue, but the symptoms look the same to a user (me).

I also see this w/ the Picture Manager accessory of Office 2007.

Moving to Foxit seems to fix the Reader (but not the Picture Manager) problem. I'm unlikely to go back until this is well and truely fixed.

|

Mark as:

Currently Being Moderated

75. (Al_Lebeau),

Jan 8, 2009 7:47 AM in reply to (AndrewLippett)

Report

Thanks Ethan for that link - posted our issue there - hope it helps get Adobe moving more quickly.

|

Mark as:

Currently Being Moderated

76. (MarTay),

Jan 8, 2009 8:29 AM in reply to (AndrewLippett)

Report

I posted it too!
I also called them again... "we are aware of the issue,they sent me a link to this thread as a work around, and then... Thank you for calling."

|

Mark as:

Currently Being Moderated

77. (Richard_Moore),

Jan 25, 2009 6:23 AM in reply to (AndrewLippett)

Report

I can't quite believe this is still outstanding.

Regardless of how bad this looks on Adobe as an example of their apparent disregard for existing customers, they are actually selling a product that claims to be compatible with Windows environments. It is not. A subset does not equal the full thing and Adobes beta testers have really fallen short of the mark on this one.

Like other customers I have ended up being forced in to implementing alternative products. The response times have been abysmal and it is inconceivable how badly Adobe has handled this. Senior representatives should have stepped in to calm things down, but it looks like the damage has been done now.

It's not atypical for Adobe to be slow with development (getting with 64 bit years later than everyone else springs to mind) but this is a known bug and should be given priority over new feature sets.

|

Mark as:

Currently Being Moderated

78. (Allen_Jacobsen),

Jan 27, 2009 6:11 PM in reply to (AndrewLippett)

Report

Its pathetic, even a request for V8 was closed by support. when I reopened it my case "disappeared"!

|

Mark as:

Currently Being Moderated

79. (Bill_Kov),

Jan 27, 2009 6:30 PM in reply to (AndrewLippett)

Report

Hello Andrew and all -
I've had an open ticket on this in tech support for a while and in reading some of these threads - I'm still confused.

I'm on a 32 bit Vista platform.

It appears that the best answer that I see is to uninstall this trouble maker and find a copy of the last version.

I'm currently 8 projects back because I can't read pdf files that clients have sent me.

I'll check back here from time to time but if anyone has a better suggestion,I'm up for it.

Bill

|

Mark as:

Adobe Reader

More Like This

Incoming Links

Bookmarked By (0)

Adobe Reader

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

Jul 11, 2008 4:56 AM

More Like This

Incoming Links

Bookmarked By (0)