Can't reenable "Acrobat PDFMaker Office COM Addin"

While PDFing a document from Microsoft Word 2007 (using Acrobat 9), the process froze so I killed the Word process.
Afterwards, I found that the Acrobat menu is now missing when I open a Word document.
In "Word Options", the Acrobat PDFMaker Office COM Addin is disabled. However, I've tried renabling it with no luck - it remains disabled.
I've tried also adding the COM to the registry, and running a repair, as described at this web page:
http://acrobat.timhuff.net/?p=29
Neither worked for me.
Does anyone have any other ideas before I have to reinstall Acrobat?
Thanks,
P.

Hi Alice,
Unfortunately that didn't fix it for me, but I finally found a solution courtesy of a comment by "Joel" at this blog - I've rewritten it slightly here:
http://acrobat.timhuff.net/?p=29#comment-8787
Open Word 2007.
Click on the Word icon. Go to the bottom of the window that is opened.
Click Word Options.
In the window opened, click “Add-ins”.
On the body of this window, choose the Adobe string that appear under “disabled application add-in”.
This is the crucial part: go to the bottom of this window, instead of "COM add-ins", Choose "Disabled Items". (This is where I was going wrong.)
Click Go.
In the Disabled Items dialog box displayed, select the Adobe addin and click Enable, then Close, then OK.
Regards,
P.

Similar Messages

  • Word experienced a serious problem with the 'acrobat pdfmaker office com addin' add-in. after Office Updates.

    I cant cant use mail merge feature in Winword in conjunction with Abobe Acrobat 10 (pdfmaker add-in) after the recent Office April Windows and Office Updates.
    Here is a quick note from the event viewer:
    The program WINWORD.EXE version 14.0.7134.5000 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. 
     Process ID: 1138 
     Start Time: 01d07dcede19c458 
     Termination Time: 15 
     Application Path: C:\Program (file:///C:/Program) Files (x86)\Microsoft Office\Office14\WINWORD.EXE 
     Report Id: 
    Microsoft Word: Accepted Safe Mode action : 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?.
    I do not wish to disable the pdfmaker add-in as I use it to run mail merge on WORD and send 10s and 1000s of pdfs via email to external users. I am not sure what are my options here and I wish
    someone could help me get to the root cause of the matter.
    My environment is as follows:
    Windows 7 x64 SP1
    Office 2010 v 14.0.7128.5000
    Adobe Reader MUI X and Adobe Acrobat X
    Feroze

    Hi,
    As the event log indicated, this is due to acrobat pdfmaker office com addin doesn't work well with Microsoft Word.
    I would suggest you go ahead and try to upgrade your Adobe product to the latest version and see if issue persists.
    Or contact the support of Adobe and see if there is a known compatibility issue or not.
    Regards,
    Ethan Hua
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Problem with Acrobat PDFMaker Office COM Addin

    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

    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.

  • Acrobat PDFMaker Office COM Addin for Microsoft Office 365 does not work. When I check the cox for COM Add-ins, it unchecks it. "A runtime error occurred during the loading of the COM Add-in." I use Adobe X Professional. The Add-in worked fine in Office 2

    I recently upgraded to Microsoft 365 Home and use Outlook 2013. The Acrobat PDFMaker Addin worked fine in Office 2010. Now, I get an error message: Not loaded. A runtime error occurred during the loading of the COM Add-in.
    I use Adobe Acrobat X Professional.
    I have restarted Outlook, restarted my computer, and nothing changes.
    Does anyone have a solution?
    Steve

    I do not think that AA X is compatible with the newest versions of OFFICE and such. Your only choice is to print to the Adobe PDF printer or use the MS plugins to create PDFs.

  • Log files when creating a pdf from PDFMaker Office COM addin

    Hello,
    I just bought Acrobat Standard to create pdfs on Word 2013.
    I'm making a catalog using this two softwares, Word 2013 (latest version with all updates) and Acrobat XI (latest version, 11.0.06). Unfortunately things are not working as I wish, and on some documents almost at the end of the transformation process, it can't save the pdf file or it gives a major word error, exiting word.
    When the transformation process is running/ending, are there any logs created to see what happens in case of errors?? If yes, where can I look up for them??

    Sorry, but when the pdf is created or not (like when happens on this particulary case), I don't see any logs on the same folder. 
    Let me try to explain my problem in depth.  I have a docx, a big file with 200 pages. It's created with Word 2013 but using the 2010 docx format for compatibility reasons. I beggun using the Word x64 but now I'm using the x86 and the problem happens on both and in the same ways. 
    First. If I try to convert the whole document, most of the times (I'd say 70%) the pdf doesn't get created or the rest of the times (30%) It causes a crash to Word with a dll error. Normally it halts (whether it doesn't create the pdf of halts word) at a certain page, after repaginanting all pages and when it says that is creating page nº X.
    I already pinpoint, more or less, where the error is. The error is located on the first pages, more exactly on the index pages. It's not a index created by the Word, it is a set of pages that I manually built with a grid of pictures with each one having a hyperlink to a designated bookmark to a desire page on the document. If I "pdfmaker" the rest of the whole document (without the index pages) I can get the pdf created.
    So, the index is where the problem resides. On this thread, http://forums.adobe.com/message/5816803#5816803 , you will see that I had a another problem due to the method used on Word 2003 about hyperlink of images that no longer works (when exporting to pdf) on the latests words versions, at least on the Word 2013. The pdf file was created with no problem, but on the pdf the hyperlinks were not created due to something that M$ has resolved to change between Word 2003 and Word 2007. I found a way to fix that (listed on that thread link). But as I like to invent, on the Field box, on the field options, for this time, I decided to choose the option "Data not stored with the document". That is what is breaking the pdf conversion. Too bad. Now I have to clear the index all the way and start again from the beggining but without that option. I already remake 3 pages and after the conversion the pdf is created. I have to finish the index redone once again and then create the full pdf document to see if any of those errors/halts happen again.
    I just wish to see a adobe log to see what type of error this bug produces so it would be possible to adobe crush the bug
    P.S. - Sorry if I was too confusiong for anyone to understand what I'm trying to say here
    Message was edited by: Onesolo

  • Acrobat X Pro - PDFMAKER Office COM  in Access 2010

    Hi,
    I have Office 2013 and Access 2010 installed on my computer. I cannot get the PDFMAKER plugin to work with Access 2010. I tried to manually register the DLL and enabling the plugin. Is this becuase I have MS Office 2013 installed alongside Access 2010. Any info would be great since we run reports in Access and need to ability to merge all the pages in the reports. This was working on another machine that only had office 2010.
    Nick

    Don't remember if it was AA X or AA XI when support for ACCESS ended. That may be the issue. The compatibility chart at Compatible web browsers and PDFMaker applications suggests that ACCESS does not work for OFFICE 2013 and PDF Maker, but does for ACCESS 2010 on AA X (only version of Acrobat that worked with ACCESS 2010. AA XI does not work with ACCESS. Since you mention both OFFICE 2013 and ACCESS 2010, there may be an issue with 2010 really being the application running (check the help file for About Access for the version). Of course, Acrobat may be confused too, so you may have to activate the addon for ACCESS 2010.

  • Cannot enable acrobat 8.1.3 addin in Word 2007

    Hi,
    I cannot enable acrobat 8.1.3 addin in Word 2007.  In Word 2007 I go to the top left circle, word options, Add-Ins, Disabled Application Add-ins,  Acrobat PDFMaker Office COM Addin, and then "Go".
    I then see Acrobat PDFMaker Office COM Addin is unchecked.  When I check it, it notes that "This add-in is installed for all users on this computer, and can only be connected or disconnected by an administrator".  See attached jpg for details.  Please advise.
    Thanks,
    Joe

    As the instructions indicate, log in as the administrator and activate the option. If you do not have access to the administrator account, then ask your IT folks to do it for you.

  • Can not finish acrobat x plugins install

    every time I open some office 2007 program or using right click menu on desktop acrobat x opens installing(configuring) window, after that everything works OK, but minute later I use right click or next time I open word or some other program everything starts all over. Reinstalling does not help, restarting does not help and so on....
    I have 32-bit win7 and office 2007
    as acrobat x opens normally it must be some plugins problem

    Hi,
    Please check if the plug-in has been installed in Office or not. Because if the status of the add in is set to Load at startup, the add in tries to configure for the first time and if proper permissions are not there, it fails to load and Office disables the add in.
    Try launching Office 2007 as Administrator, i.e. right click on Office icon and select 'Run as Administrator' and then check.
    Do also create a new user account and check the behavior.
    Also update Acrobat 10 to the latest version and check.
    Try repairing Acrobat by going to the help menu > Repair acrobat.
    In addition to the above you can check the following within the Office Application :
    Enable PDFMakerOfficeAddin from the Microsoft Office application's Disabled Items list.
    Open the Microsoft Office program (Word, Excel, Publisher, or PowerPoint).
    Click the Office button, then click the [application name] Options button.
    Click Add-Ins.
    From the Manage dropdown list select Disabled Items and click Go.
    Check the list for PDFMakerOfficeAddin:
    If it is listed, then select it and click Enable. Close all dialog boxes and restart the Office application
    If it is not listed, then make sure that PDFMOfficeAddin.dll is located in the '.../Program Files/Adobe/Acrobat 10.0/PDFMaker/Office' folder. If the file is missing, then reinstall Acrobat.
      Note: Microsoft Office Applications disable add-ins as a failsafe if the application is prematurely closed (for example, if the system wasn't shut off properly or the application crashed). 
    Add the COM add-in file to the Windows registry.
    In Windows Explorer, locate the COM add-in file (PDFMOfficeAddin.dll) and note the exact path, which may include spaces.
    Choose Start > Run.
    Type regsvr32 followed by a space, and then type the path that you noted in step 1, in quotation marks. For example: regsvr32 "C:\Program Files\Adobe\Acrobat 10.0\PDFMaker\Office\ PDFMOfficeAddin.dll "
    Click OK, and then start the Office application.
    Check if Acrobat PDFMaker Office COM Add-in is present in the list of available COM Add-ins for the Office Application. 
    Launch Microsoft Office program (Word, Excel, Access, or PowerPoint).
    Click the Office button and choose '[Application name] Options'.
    Click Add-Ins.
    From the Manage Dropdown list select COM Add-ins and click Go.
    Check the list for PDFMakerOfficeAddin and the checkbox in front of it is checked.
    If the checkbox is not checked then check it, click OK and restart the Office application.
    If the Office application doesn't allow you to check the checkbox and you have already tried Solution 1, then select Acrobat PDFMaker Office COM Add-in, click Remove and follw the next step.
    If Adobe PDFMaker COM Add-in is not present in the list of available add-ins, then click Add and navigate to C:\Program Files\Adobe\Acrobat 10.0\PDFMaker\Office\. Select PDFMOfficeAddin.dll, click OK, then restart the Office application.
    Regards,
    Ravi

  • Acrobat pdfmaker com addin for word 2010 crashes when processing large files

    I am trying to use the pdfmaker com addin for word 2010 to create a PDF document. Whenever I try and create the document, the acrobat addin crashes word.
    I attempted to perform this on both an x86 and x64 machine and it failed both times at around the approximately same point (during/immediately after determining the bookmarks).
    The document is large (862 pages, 2425 bookmarks, 311 300dpi graphics, for a total file size of 49.2MiB)
    I can generate the PDF by just printing, but the whole point of using the pdfmaker is so that we don't have to perform 2.5K of manual cross-links.
    Machine information:
    Windows 7 (x64) SP1
    Office 2010 (x64) 14.0.6112.5000
    Acrobat X Pro (x86) 10.1.3
    Crash Report:
    Version=1
    EventType=APPCRASH
    EventTime=129853934132967189
    ReportType=2
    Consent=1
    UploadTime=129853934134215189
    ReportIdentifier=4e4f5b16-c16a-11e1-ae3f-5c260a5c33cf
    IntegratorReportIdentifier=4e4f5b15-c16a-11e1-ae3f-5c260a5c33cf
    Response.BucketId=41559749
    Response.BucketTable=4
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=WINWORD.EXE
    Sig[1].Name=Application Version
    Sig[1].Value=14.0.6024.1000
    Sig[2].Name=Application Timestamp
    Sig[2].Value=4d83e2f6
    Sig[3].Name=Fault Module Name
    Sig[3].Value=wwlib.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=14.0.6024.1000
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4d83e39e
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=000000000031b4aa
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.256.48
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    UI[2]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
    UI[3]=Microsoft Word has stopped working
    UI[4]=Windows can check online for a solution to the problem and try to recover your information and restart the program.
    UI[5]=Check online for a solution and restart the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\kernel32.dll
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[5]=C:\Windows\system32\msvcrt.dll
    LoadedModule[6]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[7]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161 _none_08e61857a83bc251\MSVCR90.dll
    LoadedModule[9]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df _5.82.7601.17514_none_a4d6a923711520a9\Comctl32.dll
    LoadedModule[10]=C:\Windows\system32\GDI32.dll
    LoadedModule[11]=C:\Windows\system32\USER32.dll
    LoadedModule[12]=C:\Windows\system32\LPK.dll
    LoadedModule[13]=C:\Windows\system32\USP10.dll
    LoadedModule[14]=C:\Windows\system32\IMM32.DLL
    LoadedModule[15]=C:\Windows\system32\MSCTF.dll
    LoadedModule[16]=C:\Windows\system32\nvinitx.dll
    LoadedModule[17]=C:\Program Files\NVIDIA Corporation\CoProcManager\_etoured.dll
    LoadedModule[18]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvd3d9wrapx.dll
    LoadedModule[19]=C:\Windows\system32\SETUPAPI.dll
    LoadedModule[20]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[21]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[22]=C:\Windows\system32\ole32.dll
    LoadedModule[23]=C:\Windows\system32\DEVOBJ.dll
    LoadedModule[24]=C:\Program Files\NVIDIA Corporation\CoProcManager\nvdxgiwrapx.dll
    LoadedModule[25]=C:\Program Files\Microsoft Office\Office14\wwlib.dll
    LoadedModule[26]=C:\Program Files\Microsoft Office\Office14\gfx.dll
    LoadedModule[27]=C:\Windows\system32\WTSAPI32.dll
    LoadedModule[28]=C:\Windows\system32\MSIMG32.dll
    LoadedModule[29]=C:\Program Files\Microsoft Office\Office14\oart.dll
    LoadedModule[30]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
    LoadedModule[31]=C:\Windows\system32\msi.dll
    LoadedModule[32]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[33]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
    LoadedModule[34]=C:\Program Files\Common Files\Microsoft Shared\office14\Cultures\office.odf
    LoadedModule[35]=C:\Windows\system32\VERSION.DLL
    LoadedModule[36]=C:\Windows\system32\uxtheme.dll
    LoadedModule[37]=C:\Windows\system32\dwmapi.dll
    LoadedModule[38]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[39]=C:\Windows\system32\CLBCatQ.DLL
    LoadedModule[40]=C:\Program Files\Microsoft Office\Office14\1033\wwintl.dll
    LoadedModule[41]=C:\Program Files\Common Files\Microsoft Shared\office14\1033\MSOINTL.DLL
    LoadedModule[42]=C:\Program Files\Common Files\Microsoft Shared\office14\MSORES.DLL
    LoadedModule[43]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\MSPTLS.DLL
    LoadedModule[44]=C:\Program Files\Common Files\Microsoft Shared\office14\riched20.dll
    LoadedModule[45]=C:\Windows\system32\mscoree.dll
    LoadedModule[46]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[47]=C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPC.DLL
    LoadedModule[48]=C:\Windows\system32\Winspool.DRV
    LoadedModule[49]=C:\Windows\system32\SHELL32.DLL
    LoadedModule[50]=C:\Windows\system32\propsys.dll
    LoadedModule[51]=C:\Windows\system32\ntmarta.dll
    LoadedModule[52]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[53]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[54]=C:\Windows\system32\rsaenh.dll
    LoadedModule[55]=C:\Windows\system32\RpcRtRemote.dll
    LoadedModule[56]=C:\Windows\System32\msxml6.dll
    LoadedModule[57]=C:\Windows\system32\profapi.dll
    LoadedModule[58]=C:\Windows\system32\SXS.DLL
    LoadedModule[59]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorwks.dll
    LoadedModule[60]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_88e41e092fab0294\MSVCR80.dll
    LoadedModule[61]=C:\Windows\assembly\NativeImages_v2.0.50727_64\mscorlib\f73f0a9c9a83dcd3f f428be509a7992f\mscorlib.ni.dll
    LoadedModule[62]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorsec.dll
    LoadedModule[63]=C:\Windows\system32\WINTRUST.dll
    LoadedModule[64]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[65]=C:\Windows\system32\MSASN1.dll
    LoadedModule[66]=C:\Windows\system32\imagehlp.dll
    LoadedModule[67]=C:\Windows\system32\ncrypt.dll
    LoadedModule[68]=C:\Windows\system32\bcrypt.dll
    LoadedModule[69]=C:\Windows\system32\bcryptprimitives.dll
    LoadedModule[70]=C:\Windows\system32\USERENV.dll
    LoadedModule[71]=C:\Windows\system32\GPAPI.dll
    LoadedModule[72]=C:\Windows\system32\cryptnet.dll
    LoadedModule[73]=C:\Windows\system32\SensApi.dll
    LoadedModule[74]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Word.MathExtension.dll
    LoadedModule[75]=C:\Windows\assembly\GAC\Extensibility\7.0.3300.0__b03f5f7f11d50a3a\Extens ibility.dll
    LoadedModule[76]=C:\Windows\assembly\GAC_MSIL\office\14.0.0.0__71e9bce111e9429c\office.dll
    LoadedModule[77]=C:\Windows\Microsoft.NET\Framework64\v2.0.50727\mscorjit.dll
    LoadedModule[78]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\Microsoft.Education.Mathematics.Common.dll
    LoadedModule[79]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System\c40ec0f4cd203c88029 8f94c0427dd54\System.ni.dll
    LoadedModule[80]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Drawing\222eb8aa336 953a6b0216db2b0c4770d\System.Drawing.ni.dll
    LoadedModule[81]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Windows.Forms\dc5bb 74eefdbf954cdfb70dd534d5564\System.Windows.Forms.ni.dll
    LoadedModule[82]=C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Interop.Word\14.0.0.0__71e9 bce111e9429c\Microsoft.Office.Interop.Word.dll
    LoadedModule[83]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Configuration\193d0 3ca60573c92f92d9b07fa5bc243\System.Configuration.ni.dll
    LoadedModule[84]=C:\Windows\assembly\NativeImages_v2.0.50727_64\System.Xml\24d1b7ccbedaa36 02bae6a6acea9929e\System.Xml.ni.dll
    LoadedModule[85]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathControls.dll
    LoadedModule[86]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathEngine.dll
    LoadedModule[87]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\sqmapi.dll
    LoadedModule[88]=C:\Windows\system32\shfolder.dll
    LoadedModule[89]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\MathRichEditNative.Dll
    LoadedModule[90]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Shared\mathenginen.dll
    LoadedModule[91]=C:\Program Files\Microsoft Mathematics Add-in\2.0\Word\MathResources.dll
    LoadedModule[92]=c:\Program Files\Common Files\Microsoft Shared\VSTO\vstoee.dll
    LoadedModule[93]=C:\Windows\system32\urlmon.dll
    LoadedModule[94]=C:\Windows\system32\iertutil.dll
    LoadedModule[95]=C:\Windows\system32\WININET.dll
    LoadedModule[96]=C:\Windows\system32\Normaliz.dll
    LoadedModule[97]=c:\Program Files\Common Files\Microsoft Shared\VSTO\10.0\VSTOLoader.dll
    LoadedModule[98]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
    LoadedModule[99]=C:\Windows\system32\oledlg.dll
    LoadedModule[100]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[101]=C:\Windows\system32\MSVCR110_CLR0400.dll
    LoadedModule[102]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\ec4aeb1a93320223 07604cba8284778b\mscorlib.ni.dll
    LoadedModule[103]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\52974bd8d9753cf71a 27181621dcf4eb\System.ni.dll
    LoadedModule[104]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\a4252f50e54a5 d2987e41709da9a117a\System.Core.ni.dll
    LoadedModule[105]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V28a60cc2#\f165 482199ea49be235ec53ad93e6889\Microsoft.VisualStudio.Tools.Office.Runtime.ni.dll
    LoadedModule[106]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O5949707a#\6d99 2851fc846eac2e388d2348711376\Microsoft.Office.Tools.ni.dll
    LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V883708cb#\bc02 fe4c18b7e176e9bee4c72ff4cb32\Microsoft.VisualStudio.Tools.Applications.Runtime.ni.dll
    LoadedModule[108]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.V1955d7fd#\cc04 39da7e5347e89d6586ce262c1f69\Microsoft.VisualStudio.Tools.Applications.ServerDocument.ni.d ll
    LoadedModule[109]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Vf9a08577#\86f6 f20538156d2008fff97542e09765\Microsoft.VisualStudio.Tools.Applications.Hosting.ni.dll
    LoadedModule[110]=C:\Windows\system32\Secur32.dll
    LoadedModule[111]=C:\Windows\system32\SSPICLI.DLL
    LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1204d7ae7e 0e637669e244a02b97983b\System.Drawing.ni.dll
    LoadedModule[113]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\d7d8 56d242ddc80d696aa425195e5252\System.Windows.Forms.ni.dll
    LoadedModule[114]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\nlssorting.dll
    LoadedModule[115]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Deployment\475303e 370c565f47cd7d159485f24d9\System.Deployment.ni.dll
    LoadedModule[116]=C:\Windows\system32\dfshim.dll
    LoadedModule[117]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\0523 c17527d811bdc9606a0c62145f3d\System.Configuration.ni.dll
    LoadedModule[118]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\771d4e20776373 ee95d2058b4d3f20a8\System.Xml.ni.dll
    LoadedModule[119]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Security\819aca5f3 26d35ce5f478c20366d0f5c\System.Security.ni.dll
    LoadedModule[120]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml.Linq\76b84571f 4497227f40c72e246939ac0\System.Xml.Linq.ni.dll
    LoadedModule[121]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oab3f8ec6#\0a3a f5db2975c482e98e96c99bb938af\Microsoft.Office.Tools.Word.Implementation.ni.dll
    LoadedModule[122]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O4a946565#\a550 db8b700051717681470a0b2b07d3\Microsoft.Office.Tools.Common.Implementation.ni.dll
    LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O854200f9#\a3df 0bec1a202ce176b839f788d40f44\Microsoft.Office.Tools.Common.ni.dll
    LoadedModule[124]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.Oeab01fba#\9d47 6070258253869ff6ca2201f33b54\Microsoft.Office.Tools.Word.ni.dll
    LoadedModule[125]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.O2eb0cc9a#\3994 dd35eb969eb2221f1886598f08cc\Microsoft.Office.Tools.v4.0.Framework.ni.dll
    LoadedModule[126]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\2fd1 b7b3\d265be4b_e524cd01\PCREFindAddIn.DLL
    LoadedModule[127]=C:\Users\kking\AppData\Local\assembly\dl3\D5O6KVBP.4TZ\YDKV3YJ1.QPK\21e1 fe8e\00b3e430_67b7cb01\Microsoft.Office.Tools.Common.v4.0.Utilities.DLL
    LoadedModule[128]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[129]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMOfficeAddin.dll
    LoadedModule[130]=C:\Program Files (x86)\Microsoft Visual Studio 10.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
    LoadedModule[131]=C:\Windows\system32\MSVCR100.dll
    LoadedModule[132]=C:\Program Files (x86)\Microsoft Visual Studio 11.0\Visual Studio Tools for Office\x64\VSTOWordAdaptor.dll
    LoadedModule[133]=C:\Windows\system32\MSVCR110.dll
    LoadedModule[134]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\USP10.DLL
    LoadedModule[135]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\VBE7.DLL
    LoadedModule[136]=C:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA7\1033\VBE7INTL.DLL
    LoadedModule[137]=C:\Windows\assembly\NativeImages_v2.0.50727_64\stdole\be0906e176cf1f8ed8 1084df7042ee1c\stdole.ni.dll
    LoadedModule[138]=C:\Windows\system32\explorerframe.dll
    LoadedModule[139]=C:\Windows\system32\DUser.dll
    LoadedModule[140]=C:\Windows\system32\DUI70.dll
    LoadedModule[141]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7 601.17825_none_2b253c8271ec7765\GdiPlus.dll
    LoadedModule[142]=C:\Program Files\Microsoft Office\Office14\msproof7.dll
    LoadedModule[143]=C:\Program Files\Microsoft Office\Office14\MSOHEV.DLL
    LoadedModule[144]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\1033\MSGR3EN.DLL
    LoadedModule[145]=C:\Windows\system32\MPR.dll
    LoadedModule[146]=C:\Windows\System32\drprov.dll
    LoadedModule[147]=C:\Windows\System32\WINSTA.dll
    LoadedModule[148]=C:\Windows\System32\ntlanman.dll
    LoadedModule[149]=C:\Windows\System32\davclnt.dll
    LoadedModule[150]=C:\Windows\System32\DAVHLPR.dll
    LoadedModule[151]=C:\Windows\system32\wkscli.dll
    LoadedModule[152]=C:\Windows\system32\cscapi.dll
    LoadedModule[153]=C:\Windows\system32\netutils.dll
    LoadedModule[154]=C:\Windows\system32\SFC.DLL
    LoadedModule[155]=C:\Windows\system32\sfc_os.DLL
    LoadedModule[156]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Csi.dll
    LoadedModule[157]=C:\Windows\system32\WINHTTP.dll
    LoadedModule[158]=C:\Windows\system32\webio.dll
    LoadedModule[159]=C:\Windows\system32\PSAPI.DLL
    LoadedModule[160]=C:\Windows\system32\WS2_32.dll
    LoadedModule[161]=C:\Windows\system32\NSI.dll
    LoadedModule[162]=C:\Windows\System32\netprofm.dll
    LoadedModule[163]=C:\Windows\System32\nlaapi.dll
    LoadedModule[164]=C:\Windows\system32\srvcli.dll
    LoadedModule[165]=C:\Windows\System32\npmproxy.dll
    LoadedModule[166]=C:\Windows\system32\HLINK.DLL
    LoadedModule[167]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[168]=C:\Windows\system32\WINMM.dll
    LoadedModule[169]=C:\Program Files\Microsoft Office\OFFICE14\PROOF\MSSP7EN.DLL
    LoadedModule[170]=C:\Program Files\Microsoft Office\Office14\mscss7en.dll
    LoadedModule[171]=C:\Program Files\Microsoft Office\Office14\css7Data0009.dll
    LoadedModule[172]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMWord.dll
    LoadedModule[173]=C:\PROGRA~2\Adobe\ACROBA~1.0\PDFMaker\Common\X64\ADOBEP~1.DLL
    LoadedModule[174]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[175]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
    LoadedModule[176]=C:\Windows\system32\apphelp.dll
    LoadedModule[177]=C:\Windows\system32\NetworkExplorer.dll
    LoadedModule[178]=C:\Windows\system32\EhStorShell.dll
    LoadedModule[179]=C:\Program Files (x86)\Google\Drive\googledrivesync64.dll
    LoadedModule[180]=C:\PROGRA~1\MICROS~1\Office14\GROOVEEX.DLL
    LoadedModule[181]=C:\Windows\WinSxS\amd64_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.61 61_none_0a1fd3a3a768b895\ATL90.DLL
    LoadedModule[182]=C:\PROGRA~1\MICROS~1\Office14\1033\GrooveIntlResource.dll
    LoadedModule[183]=C:\Windows\System32\cscui.dll
    LoadedModule[184]=C:\Windows\System32\CSCDLL.dll
    LoadedModule[185]=C:\Windows\system32\ntshrui.dll
    LoadedModule[186]=C:\Windows\system32\slc.dll
    LoadedModule[187]=C:\Windows\System32\StructuredQuery.dll
    LoadedModule[188]=C:\Windows\system32\actxprxy.dll
    LoadedModule[189]=C:\Program Files\Internet Explorer\ieproxy.dll
    LoadedModule[190]=C:\Windows\system32\thumbcache.dll
    LoadedModule[191]=C:\Windows\system32\SHDOCVW.dll
    LoadedModule[192]=C:\Windows\system32\ieframe.DLL
    LoadedModule[193]=C:\Windows\system32\OLEACC.dll
    LoadedModule[194]=C:\Windows\system32\SearchFolder.dll
    LoadedModule[195]=C:\Windows\System32\cscobj.dll
    LoadedModule[196]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ACE.DLL
    LoadedModule[197]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AGM.DLL
    LoadedModule[198]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIB.DLL
    LoadedModule[199]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\BIBUtils.DLL
    LoadedModule[200]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\Cooltype.DLL
    LoadedModule[201]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\JP2KLib.DLL
    LoadedModule[202]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\ARE.DLL
    LoadedModule[203]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobePDFL.dll
    LoadedModule[204]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AdobeXMP.dll
    LoadedModule[205]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\AXE8SharedExpat.dll
    LoadedModule[206]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFMEngine.dll
    LoadedModule[207]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\pdfsettings.dll
    LoadedModule[208]=C:\Program Files (x86)\Adobe\Acrobat 10.0\Acrobat\x64\MPS.dll
    LoadedModule[209]=C:\Program Files (x86)\Adobe\Acrobat 10.0\PDFMaker\Office\x64\PDFPort.dll
    Sec[0].Key=LCID
    Sec[0].Value=1033
    Sec[1].Key=skulcid
    Sec[1].Value=1033
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    State[1].Key=DataRequest
    State[1].Value=Bucket=41559749/nBucketTable=4/nResponse=1/n
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Microsoft Word
    AppPath=C:\Program Files\Microsoft Office\Office14\WINWORD.EXE

    I recently ran into this with a bitmap in a 265 page document. I copied the bitmap to IrfanView and then back (I think that was the step -- I am already forgetting) and the copied it back. The problem went away. My student may look a bit more at the file -- I asked so I could give a more definitive comment here.
    The result I had suggests that it is a problem in WORD or the bitmap that WORD was using. Why WORD can deal with it and not Acrobat, I am not sure. However, when printing to the Adobe PDF printer there was not a problem, just with PDF Maker.

  • Acrobat PDFmaker 9 won't work with Office 2010

    Acrobat is Adobe's powerful and long-running pdf handler.  It's good software, but according to Adobe tech support in India, has known incompatibilities with Office 2010.  We can't create pdf files from any Office document or spreadsheet.  Adobe dropped the ball on this one, Office 2010 was out in beta for long enough for big developers like Adobe to get with the program.  Avoid Acrobat 9 until Adobe fixes it.

    I see a lot of people commenting that they had Adobe Acrobat 8.xx Pro and it worked fine with Microsoft Office 2010.
    That was not my experience.
    I downloaded MS Office 2010 and had the latest update of Adobe 8 Professional. (Don't know which release that was, but I keep my Adobe programs automatically updated.) As soon as I tried to use Adobe Acrobat to combine Excel files into a PDF, the PDFMaker functionality failed. This is why I purchased Adobe Acrobat 9, because my previous version did not work with MS Office 2010.
    It was incredibly infuriating to find out that upgrading did not resolve my problem, nor would going back to the previous install of Acrobat 8 Pro work for me. So, Adobe cheated me out of $160 for no reason, and after spending 6+ hours uninstalling, reinstalling and all kinds of other nonsense, I still can't use my PDFMaker plugin.
    The same thing happened with Adobe 8 and Microsoft Office 2007. The first version of Adobe 8 wasn't compatible, but then Adobe released a patch for Acrobat 8 that made it work with 2007. FOR FREE. I would say that we, the customers, have a reasonable expectation that the same should be done for Adobe 9, also at no extra charge.
    There is no way in hell that I'm buying Adobe Acrobat 10. Adobe has been incredibly dishonest about this problem and they're not getting one more red cent of my money. I'd rather scan my documents to PDF or use the Distiller.
    I'm quite sure I'm not alone in this sentiment, either.

  • Adobe Acrobat 11 Office Addin

    I have a recurring issue with Adobe Acrobat Pro 11.0 COM Addin causing Microsoft Word 2013 to Crash.
    I have tried to reboot
    I have tried to "repair" Acrobat Pro v 11.0
    I have uninstalled and re installed Acrobat Pro v 11.0
    I have re-imaged my PC and re installed freshly Adobe Acrobat Pro  v 11.0 and MS Office 2013
    None of the above solutions have worked. When converting a Word document to PDF using the Acrobat Ribbon It consistently causes MS Word to crash and when the restart of the application occurs the PDFMOfficeAddin.dll is disabled and even when I enable it the Acrobat Ribbon is not made available until a full PC reboot.
    I am running:
    Windows 7 Pro 64 Bit Version - Service Pack One
    MS Office 2013
    Adobe Acrobat 11.0 v 11.0.10

    [discussion moved to Creating, Editing & Exporting PDFs forum]

  • Acrobat Std/Pro 8 addin for Outlook causing causing corruption of email graphics & pollution of Outl

    Our IT Support team, in conjunction with Microsoft Premier Support, has been investigating reports of email messages not correctly displaying graphics. Microsoft Premier Support has identified the Adobe PDFmaker addin for Microsoft Outlook as the cause.
    When active, the Adobe PDFmaker addin stops Outlook from clearing it's temporary working folder, resulting in this folder becoming 'pollulted' over time, and ultimately affecting the ability of Outlook to use the temporary working folder for caching graphics received in emails.
    Please follow the below steps to replicate the issue.
    (Note: our testing has been performed with Adobe Acrobat Standard / Professional version 8.1.2 and Microsoft Office Outlook 2003 SP2 and SP3 running from Windows XP SP2)
    Steps to replicate
    ==================
    1. Ensure Adobe Acrobat Standard or Professional is installed to the machine
    2. Ensure Microsoft Outlook is closed
    3. Identify the location of your Outlook temporary working folder. This information can be obtained from the registry key: HKEY_CURENT_USER\Software\Microsoft\Office\11.0\Outlook\Security\OutlookSecureTempFolder
    4. Using Explorer, delete the contents of the Outlook temporary working folder (eg. C:\Documents and Settings\username\Local Settings\Temporary Internet Files\OLK91)
    5. Once the Outlook temporary working folder is empty, open Microsoft Outlook, and open an email message containing graphics
    6. Observe that the Outlook temporary working folder now contains the supporting JPG images that are loaded by the email :
    7. Close Microsoft Outlook
    8. Wait for 30 seconds, and re-open Microsoft Outlook
    9. Re-open the same email message containing embedded graphic images, confirm that the graphics are correctly displayed.
    10. Close the email, then close Microsoft Outlook
    11. Observe that the Outlook temporary working folder now contains a second copy of the supporting JPG images that are loaded by the email
    This is a bug. The expected behaviour of Microsoft Outlook would be that the above files should be automatically deleted from the Outlook temporary folder when the email is closed.
    With continued use the Outlook temporary folder will continue to grow as the user opens & closes emails with embedded graphics, as the files in this folder are not being automatically deleted when no longer accessed by Microsoft Outlook. Eventually this will affect the performance of Outlook and ultimately result in the graphic images not being displayed in any email messages.
    The Workaround
    ==============
    Microsoft have recommended the below registry entry be modified in order to rectify this issue:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Outlook\Addins\PDFMOutlook.PDFMOutlook\LoadBe havior
    The value of the LoadBehavior key needs to be changed from "3" to "2" to disable the Adobe PDFMaker addin from Microsoft Outlook.
    We have tested Microsoft's recommendation and confirmed that it resolves the above symptoms.

    William,
    Thanks for the report. May I ask that you file a bug report so that
    Adobe will be officially aware of the issue and fix. Maybe it will be
    fixed or the solution posted in the knowledgebase.
    Mike

  • I just downloaded Acrobat XI and the addin options is not showing up for Access 2010

    I just downloaded Acrobat XI and the addin options is not showing up for Access 2010

    Acrobat XI Pro/Standard doesn't support MS Access 2010:  http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html
    Third-party version/ Acrobat Version (ship  date)
    Acrobat 6
    (April 2003)
    Acrobat 7 (January 2005)
    Acrobat 8
    (November 2006)
    Acrobat 9 (July 2008)
    Acrobat X (November 2010)
    Acrobat XI (October 2012)
    MS Access
    Office 97
    x
    x
    x
    x
    x
    x
    Office 2000 (Office 9)
    N/A


    x
    x
    x
    Office XP (Office 2002/Office 10)
    N/A



    x
    x
    Office 2003 (Office 11) (11/17/03)
    N/A




    x
    Office 2007 (Office 12) (11/30/06)
    N/A
    N/A
    √ (8.1)


    x
    Office 2010 (Office 14) 32 bit
    x
    x
    x
    x

    x
    Office 2013 (Office 15) 32 bit
    x
    x
    x
    x
    x
    x

  • PDFMaker Office 2010 fails while creating the PDF

    I have a Window 7 laptopn with Office 2010 Adobe Acrobat 8.2.5. Slect create PDF button on tool bar and process starts but hangs while "onverting to PDF". Error occurs in MS Word, Excel & Powerpoint. System has worked fine up unitl a week ago. PDF creation in MS IE 8 have never worked but the Office suite ahs always worked.
    Tried rebooting, disbaling and reenabling the PDFMaker ADD-IN in office, downloaded alll the lated Adobe updates.
    Anyone any suggestions ?

    Hello there,
    I'm sorry you're having trouble. Unfortunately, this forum is exclusively for questions about Acrobat.com (www.acrobat.com); we're not able to help with questions about problems with other Adobe products and services. Here are some links that may be more helpful:
    Acrobat Help and Support:
    www.adobe.com/support/acrobat
    Acrobat Users' moderated forum:
    www.acrobatusers.com/forum
    I recommend posting this question to the Acrobat Users' forum, where there are many helpful and knowledgeable participants. I'm sorry not to have more specific advice for you! Best of luck.
    Kind regards,
    Rebecca

  • Acrobat PDFmaker is ignoring hard page breaks in Word docx

    I'm working with a client's Word docx file which is formatted almost entirely with tables and uses hard page breaks throughout. When the document is exported to a PDF using Acrobat PDFMaker, some of the hard page breaks are rendered but some of them are completely ignored. In those cases, section breaks, extra spaces and anything else is ignored, too. It simply runs the table and/or text together as if there was nothing between them. I'm totally baffled. I turned off all widow/orphan control and keep options.

    Glad you found a solution. I am not quite sure what you did or why what was suggested did not work. If you can ever post a document or part of such that demonstrates the problem and the inability of Acrobat to resolve it, I would be interested (a learning process!).
    In terms of WORD, I have seen many forms that folks create in WORD and have similar problems. In many cases they like to use as much of the page as possible. When I try to print the form on my printer, or even view it, it is generally messed up. This WORD form aspect is similar to the book issue you have mentioned. It is characteristic of the reflow of word processors based on the printer metrics.
    You might find this link (http://office.microsoft.com/en-us/word-help/preserve-original-appearance-for-viewing-or-pr inting-HP005189614.aspx) helpful in maintaining the layout. In OFFICE 2007 use of printer metrics was turned off by default in the Options>Advanced>Compatibility. I believe they turned it back in with later updates and versions. The article also mentions the issues with various fonts and the need to embed fonts. Unfortunately, the newer versions of WORD do not embed the fonts of vector graphics.

Maybe you are looking for

  • Error While Activating the Table

    i have created a table name ZEMPLOY11 in ABAP Dictionary containing fields Client [NUM] Carieer [NUM] Firstname [CHAR] and Surname [CHAR] and save it . when i activated this table it shows and error Mesage "Errors occurred during activation". kindly

  • How big an external monitor can i plug into the X60?

    I will be running Serato Scratch Live SL3 DJ software on my X60 and it would be nice to have a little extra sceen area for the display. How big of an external monitor can I plug into my X60? What can the built in graphics card handle? Thanks! (best n

  • I photo freeze,no key response,force shutdown,is there a fix?

    Just a few months now and freeze up is regular on slideshows,even edit saves are given trouble,don't wanna use the new 11 Iphoto,any help is welcome Thanks very much

  • Flash site issue

    I have a problem with a flash site I inherited. When I click the back button in Internet Explorer it takes me all the the way back to the Flash intro and not the last page I was in. This appears to be a site issue problem it is not IE related. Any he

  • BW Performance & troubleshooting role

    Dear SDN! I would like to know is it advisable for an rather inexperienced certified BW person to be deployed solo to a major customer who needs someone experienced to look into the cause of the BW performance and other problems experienced by users