Accessibility

Forums


Sorry, search is not currently available.



Reader 8 Crashes when started from external program

Hi,

I am using TexnicCenter to create pdf documents from Latex code.
The tool starts Adobe Reader 8 with the following DDE command:
[DocOpen("%bm.pdf")][FileOpen("%bm.pdf")]

And closes a document before the new version is shown with this DDE command:
[DocClose("%bm.pdf")]

The pdf documents opens and displays fine, but when I try to close either the document,or the reader, or close it with the above DDE command the reader crashes.

Any ideas? Is this a bug?
Thanks,
Petra
Dec 6 '06
11:28 AM Pacific


Subscription Options

You can subscribe to keep track of new messages posted to this area. You can check all or none of these options.




Sign in or create an account to reply.
Replies (indexing)
1 – 21 of 21 First | < Prev | Next > | Last

1 new replies | all replies
View   60


Reply 1 of 21

No solution, just a confirmation.

Our app has nothing to do with Latex, but we are experiencing the exact same problem.

Once a document has been brought up with DDE, it appears Reader becomes unstable. If we try to do anything with that document, Reader immediately crashes.

Has the DDE interface changed? The IAC Reference on the site is still for Adobe 7.0.5

To politely quote Petra, "Any ideas? Is this a bug?"

Hopefully there can be some kind of fix rather than a workaround, we don't want our project to artificially stall at version 7.

Thank-you.

Bruce
Dec 7 ' 06
8:30 AM Pacific


Reply 2 of 21

A workaround for now: if you use TeXnicCenter to open two PDFs you can work as usual without the crashes. Just open an additional *.tex file, compile this one and view it. Leave it open and then you can compile and view your regular *.tex file without problems. However, this does not fix the actual problem.

Cheers,
Petra
Dec 7 ' 06
2:27 PM Pacific


Reply 3 of 21

I can confirm that this is a bug in Acrobat Reader 8.0 I submitted the bug at http://www.adobe.com/misc/bugreport.html, but will apparently not get a response.

It is hard to understand how version 8 could ship with DDE support that is this broken.

Erik
Dec 8 ' 06
10:17 AM Pacific


Reply 4 of 21

I also have the same problem. I don't use TeXnic Center, but another editor with pdfopen and pdfclose (http://magic.aladdin.cs.cmu.edu/2005/07/15/pdfopen-and-pdfclose/)

If a document has been opened using pdfopen, AR crashes when the window is closed.
Dec 8 ' 06
1:33 PM Pacific


Reply 5 of 21

No solution here ... just confirming: the same situation using WinEdt and Reader 8.0. I'm going back to 7.0.8
Dec 9 ' 06
5:52 AM Pacific


Reply 6 of 21

I am also having the same problem using TeXnicCenter. However, the workaround Petra posted about opening a second document seems to work; annoying though.
Dec 9 ' 06
9:01 PM Pacific


Reply 7 of 21

I also use TexnicCenter and the reader crashes in the same manner. Actually, the reader crashes when I close the document manually. I will switch.
Dec 11 ' 06
3:00 AM Pacific


Reply 8 of 21

I'm noticing third party creation tools for all of these PDF files. Can someone post a PDF file so the group can look at it?

Sabian
Dec 11 ' 06
1:46 PM Pacific


Reply 9 of 21

Here is a sample pdf file I just created:

http://pages.cpsc.ucalgary.ca/~pneumann/test.pdf

Note, though, that the reader does not crash on file-close after I open the document by double-clicking on it in the file manager. It only crashes when I open it from my external program (TexnicCenter in this case) using DDE.

Petra
Dec 11 ' 06
2:05 PM Pacific


Reply 10 of 21

I've just tested this again with a few documents.

No matter what PDF file is opened (using DDE commands), it always crashes on close.
Dec 11 ' 06
2:08 PM Pacific


Reply 11 of 21

Hmmmm... I just used the Acrobat 8 SDK DDEOpenVC sample and that sample appears to be working with this file for me. If you compiled with VS2003 .NET have you tried recompiling your application with VS2005 .NET??

Sabian
Dec 11 ' 06
3:29 PM Pacific


Reply 12 of 21

I bumped into this problem while using these tools:
http://magic.aladdin.cs.cmu.edu/2005/07/15/pdfopen-and-pdfclose/

Open a file with the command
pdfopen --file somefile.pdf
and close the Reader window.

I did not try to compile these tools myself.
Dec 11 ' 06
3:40 PM Pacific


Reply 13 of 21

Sabian,

I've compiled my app with both VS 2003 and VS 2005 and it doesn't make any difference (nor would I expect it to).

I did look at the DdeOpenVC sample and tried to run it, but all it does is display a message box stating "No PDF Viewer installed. Aborting...". It uses FileOpenEx as the command string instead of DocOpen which is what IAC said back in version 5 when I first wrote this. I tried switching to FileOpenEx, but that just causes an immediate crash on opening.

Something is really broken with DDE support in Adobe Reader 8.

Erik
Dec 12 ' 06
12:59 PM Pacific


Reply 14 of 21

I am having the same issue. The DDE commands don't work in Adobe 8.0 reader or full product. Our product has 100's of thousands of users which rely on our interface with Adobe. You would think Adobe would take ownership of this issue.
Dec 15 ' 06
9:14 AM Pacific


Reply 15 of 21

Petra, when I open your file "test.pdf" on its own with the AR, I can close without any problems.

I'm using the TexnicCenter, too, and files compiled/opened with/through the TeXnicCenter will crash the AR when they are closed.
Jan 23 ' 07
1:34 PM Pacific


Reply 16 of 21

Hello All,

I have good news. This problem has been fixed in the beta of Acrobat Reader 8.1. I don't know when 8.1 will be released, but at least when it is this will no longer be an issue.

Erik
Mar 19 ' 07
12:45 PM Pacific


Reply 17 of 21

Hello all!

With our custom application programs (VB) we ran into a similar problem, which is probably related:

Using the Windows kernel ShellExecute function passing just the filename to open a file's parent application works with any program including Reader versions up to 7, but fails with Reader version 8. The AcroRd32 process starts and consumes 99% of CPU time, but never finishes.

Dietmar
Mar 20 ' 07
4:18 AM Pacific


Reply 18 of 21

Check the registry key:
 AcroExch.Document.7
     shell
       Open
         command
             Default key can be
                     "AcroRd32.exe" "%1"

After installation Acrobat Reader 8.0 we got
    "AcroRd32.exe" "%1"
  Change the file name to full path like
   "C:\Program Files\Adobe\Reader 8.0\Reader\AcroRd32.exe" "%1"

Iliya.
Apr 27 ' 07
12:33 AM Pacific


Reply 19 of 21

Thanks, Iliya!

The registry keys all show the full and correct path to AcroRd32.exe, and using task manager you can see that the exe is found and started, it never finishes, though. If you open the Reader in advance, you see that even the PDF file name is correctly interpreted as the window title changes accordingly. However, again, the window goes blank and the PDF is never shown.

Dietmar
Apr 27 ' 07
11:00 AM Pacific


Reply 20 of 21

This problem has been fixed in the beta of Acrobat Reader 8.1. I don't know when 8.1 will be released, but at least when it is this will no longer be an issue.


Is there any news about this? It is a shame that Adobe leaves a crasher bug unfixed for more than 6 months.
May 17 ' 07
11:55 PM Pacific


Reply 21 of 21

I found a workaround on the German Wikipedia site:

http://de.wikipedia.org/wiki/TeXnicCenter

The trick is, to put extra [DocOpen("%bm.pdf")] in front of each of the three DDE commands.

You can find some additional tips on the French Wiki site, making it possible to automatically open a document at the same position as it was when closed.

http://fr.wikipedia.org/wiki/TexnicCenter

Martin
May 26 ' 07
7:17 PM Pacific


View   60

Replies (indexing)
1 – 21 of 21 First | < Prev | Next > | Last


Sign in or create an account to reply.



Important Note: These online forums are for user-to-user discussions of Adobe products, and are not an official customer support channel for Adobe. If you require direct assistance, or prefer to contact Adobe support staff directly, please contact Adobe support.