Acrobat Pro 9 crashes when opened on network accounts

[_msingerman_]

We use network logins via Open Directory on our network. For users with either 10.5.4 or 10.4.11, whenever they try to open Acrobat on their network accounts, it hangs and eventually crashes. It will open fine on local machine accounts. This has been seen on all machines, be their Intel or G5. Here is the crash log via console. Any ideas?

Process: AdobeAcrobat [10758]
Path: /Applications/Adobe Acrobat 9 Pro/Adobe Acrobat Pro.app/Contents/MacOS/AdobeAcrobat
Identifier: com.adobe.Acrobat.Pro
Version: 9.0.0 (9.0.0)
Code Type: X86 (Native)
Parent Process: launchd [83]

Date/Time: 2008-09-03 16:29:56.664 -0400
OS Version: Mac OS X 10.5.4 (9E17)
Report Version: 6

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libSystem.B.dylib 0x921b2b9e __kill + 10
1 libSystem.B.dylib 0x92229ec2 raise + 26
2 libSystem.B.dylib 0x9223947f abort + 73
3 libstdc++.6.dylib 0x93706005 0x936be000 + 294917
4 libstdc++.6.dylib 0x9370410c __gxx_personality_v0 + 1108
5 libstdc++.6.dylib 0x9370414b std::terminate() + 29
6 libstdc++.6.dylib 0x93704261 __cxa_throw + 101
7 com.adobe.Acrobat.framework 0x8097b2cb CopiesPagesPDE_Open + 8743607
8 com.adobe.Acrobat.framework 0x8093cbb6 CopiesPagesPDE_Open + 8487842
9 com.adobe.Acrobat.framework 0x8093be15 CopiesPagesPDE_Open + 8484353
10 com.adobe.Acrobat.framework 0x8093d400 CopiesPagesPDE_Open + 8489964
11 com.adobe.Acrobat.framework 0x80d05fc7 0x7feb8000 + 14999495
12 com.adobe.Acrobat.framework 0x80d06172 0x7feb8000 + 14999922
13 com.adobe.Acrobat.framework 0x808c7a88 CopiesPagesPDE_Open + 8008308
14 com.adobe.Acrobat.framework 0x807709d0 CopiesPagesPDE_Open + 6603196
15 com.adobe.Acrobat.framework 0x80770bbb CopiesPagesPDE_Open + 6603687
16 com.adobe.Acrobat.framework 0x80005c8b RunAcrobat + 1357585
17 com.adobe.Acrobat.framework 0x800059c0 RunAcrobat + 1356870
18 com.apple.CoreFoundation 0x96973b45 CFRunLoopRunSpecific + 4469
19 com.apple.CoreFoundation 0x96973cf8 CFRunLoopRunInMode + 88
20 com.apple.HIToolbox 0x92cc9da4 RunCurrentEventLoopInMode + 283
21 com.apple.HIToolbox 0x92cc9bbd ReceiveNextEventCommon + 374
22 com.apple.HIToolbox 0x92cc9a31 BlockUntilNextEventMatchingListInMode + 106
23 com.apple.AppKit 0x948b7505 _DPSNextEvent + 657
24 com.apple.AppKit 0x948b6db8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
25 com.apple.AppKit 0x948afdf3 -[NSApplication run] + 795
26 com.adobe.Acrobat.framework 0x7febb18c RunAcrobat + 3090
27 com.adobe.Acrobat.framework 0x7feba6b8 RunAcrobat + 318
28 com.adobe.Acrobat.Pro 0x00002e8b start + 2371
29 com.adobe.Acrobat.Pro 0x0000264a start + 258
30 com.adobe.Acrobat.Pro 0x00002571 start + 41

Thread 1:
0 libSystem.B.dylib 0x9214b68e __semwait_signal + 10
1 libSystem.B.dylib 0x9217636d pthread_cond_wait$UNIX2003 + 73
2 com.apple.ColorSync 0x917f7460 pthreadSemaphoreWait(t_pthreadSemaphore*) + 42
3 com.apple.ColorSync 0x91809d92 CMMConvTask(void*) + 54
4 libSystem.B.dylib 0x921756f5 _pthread_start + 321
5 libSystem.B.dylib 0x921755b2 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x9214b68e __semwait_signal + 10
1 libSystem.B.dylib 0x9217636d pthread_cond_wait$UNIX2003 + 73
2 ...ple.CoreServices.CarbonCore 0x9376724f TSWaitOnCondition + 126
3 ...ple.CoreServices.CarbonCore 0x9374618e TSWaitOnConditionTimedRelative + 202
4 ...ple.CoreServices.CarbonCore 0x93766ecc MPWaitOnQueue + 208
5 AdobeACE 0x7fc1dd8d ACEMPThread::Task(

[Phillip_M_Jones]

in one ne of two places:

Library > Internet Plugins Directory

or

Username (short name you used name Computer) > Library > internet Plugins

look for a plugin with the name Adobe it. Simply drag to desktop before install the PDFViewer Plugin.

If for some reason you have duplicates remove all plugins from the in the username > Internet plugins and drag to Main Library > Internet Plugins.

if it say you are replacing an newer version with an older version stop - throw away.

If on the other hand it says you replacing and older version with a newer version allow it to do so.

[Patricia_Isaac]

I certainly thank you for all your help with this. I did all you said

and installed Schubert and I still couldn't open a pdf in Safari.

Well, I tried with acrobat again but it told me that it couldn't find

the plug in. I tried to open Reader alone and it worked (wouldn't

before). To make a long story short, I put the plug in back and tried

again. I was told I needed to update Adobe Acrobat to 9.1. I did and

it all works now....go figure. Funny it didn't indicate an upgrade

before.

Thanks so much for your help.

Pat

www.fineartbypatricia.com

http://newbypat.blogspot.com/

[Phillip_M_Jones]

Sorry I was no better help.

One tip. Check version see if it 9.1 or 9.1.1. if not you need to update to 9.1.1.

[Frank Fechner]

We have the very same problem with Acrobat 9 Pro (from the beginning upt to the most recent version 9.1.3) here.

Local users can use Acrobat 9 (local install on all maschines) without any problems, the same for mobile users (server-synced version of networked homes) which are used for MacBooks - flawless. But any user who have an account and home-dir on the server (still 10.4.11) cannot start Acrobat 9 without seeing crashing it seconds after the start.

I think the whole problem is caused by the document-tracking-database of acrobat which is SQLite based since Acrobat 9 (was MySQL in Acrobat 8.x) and the lack of support for advisory locking in AFP filesystem (which is used for the networked homes) which leads SQLite to report that the "database is locked" whenever Acrobat tries to use it. The SQLite-DB-file itself resides somewhere in the users ~/Library folder and thus cannot be used.

It seems that MySQL didn't had such problems (but others).

Adobe should update the SQLite-Library used within Acrobat (or make it an optional turn-off-completely feature ) accordingly to Apple (they fixed their stuff allready) - refere to http://alastairs-place.net/2006/07/sqlite_and_mac/ .

I had other apps using SOLite as storage that have similar falures on networked user accounts - but most of them didn't crash even when not usable for me.

I hope that helps Adobe to fix that annoying crash-thing Acrobat for hundreds and thousands of bucks payed by brave users ... damn!

Sorry

FF

[John_Lockwood]

ARGHHH!!!!!

I first hit this bug in 2005 when Acrobat Pro 7.0 was launched, I then spent TWO YEARS pursuing this with Adobe through versions 7.0.2, 7.0.3, 7.0.5, 7.0.7, 7.0.8, 8.0, and eventually got them to fix it in Acrobat Pro 8.1 in 2007.

Recently I have started replacing ageing PowerPC Macs with new Intel ones and hence upgrading from CS2 to CS4 which includes Acrobat Pro 9 (9.2). I am therefore absolutely aghast that this bug has been reintroduced. What's worse, it also affects Acrobat Reader 9.2 as well. Neither Acrobat Pro 9.2 or Reader 9.2 will successfully launch when used via Network Login accounts (local and portable accounts work fine).

Note: It affects Mac OS X 10.4.11 and 10.6.2 clients and based on comments here also 10.5.x.

[akiro2]

We have had the same problems on an OpenDirectory Network, but not with all users on every machine. So I started debugging user by user and Mac by Mac.

I found a solution for our Mac Network: On the local machine go to /Users/Shared/ > there you will find a folder named 9.0_x86, which is owned by the user (admin) who has installed Adobe Acrobat 9.x.

Now just add read/write rights for your network group (which contains all users who usually work on that machine) to this folder and all sub objects.

Now every network user of this group can open Acrobat without problems.

I hope this will help some of you!

Greetings Martin Skladal

[mpola2702]

Hi Martin,

but on the local machine in /Users/Shared/ I don't have the folder "9.0_x86", this is in Library/Application Support/Adobe/Acrobat...

So I have to change for every network user the link for the  folder "9.0_x86"?

Thanks,

Mario Pola

[paul_nord]

How can Adobe not have fixed this yet?

Does it really take more than two years?

Egads!

[hirokiSince1998]

paul.nord wrote:

How can Adobe not have fixed this yet?

Does it really take more than two years?

Egads!

Seems not yet. How annoying!

BTW, I found that only a single file "SharedDataEvents" is relevant to this bug. Our workaround is shown below, for future reference.

1. sudo mkdir -p /Users/Shared/Library/Application\ Support/Adobe/Acrobat/9.0_ppc

2. sudo touch /Users/Shared/Library/Application\ Support/Adobe/Acrobat/9.0_ppc/SharedDataEvents

3. sudo chmod 777 /Users/Shared/Library/Application\ Support/Adobe/Acrobat/9.0_ppc/SharedDataEvents

4. cd ~/Library/Application\ Support/Adobe/Acrobat/9.0_ppc

5. rm SharedDataEvents

6. ln -s /Users/Shared/Library/Application\ Support/Adobe/Acrobat/9.0_ppc/SharedDataEvents .

Hiroki

[serogers1970]

December 2010 -

Reader X is now out, and the problem still persists.

Creating a local folder and running a Terminal command for every user on every machine they use, is NOT a fix.

I know Adobe and Apple have their battles going on right now, but seriously...this is ABSURD!

Maybe one of these days soon we will have a patch that will actually fix the problem.

Get your act together Adobe!

[John_Lockwood]

Adobe have copied all Microsoft's worst habits - product activation, no proper manual included, rip off pricing, and of course failing ever to fix major bugs.

As a reminder, for me at least, switching to using NFS to share network home directories instead of the more standard AFP seems to have fixed this problem for me. I did not make this switch to cure this issue, but since I did (for a different reason) I have not had this problem.

[BitingChaos]

I know this is a super-old thread, but I noticed that we could load Acrobat only if the NFS mounts were exported with the setting to map "Root to Root", so that the local root account has access to the share.

Even though a regular user runs the Acrobat program, on first-launch it will run background tasks (like MoverTool or installd) as the local *root*. With a default NFS export (where local root has no rights to the NFS share) this causes the background task to fail and even crash. So the first Acrobat initialization fails, and the program never runs.

Of course, allowing local root access to the NFS is not something you'd want.

It's a shame Adobe is this sloppy with their program, and refuses to fix it after all this time.