Viewers for PDF, PS, and DVIAdobe Reader 10 and viewing error

Information and discussion about output viewers related to LaTeX (e.g. Adobe Reader, Ghostview, YAP, ...)
zgilboa
Posts: 1
Joined: Mon Feb 14, 2011 8:18 pm

Re: Adobe Reader 10 and viewing error

Post by zgilboa »

For the DDE request to work, settings need to be verified/updated in both Adobe Reader 10 and TeXnicCenter.

Adobe Reader 10:
--> Edit --> Preferences --> General --> UNCHECK the box "Enable Protected Mode at Startup"

TeXnicCenter:
--> Build --> Define Output Profiles --> Viewer (tab) --> the Server should be updated to AcroViewR10 (all three boxes)

Recommended reading 2024:

LaTeXguide.org • LaTeX-Cookbook.net • TikZ.org

NEW: TikZ book now 40% off at Amazon.com for a short time.

schanaka
Posts: 1
Joined: Wed Mar 02, 2011 6:04 am

Re: Adobe Reader 10 and viewing error

Post by schanaka »

Hi,

Guys, i think the solution provided in the Adobe forum as mentioned above works with DDE.

So use DDE and set the server in all 3 options to acroviewR10 instead of acroview
dskillz
Posts: 1
Joined: Tue Mar 29, 2011 2:55 am

Re: Adobe Reader 10 and viewing error

Post by dskillz »

What's up everyone.

If you upgrade Adobe Reader to version X from prior versions, Adobe has changed the name of the DDE server, thus causing TXC to crash when program calls are made to view your compiled PDF. To fix this, do the following:

1. Go to: Build -> Define Output Profile (Alt+F7).
2. For every profile you have that concludes with PDF viewing, click on its "viewer" tab.
3. Everywhere you see the server name "acroview", change it to "acroviewR10" (without the quotes of course)
4. Click ok

PDF viewing should work fine now. If you have the full version of Acrobat, use "acroviewA10" as the DDE server name.

Hope this helps!

-dB
0MerEdith
Posts: 1
Joined: Wed Apr 13, 2011 4:20 am

Re: Adobe Reader 10 and viewing error

Post by 0MerEdith »

No way. Nothing is working. Can't find my mistake.
I tried with Windows 7 32 and 64 bit.
I tried Adobe 9 and 10, Sumatra, changing registry file.
Just can't create pdf...
What am I missing?
Edith
impossible
Posts: 1
Joined: Fri Apr 15, 2011 6:29 pm

Re: Adobe Reader 10 and viewing error

Post by impossible »

Still having problems with configuring TexnicCenter (version RC1) with Adobe Reader X, actually I'm having problems with version 9.3 (haven't tried the others).
I have changed the DDE like it's written (for LaTex->PDF), changed the registry, minimized my document, in a short statement, everything that was mentioned in this thread. This is really annoying, everytime I want to work with Latex same problems appear every freakin time ([DocOpen("%bm.pdf")][FileOpen("%bm.pdf")] Cannot execute the command)...losing my patience, though I don't know is it the "complexity" of configuring TexnicCenter or is it something else (me being incapable of setting up). At the end I'll have to switch to my older PC, which has all these programs installed and it's working to a certain limit.

By the way I have Miktex 2.9 installed also.
Team3
Posts: 1
Joined: Fri Jan 21, 2011 9:20 pm

Adobe Reader 10 and viewing error

Post by Team3 »

zgilboa wrote:For the DDE request to work, settings need to be verified/updated in both Adobe Reader 10 and TeXnicCenter.

Adobe Reader 10:
--> Edit --> Preferences --> General --> UNCHECK the box "Enable Protected Mode at Startup"

TeXnicCenter:
--> Build --> Define Output Profiles --> Viewer (tab) --> the Server should be updated to AcroViewR10 (all three boxes)
This worked for me. In other words, the DDE server changes only worked once I disabled protected mode in Reader itself (Win 7 OS).
Arty
Posts: 1
Joined: Wed Jun 22, 2011 12:24 pm

Re: Adobe Reader 10 and viewing error

Post by Arty »

it stills not work for me :( the file cannot be found. Can someone please help me??

thx
Emo916math
Posts: 1
Joined: Tue Oct 18, 2011 4:55 pm

Re: Adobe Reader 10 and viewing error

Post by Emo916math »

zgilboa's fix worked for me. This ought to be on the TeXnicCenter help.

Those of you who claim that the PDF file cannot be found, can you clarify whether the file exists in the appropriate folder or not?
Azery
Posts: 1
Joined: Wed Nov 09, 2011 3:46 pm

Adobe Reader 10 and viewing error

Post by Azery »

Neverwinterx wrote:I've just installed the new Adobe Reader 10 (or Adobe Reader X as it is also called) and I'm trying to view a PDF file from within TexnicCenter. I've changed the path to the new AcroRd32.exe in "define output profiles" in the tab "viewer". When I click on "View Output" in TexnicCenter, Adobe Reader 10 opens but not the pdf file itself: it's just the standard opening screen of Adobe Reader 10. Also TexnicCenter itself stops responding for a while and then shows the "[DocOpen("%bm.pdf")][FileOpen("%bm.pdf")] Cannot execute the command." dialog. The other settings in "define output profiles" were left the same as before: DDE command, [DocOpen("%bm.pdf")][FileOpen("%bm.pdf")], server: acroview, topic: control. Manually opening the PDF file with Adobe Reader 10 goes fine of course.

I'm using Windows 7 (32 bit), TexnicCenter 1.0 stable RC1 and MiKTeX 2.9.
I had exactly the same situation and I did what was advised to this post and my problem was solved but the next time I restarted my Windows again I have problem viewing. This time the error message from TeXnic Center is "%bm.pdf Can not execute the command"

Would you please help me with that? Thanks
AzimAbdool
Posts: 1
Joined: Thu Nov 24, 2011 12:51 am

Re: Adobe Reader 10 and viewing error

Post by AzimAbdool »

Hi guys,

I have TeXnicCenter and after installing Adobe Reader X, I ran into this same problem. Found a workaround here: http://forums.adobe.com/message/3301219#3301219

The summary of the solution points are:

1. In TeXnicCenter go to Build -> Define Output Profiles (Viewer Tab)
2. Change the DDE servername to acroviewR10 (if you have the reader) or acroviewA10 (if you have the full Adobe)
3. Change the path of the executable to the AcroRd32.exe (the new one for the Reader X)
4. In Adobe Reader X, go to Edit -> Preferences -> General and uncheck "Enable Protected Mode at startup"

This solution worked for me.

-Azim.
Post Reply