Actobat 8.0 Pro Closes Automatically

For the group, We have installed Acrobat Pro 3D 7.07 after uninstalling 8.0 completely. This has yet to fail, regardless of the client or platform. We are using this successfully on Vista as well. We ran the update to 7.08, and it still works fine. I agree with the earlier statements that you should back down to Acrobat 7 to get working. There are a number of places to download a demo, which is good for 30 days, but if you have trouble finding one, feel free to contact me.

It is too bad that we have not been given any options from Adobe.

JM

None of the clients we work with, nor any of our customers are reporting any message about "Organizer database is damaged..."

Most have reported the premature closing, with no messages at all. I would say that it is definately an issue, one that deserves to have its own thread (which it does). Can you explain how you think there is a connection with this issue?

JM

Here is what I have found so far.

We are running Vista on all of our clients, and have been told by adobe that Acrobat 8 is designed to run on Vista. We have seen this problem on a variety of platforms including laptops and desktops, regardless of the client OS. There is no indication for a connection to the video hardware, as we see this on nVidia, ATI, and even some older type cards. We have also reasonably confirmed that it is not likely a corruption of any of the installed files... removing all of the installed files from ALL directories and reinstalling does not eliminate the problem. Same thing for the registry entries. So what is left?

We believe that the problem lies firmly in the files installed by Adobe Acrobat that deal directly with the writing and gathering of information written to the registry. Our developers feel that this would explain almost all of the problems being reported here. Adobe has written their dlls specifically in this way.

We have been corresponding separately with Jeff Moran, however like the rest of the group reporting on this issue, we have seen little actual support for the issue. We have a number of commitments for contacts with engineering (theirs to ours), however this has thus far not happened. His voice mail says that he is out until the 8th of Jan. Our team of developers can not take the issue much further than what we have outlined, as we do not have access to the internal workings of the program, so our only recourse at this point is to either wait for Adobe to rectify the issue (hopefully the developers will be back off of vacation to start working again) or start motivating management to move it along using fiscal measures. I have to think that a substantial problem like this with customers seeking remuneration and/or moving to a competitive product HAS to get their attention.

If anyone has any productive thoughts as to a resolution given these circumstances, I know that we would be thrilled to hear them, as I am sure the rest of the forum would. Aside from this, we are regrettably at the mercy of the engineers, not tech support, to solve this issue.

Happy Holidays,
Jeff MacMillan

Jeff MOran, you seem to be familiar with Organizer's database. Please take a look at the thread that's headed "Organizer database is damaged..." and see if you have any thoughts.

OK Guys. I had the same problem that everyone else was having. I tried everything from re installing from another profile, and also installing it on a different machine.

Finally I took a different approach. I uninstalled the entire app, got rid of everything on my PC/Laptop that had acrobat in the name. I did not go through the registry, just files on the local disk.

After I installed it, I killed my wireless connection, and Activated the program over the phone. After punching in all the friggin numbers and letters, Acrobat no longer closes after 8 seconds.

I just had to let everyone know how I did this. I have been watching this post for about a week or so, and Adobe has not done a thing about it.

Hope this helps Everyone !!

PS for a good online poker game visit

http://www.pokerbreakout.com

Still accepting business from our U.S. Players !

Well...

I'm glad to hear that your problem is fixed Otto...but on two separate computers...with two different ATI cards...the problem is still there...

This isn't a NVidia problem....it's ACROBAT....

True..there may be some conflicts...but a lot of us don't even have NVidia...(and I never have).

I've even tried in different monitor and screen size configurations...because I remember years ago, Quickbooks had the same problem..and it turned out that it would only work correctly in 800x600..until the updates came out.

Besides Adobe's lack of urgency to this problem...the only other, really "in common" thing here is that a lot of us upgraded via windows update recently.

There is also a similar problem with some folks on this forum regarding Acrobat 7.08....and the video cards didn't seem to be the "main" problem with the reason for this constant crashing.

Acrobat 8 is closing after 8 sec.
I have WIN XP and ATI Radeon and that problem must have
another reason.
Now I have installed Acrobat 7 and it works.

Acrobat 8 Professional. was working fine until I updated my NVIDIA GF drivers to...

Windows XP/2000 32-bit
Version: 93.71
Release Date: November 2, 2006

Since the above graphic card update Acrobat is now closing automatically after about 6 seconds.

I went back to my previous NVIDIA drivers Installing the previous version...

Windows XP/2000 32-bit
Version: 91.47
Release Date: September 14, 2006

Acrobat 8 closing problem solved.

Unfortunately I don't who is worse with their tech support. Nvidia or Adobe.

Nope. I think I've Made up my mine...Nvidia, by a very, very, very small margin !

Hi, I'm using ATI Radeon, and IMHO don't think the problem is there..

Just how many of you have NVidia Video Cards. It might have something to do with the GPU Acceleration in Acrobat... My friend and I have identical machines from Memory to Motherboard to CPU and hard drives. THe only difference is the Video Card. Mine is an ATI and his is NVidia. Mine works fine, his does not... Go figure...