Participating Frequently

解決済み

Problem with Acrobat PDFMaker Office COM Addin

Forum|Forum|15 years ago
November 12, 2010
返信数 8.
59325 ビュー

I have recently installed MS Office 2010 on my W7 system but find that the Acrobat addin for MS Word 2010 is not working -- it gives errors messages and recommends that I disable the addin.

This all used to work fine with MS Word 2007.

Is there anything that can be done about this problem. Is there an upgrade for the Acrobat PDFMaker Office COM Addin ?

Gerry

解決に役立った回答 Bernd Alheit

Upgrade to Acrobat X.

F

Federico34978617vpv6

Participant

I use PDFMaker office COM Add-in to print emails for keeping; but I noticed that on my Android phone in the files generated with the add-in there are no attachments (on the PC instead I see them); I already reported this problem some time ago but it doesn't seem to have been solved. Do you have any news?

T

Tariq Ahmad

Community Manager

Hi @Federico34978617vpv6,

Thank you for reaching out with your question and for the feedback.

I'm not sure how you're printing a PDF using the PDFMaker Office COM Add-in. If you mean converting a Word document to PDF, that's fine.

Again, I'm not sure what you mean by "Add-in" on Android; we don't have add-ins on Android. Please post your question here: https://adobe.ly/45m3tRI and kindly explain a bit more about your question for an Android device and how Adobe is involved.

Thank you for your patience and support.

~Tariq

A

Anonymous

I have Acrobat X and Word 2010. I seem to have lost my Acrobat tab. When I try to manage the addins the box for the Acrobat is not checked. I check it and hit okay and nothing. The loaded behavior is set to unloaded. Help.

V

Vishal@PDF

Adobe Employee

Hi,

To enable the Acrobat tab back, perform following steps in Word 2010:

1. Go to File --> Options --> Add-Ins

2. Click the drop down of "Manage" and select "Disabled Items"

3. Now click "Go"

4. Select "acrobat pdfmaker office com addin (pdfmofficeaddin.dll)" and click "Enable"

5. Close the "Disabled items" dialog.

6. Re-start the Word.

Acrobat Tab should be back now. Also see attached pdf for snapshots.

Mail.pdf

A

Anonymous

This is a Microsoft issue as well all over message boards, with 64-bit Office. This issue occurrs with many programs other than (and including) Acrobat. If you install Microsoft Office as 64-bit, many plug-ins do not work. Microsoft recommends you install Office as 32-bit, unless you are doing SERIOUSLY complex Excel work. See article:

http://technet.microsoft.com/en-us/library/ee681792.aspx

Further note, Acrobat X, Version 10.1 supports 64-bit Office, but not for Outlook:

http://blogs.adobe.com/pdfitmatters/2011/06/acrobat-x-version-10-1-adds-support-for-office-2010-64-bit.html

Finally, while Printing to the AdobePDF printer is an excellent option, please keep in mind that you will not get your bookmarks, hyperlinks or tags(accessibility for the visually impaired) in the resulting PDF. The point of File > Print to the AdobePDF Printer is to create PDFs from non-Adobe & non-Microsoft applications. PDFMaker out of Word does many wonderful things, like taking your Styles (Heading 1, Heading 2, etc.) and automatically bookmarking them. It also adds tags, so that the visually impaired can have a screen reading program read their content out loud. And it adds Hyperlinks (whether built in Word or Web links in the document). Standard web links will typically remain clickable in files created through File > Print, because Adobe Reader and Acrobat look for those.

I hope this info helps.

D

David J Wood

Participating Frequently

Kelly,

Whilst the main reason for 64 bit Office is large and complex Excel files, significant performance gains have been found in other usage scenarios, such as with lengthy and complex Word documents (especially when using complex plugins such as EndNote). It is in users' interests to use 64 bit Office if they can - but this is only possible if all their plug-ins support 64 bit Office.

I see Microsoft's document as a classic support driven response (or should I call it a cop-out) - there are compatibility issues with non-Microsoft software, so, to eliminate the support burden, we will steer you towards the lowest common denominator of installing 32 bit Office even if you have an x64 OS. Whilst this makes a great deal of sense, in that many users will see no advantage in 64 bit Office, there are plenty of users, including myself, who would see advantages from 64 bit Office but are being prevented from moving to 64 bit Office because third party plug-in providers have yet to make 64 bit versions available.

The situation with 64 bit Office plug-ins mirrors the situation with 64 bit Photoshop plug-ins, but with one key difference. Photoshop CS4, CS5 and CS5.1 (same as CS5; the apparent version bump indicates it was installed as part of Creative Suite 5.5) default to installing both 32 bit and 64 bit versions on x64 versions of Windows. You can therefore pick and choose which version of Photoshop you use according to which plug-ins you need. I'm now in the fortunate position of having 64 bit versions of all but two of the plug-ins I use regularly. I start the 32 bit version of Photoshop CS5.1 if I need those plug-ins, but my default is the 64 bit version.

Office 2010 requires you to choose between 32 bit and 64 bit; you cannot install both at the same time, and you cannot mix and match between different Office applications (so, for example, installing 64 bit Project 2010 alongside 32 bit Office Professional Plus 2010 is not supported and may cause problems - indeed, I'm not sure if the Project installer would allow you to install the 64 bit version if you had 32 bit Office applications already installed). This makes the unavailability of 64 bit versions of a single plugin that you require for one Office application a total bar to moving to 64 bit Office.

Unfortunately, this creates a 'chicken and egg' effect - the apparent demand for 64 bit versions of Office plugins is reduced because the unavailability of 64 bit versions of a crucial plugin prevents a move to 64 bit Office. I, for one, have a clear intention to switch to 64 bit Office, and will not buy new products or pay to upgrade existing ones unless they support 64 bit Office. Many products that can hardly be said to be aimed at the Office power user have supported 64 bit Office for some while, including Dragon NaturallySpeaking 11.5 and 11.0.

I wholeheartedly welcome the support for some 64 bit Office applications in Acrobat 10.1, but urge Adobe to provide complete support for 64 bit Office 2010. Currently, 64 bit versions of Visio 2010, Project 2010, Access 2010 and Publisher 2010 are not yet supported in PDFMaker. Hopefully this support will be forthcoming in a future quarterly update.

There is a mistake in your post - 64 bit Outlook 2010 is supported in Acrobat 10.1's PDFMaker. The issue with Outlook in the blog post you linked to is that Outlook 2010 doesn't have Microsoft's Save as PDF functionality - but if you have PDFMaker, using PDFMaker is the best option anyway.

CtDave

Participating Frequently

"I wholeheartedly welcome the support for some 64 bit Office applications in Acrobat 10.1, but urge Adobe to provide complete support for 64 bit Office 2010."

It'll take some time. The turn around (10.1.0) for the core Office 2010 applications seemed fairly brisk.

Sorry for the transcription error - Correct, only 32-bit support for Access, Project, Visio, & Publisher.

Maybe it'll all align with Acrobat XI (or will it be "11" ).

Be well...

CtDave

Participating Frequently

fwiw —

Acrobat X (3.1.0) PDFMaker provides:

See: http://kb2.adobe.com/cps/333/333504.html

Be well...

D

David J Wood

Participating Frequently

I'd missed the Office 2010 (64 bit) PDFMaker support in Acrobat 10.1. It's a great start - but only partial, in that it doesn't cover Publisher, Access, Visio or Project. I don't really care about Publisher (I am an InDesign CS 5.5 user and only use Publisher when someone sends me a Publisher file), but I do use Access, Project and especially Visio.

The day when I can switch to 64 bit Office is getting closer. Around half my Office plugins now support 64 bit Office. I look forward to the day when Acrobat has full support for 64 bit Office and I can retire my Windows Mobile 6.x phones (as Microsoft will not be upgrading the synchronisation software for this now orphan platform to support 64 bit Office) as that will put me very close to being able to switch.

The big shame in Acrobat 10.1 was supporting Firefox 4 days before Firefox 5 was released. As Firefox 5 is partly a security upgrade, sticking with Firefox 4.0.1 is not really an option. Hopefully Adobe will catch up with the new rapid release schedule Mozilla have adopted - there will be far fewer point releases and much less change between 'major' versions.

B

BreakfastInAmerica

Participant

I am having the same issue - is there a solution available?

Tech support in my organization are suggesting that I use a competing acrobat product to get the job done (c'mon Adobe!).

Here are my details...

DESCRIPTION

=======================

In Word 2010, I'm trying to create a PDF by using the PDFMaker Office Com add-in. The program always crashes after freezing for a couple of minutes. A PDF is never generated.

My machine is fully patched and up-to-date with all patches from Microsoft, as of date of this post.

ERROR MESSAGE TEXT

=======================

Word experienced a serious problem with the'acrobat pdfmaker office com addin' add-in. IF you have seen this message multiple times, you should disable this add-in and check to see if an update is available. Do you want to disable this add-in?

Yes | No

TECH DETAILS

=======================

OS - Windows 7 (x64)

Adobe Acrobat - Version 9.4 Professional

Microsoft Word - Version 2010 (32bit)

Problem signature:

Problem Event Name: APPCRASH

Application Name: WINWORD.EXE

Application Version: 14.0.6024.1000

Application Timestamp: 4d83e310

Fault Module Name: PDFMOfficeAddin.dll

Fault Module Version: 9.1.0.0

Fault Module Timestamp: 49a84ec8

Exception Code: c0000005

Exception Offset: 0000b697

OS Version: 6.1.7601.2.1.0.256.4

Locale ID: 4105

B

Bill12

Inspiring

AA9 does not work with WORD 2010. How you got the PDF Maker menu is a question, it should not be there. With OFFICE 2010 and AA9, your only choice is to print to the Adobe PDF printer. The other alternative is to upgrade to AAX. Also, be sure to update AA9 which is currently at AA9.4.5. Some folks have had problems with 9.4.5 and you might want to stop at 9.4.4 in that case. Others say to use a 3rd party PDF producer, but keep in mind that most will do no more than printing to the Adobe PDF printer. So the fact that PDF Maker does not work is not a reason to go to a 3rd party as such.

B

BreakfastInAmerica

Participant

To Bill@VT

Can you help me understand why you're suggesting I upgrade to AAX, when other posters in this thread continue to experience issues after upgrading to AAX.

I'm looking for Adobe to provide a definitive solution to successfully resolve the issue in a series of clearly outlined steps (with or without a patch). It doesn't help Adobe improve their customer service / product / reputation by downloading/installing a 3rd party tool that will, at most, duplicate functionality I already have.

I appreciate the time it took to post your reply, but to be frank, you're answer doesn't provide what is required, or inspire confidence (e.g. "Some folks..." and "Others say to use..." etc.).

D

ditchyglen3

Participant

I just purcahsed acrobat X online, and it errors everytime i try to convert a word 2010 .doc larger than about 10Mb. Then it tries to disable the add-on. This problem doesn't happen with Windows XP running word 2007. Any suggestions? Seems like a wasted purcahse.

B

Bill12

Inspiring

Try turning off some of the options in the PDF Maker preferences, particularly tags, and see if you are able to get the desired results.

D

ditchyglen3

Participant

thanks. tried this, and no difference. any other ideas? seems like a known problem between office 2010 word and acrobat, (several versions) clearly including X and some prior. have tried several different documents, all over 10Mb and they each cause the program to crash.