2 instances of Acrobat PRO DC running concurrently
One Acrobat instance installed but 2 instances of Acrobat PRO DC running concurrently prevent PDFs from opening. Only solution is to quit "both" Acrobats and try again. Uninstalling and reinstalling Acrobat does not help. Uninstalling and reinstalling the entire ACC suite does not help either. Problems observed in three separate, not networked Macs. No Acrobat Free Reader installed on the systems either.
Hi Andres,
Can you elaborate on the behavior here:
1. What happens when you open a PDF with Acrobat? Does it trigger two instances of Acrobat.
2. When you just launch Acrobat from finder, does that also trigger two separate instances.
Thanks
-
Andres F. Cathalifaud commented
Oh. If I launch Acrobat by double clicking the very App icon, only one Acrobat will launch.
The error also occurs sometimes when I open a single PDF and two Acrobats try to lunch at one. That causes neither one to run properly and the only way out is Force Quit them both.
Both instances lead to the same application in the same folder or directory: User/Applications/Adobe Acrobat DC/Adobe Acrobat.app
-
Andres F. Cathalifaud commented
Hello. This may happen in one of two ways (by now, I've got plenty of experience with the symptoms). I open a PDF and all is well. I try open another one (double click, from the Finder) and nothing happens. I check to se the status of Acrobat and I notice two instances open in the Launch bar. The Force Quit window shows two Acrobats: "Acrobat Pro DC" and another that may be called the same or "Adobe Acrobat". The Activity Monitor also shows two instances running concurrently.
When two Acrobats are running, I cannot open another PDF until I Force Quit one or the two.
I have shared in the Acrobat Forum screen captures that show some of what I described above. I can send this to you separately if you'd like.
To clarify even more: I only have one Acrobat installed (no additional older or Reader versions). This is behavior that is random (I cannot duplicate it on purpose) BUT I see in two other Macs (so, not isolated). It looks like other users have reported the same or similar as well. Thank you.