Contribute plugins crash Word 2007

Cursor movement within the edit space of Word 2007 (and a few
other places in Word, like the Word options dialog box) stopped
after installing Adobe CS3. I traced the problem to
Adobe Contribute CS3's OfficePlugIn.dll. I disabled it for
Word. This required a registry edit. Cursor movement for Word
returned, but Word still always exited with a crash (ugly!). I then
tried to remove another suspected culprit,
ContributeWordUITemplate.dot., using Word's Templates and
Add-Ins dialog box. Attempts to OK my choice immediately end in a
crash.
Does anyone know of a solution to this behavior by
Contribute? It resembles the behavior of malicious code: wreck the
program and block options to fix it.

Michael,
I tried printing to a PDF file and for the first time I get an error
listing:
%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[Page: 2]%%
%%[Page: 3]%%
Cambria not found, using Courier.
%%[ Error: invalidfont; OffendingCommand: xshow ]%%
Stack:
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
I did not select this font, MS Word did when I created a few formulas. The
font is in the Windows Font folder. Selecting it and trying to change the
font just causes it to either not change or change back to Cambria Math
after a few seconds.
It prints fine on the printer, and HP LaserJet.
Dan

Similar Messages

Cannot install xmlp plugin for word 2007 on Windows 7 64bit

I cannot install xmlp plugin for word 2007 on Windows 7 64bit. I keep getting a "java runtime not installed" error. I have applied the latest updates to word. Is there a fix to this?

Hi,
Even if you use a 64bit OS, the office version could be either 32bit or 64bit. Which one do you use? If already installed a 64bit version Office, try to switch to a 32bit one, because it will work fine and might solve your problem too.
*[url http://www.java-forums.org/blogs/advanced-java/collection/]Java collection*

PDF Creator Plugin crashs Word.

I have not seen the actual event, but the user after using the create PDF on the
Acrobat ribbon tab Word will crash. At this point Word can never be open again unless you run repair. The user can print to the Adobe PDF, but is alot more work. How do we stop the PDF Creator to stop crashing Word?
Windows XP SP 3 all patchs
Office 2007 SP2 all patchs
Acrobat Pro 9.3.2 all patchs
This is a clean install of Acrobat, as I had to remove version 8 because it kept breaking on more than one computer. (Long story, it would update then would never really be updated or think its not or cause other issues.)
I did install Reader 9.3.2 and BullPDF printer at first as a free alternative, but boss liked the functionability of the full Acrobate so I removed BullPDF and forgot reader was on there and Acrobat never removed it. I did remove it just before removing the plugin but I can't see that being the culprit.
Thank you for your time,
Eric Vogel

Nobody can tell you anything without proper system info or other technical details like what version of the Office products. Either way, ask in the Acrobat forum.
Mylenium

Word 2007 crashes when sving a document

Hey guys,
I have a user that is using Word 2007 on Windows XP sp3. When she tries to save a word document, Word crashes on her. It appears to do this randomly and there is nothing I can see that would trigger it. She can edit a document, save it
(using either quick save, or file, save) and it will crash on her. She's noticed more of a issue when she uses the quick save button. I have uninstalled Office twice. Once doing an uninstall/reinstall and the other doing an uninstall, delete the
directory and reinstalling word. The only add-on she has is Dorland's 28th edition dictionary. I have uninstalled/reinstalled this and the issue still seems to come up. I have gone through the registry and deleted any instance of Dorland's
I found. I did notice in the add/remove programs that there was a Dorland's lsited there, but could not be uninstalled. I am betting that could be the culprit. Anyone have any ideas?
Thanks,
David

See the KnowledgeBase article "How to troubleshoot problems that occur when you start or use Word 2010, Word 2007, Word 2003, or Word 2002" at:
http://support.microsoft.com/default.aspx/kb/921541?p=1
-- Hope this helps.
Doug Robbins - Word MVP,
dkr[atsymbol]mvps[dot]org
Posted via the Community Bridge
"whitehurstge" wrote in message news:[email protected]...
Hey guys,
I have a user that is using Word 2007 on Windows XP sp3. When she tries to save a word document, Word crashes on her. It appears to do this randomly and there is nothing I can see that would trigger it. She can edit a document, save it
(using either quick save, or file, save) and it will crash on her. She's noticed more of a issue when she uses the quick save button. I have uninstalled Office twice. Once doing an uninstall/reinstall and the other doing an uninstall, delete the
directory and reinstalling word. The only add-on she has is Dorland's 28th edition dictionary. I have uninstalled/reinstalled this and the issue still seems to come up. I have gone through the registry and deleted any instance of Dorland's
I found. I did notice in the add/remove programs that there was a Dorland's lsited there, but could not be uninstalled. I am betting that could be the culprit. Anyone have any ideas?
Thanks,
David
Doug Robbins - Word MVP dkr[atsymbol]mvps[dot]org

Word 2007 crashes during autosave and when saving as .DOC

Hi,
I have a problem with Microsoft Word 2007. It crashes every time during autosave. It also crashes when I try to save a file as .DOC (even an empty new file). When I save it as any other file type it's fine.
I have already tried repairing the office installation, reinstalling the whole suite (and then installing SP3 and all latest patches again), auto fix it from
http://support.microsoft.com/kb/822005/en-us and
http://support.microsoft.com/kb/921541/en-us, changing the autosave file location, using different windows account. None of these helped. I wouldn't like to work with autosave switched off.
I am using Windows 7 Professional SP1 and Office 2007 Professional 12.0.6683.5002 with SP3 on HP EliteBook 8470w.
-- Igor M.

Hi,
I tried to start Word in safe mode be it did not change anything. I also tried to start Windows 7 in clean boot but it did not help either (same issues).
Two entries are added to the event log when Word crashes:
First one:
ID: 0, Application Name: Microsoft Office Word, Application Version: 12.0.6683.5002, Microsoft Office Version: 12.0.6612.1000. This session lasted 94 seconds with 0 seconds of active time. This session ended with a crash.
Second one (Google translation):
Log Name : Application
Source: Application Error
Date: 2013-12-29 0:38:43
Event ID : 1000
Task Category : (100)
Level: Errors
Keywords: Classic
User : Not applicable
Computer: XXX
Description:
Name of the application causing the error: WINWORD.EXE , version : 12.0.6683.5002 , time stamp : 0x520bb457
Name of the module causing the error : wwlib.dll , version : 12.0.6683.5002 , time stamp : 0x520bb54c
Exception code : 0xc0000005
Fault offset : 0x0006d564
The process ID causing the error : 0xbb0
Time to run the application causing the error: 0x01cf0425b9f67b73
The application path causing the error: C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ WINWORD.EXE
The path of the module causing the error : C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll
Report ID : 2fcdf5c7 - 7019 - 11e3 - 96f9 - 1c3e84fe29b2
Event Xml :
  "><Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    "><Provider Name="Application Error" />
    1000</EventID>"><EventID Qualifiers="0"> 1000 < / EventID >
    100</Task>"><Task> 100 < / Task >
    "><TimeCreated SystemTime="2013-12-28T23:38:43.000000000Z" />
    Application</Channel>"><channel> Application < / Channel >
    "><Security />
  "><EventData>
    12.0.6683.5002</Data>"><Data> 12.0.6683.5002 < / Data>
    wwlib.dll</Data>"><Data> Wwlib.dll < / date >
    520bb54c</Data>"><Data> 520bb54c < / date >
    0006d564</Data>"><Data> 0006d564 < / Data>
    01cf0425b9f67b73</Data>"><Data> 01cf0425b9f67b73 < / date >
    C:\Program
Files (x86)\Microsoft Office\Office12\wwlib.dll</Data>"><Date> C : \ Program Files (x86 ) \ Microsoft Office \ Office12 \ wwlib.dll < / date >
  ">< / EventData >
<span title="">< / Event >
Kind regards,

Word 2007 Crashes

Every time I open Word 2007 it crashes. It also crashes while working in a document. Any help you can provider would be greatly appreciated. It is getting very frustrating. The following is the error message pops up:
Word has stopped working .....
Here are the crash details:
Problem signature:
Problem Event Name: APPCRASH
Application Name: WINWORD.EXE
Application Version: 12.0.6690.5000
Application Timestamp: 52881869
Fault Module Name: gdiplus.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 515ba857
Exception Code: c0000005
Exception Offset: 737e74b2
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Additional information about the problem:
LCID: 1033
Brand: Office12Crash
skulcid: 1033
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Hi,
You can also try starting Word in Safe Mode:
Press Win + R and type “Winword.exe /safe” in the blank box, then press Enter.
If there’s no problem in Safe Mode, disable the suspicious add-ins to verify which add-ins caused this issue.
In addition, I have seen such Word crash issues caused by conflicted programs, you can perform a clean boot to determine if background programs are interfering with Word:
http://support.microsoft.com/kb/929135
I hope this helps.
Regards,
Melon Chen
TechNet Community Support

Word 2007 Acrobat X Pro Plugin adds garbage to PDF Headers

I'm generating PDFs from Word 2007 using the Acrobat X Pro plugin, which is inserting garbage into some of my headers during the process. I can actually see it happen during PDF generation. The Word headers and footers are enabled and the garbage suddenly appears. For some reason, its usually an 0B prefix attached to the headers.
It doesn't happen to all headers and not with any pattern or consistency.
Any ideas?

Thanks, Steve. It's just aggravating that I have to go through an extra set of steps to do this on a Mac.
I appreciate the help!
jtlynn23

Acrobat X 10.02 crashes when converting Word 2007 document wiht linked Visio file.

Acrobat X 10.02 crashes when converting Word 2007 document with linked Visio file and causes a C++ runtime error in Word and crashes Word.
To see the behavior create a short Word 2007 document with a linked Visio file (e.g., create a Visio file with one box and text and insert it as a link into a Word docx).
No problem in Acrobat 9

There may be some of an issue with AA X on this, but part of the blame probably goes to MS also. I would suggest you simply clip the graphic from VISIO as a vector graphic (EMF will be used by default) and not do the link and do not embed the VISIO object. The linking and use of embedded objects in WORD 2007 seems to have been a major problem and is mostly a MS issue.

WORD 2010 Crashes Opening Word 2007 files

WORD 2010 crashes when opening Word 2007 files. If you save the files in Office 2007 as an RTF file, then open in WORD 2010 and save as a DOCX it works fine. Why can't WORD open legacy documents (these are not big files ~13 pages).
I have tried opening in safe mode, same effect - the doc opens and appears in the WORD window, and then the pop-up appears before you can do anything telling you that WORD 2010 has crashed.

Try using Open and Repair on the problem docs.
In the Open dialog, select the file, then click the arrow beside Open and choose Open and Repair
If that doesnt help you may want to check the How to troubleshoot damaged documents in Word 2007 and in Word 2010
http://support.microsoft.com/kb/918429
Regards, ~G MCSE, MCDST, MCITP, MCTS, MCP, CCNA

Help me stop Word 2007 from crashing with PDFMaker!

I'm running Word 2007 (along with other Office 2007 applications) on a Windows 7, 64-bit computer that I recently migrated to. Every single time I try to create a pdf of a Word .doc or .docx file, the pdf is created OK but Word crashes. This is a huge nuisance, as I'd like to be able to keep other Word files open as I pdf the one I'm working on. I'm up-to-date with the Acrobat version (9.5.1); it's Acrobat Pro. Plenty of room on the hard drive (500 GB, of which 333 GB is free) and plenty of memory (8GB).
Note I'm able to create pdfs in PowerPoint and Excel without problems using the Acrobat add-in. I'm also able to create a pdf from a file shown in Windows Explorer by highlighting the file and using the right-click button to choose "Create PDF."
Any ideas?

I belive this is because technically Adobe is not supporting Windows 64 bit, so all the features we enjoyed in, say Windows XP, are not supported now. This is an ongoing battle with Adobe who apparently has 0 interest or intent in supporting 64 bit. They SAY they support it, but they only mean you can save to PDF. None of the features like hyperlinks, PDF Maker, TOC, shared reviews, etc. are supported. I think they are literally the only company not supporting 64 bit and their only workaround is to now use 64 bit. (Can you tell I am annoyed - I am. It's been over a year battling them and 0 action on their part.)

Word 2007 Acrobat 9 CRASHES

Large document in DOCX format, 490 pages, starts to convert, then after three progress bars, Word goes to a solid 50% of CPU and everything stops.
I did not pay $300 to have this happen with the first stinking document I am working on.
System INFO:
Available Physical Memory: 2097151 KB
Available Virtual Memory: 2005708 KB
BIOS Version: IntelR - 42302e31
Default Browser:
Default Mail: Microsoft Office Outlook
mapi32.dll
Version: 1.0.2536.0 (XPClient.010817-1148)
Graphics Card: NVIDIA GeForce 8800 GT
Version: 6.14.11.7116
Check: OK
Installed Acrobat: H:\Program Files\Adobe\Acrobat 9.0\Acrobat\Acrobat.exe
Version: 9.0.0.2008061200
Creation Date: 2008/06/12
Creation Time: 2:25:18 AM
Locale: English (United States)
Monitor:
Name: NVIDIA GeForce 8800 GT
Resolution: 1280 x 1024 x 60
Bits per pixel: 32
OS Manufacturer: Microsoft Corporation
OS Name: Microsoft Windows XP Professional
OS Version: 5.1.2600 Service Pack 3
Page File Space: 4194303 KB
Processor: x86 Family 6 Model 23 Stepping 6 GenuineIntel ~3060 Mhz
System Name: FIRE
Temporary Directory: H:\DOCUME~1\SLASHS~1\LOCALS~1\Temp\
Time Zone: Eastern Standard Time
Total Physical Memory: 2097151 KB
Total Virtual Memory: 2097024 KB
User Name: slashsplat
Windows Directory: H:\WINDOWS
Installed plug-ins:
H:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins\Annots.api
Version: 9.0.0.2008061200
Creation Date: 2008/06/12
Creation Time: 1:59:50 AM
H:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins\EScript.api
Version: 9.0.0.2008061200
Creation Date: 2008/06/12
Creation Time: 2:05:18 AM
H:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins\SendMail.api
Version: 9.0.0.2008061200
Creation Date: 2008/06/12
Creation Time: 2:17:10 AM
H:\Program Files\Adobe\Acrobat 9.0\Acrobat\plug_ins\Updater.api
Version: 9.0.0.2008061200
Creation Date: 2008/06/12
Creation Time: 2:00:30 AM

Footnotes in tables were the problem with my doc as well. I tried the option of saving the doc as a Word 2003 file, but it didn't help. I chatted with Adobe Customer Service and was provided this fix:
In Word 2007, click on the Acrobat ribbon
In the "Create Adobe PDF" panel, click on "Preferences"
In the "Settings" tab, under "Application Settings," UNCHECK the box next to "Enable Accessibility and Reflow with tagged Adobe PDF"
After that, I was able to create the PDF, and the table of contents and external hyperlinks all worked. The footnotes were no longer hyperlinked, but since they're on the same page as the items they're referencing, that's not really a problem. Cheers,
JG

AA mailmerge in Word 2007 (Office SP3) crashes. Windows 8.

Have just installed AA 11.0.07
Every time I try to do a mailmerge:
1. A File save as box opens up. I don't know why. Nevertheless have tried saving as either .doc or .pdf
2. Word then crashes

Footnotes in tables were the problem with my doc as well. I tried the option of saving the doc as a Word 2003 file, but it didn't help. I chatted with Adobe Customer Service and was provided this fix:
In Word 2007, click on the Acrobat ribbon
In the "Create Adobe PDF" panel, click on "Preferences"
In the "Settings" tab, under "Application Settings," UNCHECK the box next to "Enable Accessibility and Reflow with tagged Adobe PDF"
After that, I was able to create the PDF, and the table of contents and external hyperlinks all worked. The footnotes were no longer hyperlinked, but since they're on the same page as the items they're referencing, that's not really a problem. Cheers,
JG

Bug? Accessibility Tags Converting from Word 2007

This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
I'm using Acrobat 9 Pro.
Thanks,
Joe

Hi Joe,
I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
The is no "work smarter with less & pump out more" in this venue.
Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
contribute to major conceptual errors vis-a-vis accessible PDF.
Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Additional, useful information is found in these two documents:
(1) - PDF Accessibility API Reference (from the Acrobat SDK)
https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
(2) - Reading PDF Files Through MSAA
https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
About JAWS - Yes, much used. However, not the exlusively used AT application.
If I use Windows Eyes, NVDA, a braille reader, or something else then what?
JAWS *does not* define "it is accessible"...
re: (1)
"Game away and if it ...."
   Consider "Stop before right on red".
   "Compliance" is Stop on Red - Turn Right
   "Intent" (aka usability) is Stop on Red - Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
But, at least we are not talking about "left on red" 8^)
re: (2)
Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
Quantity replacing Quality just is not a success precursor.
Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
Resolved now - see NFB's web site.
re: (3)
Ah, but what would Judge Judy or Judge Marily say?
Efficiency does not preclude providing a "whole" product.
I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
For PDF there is no other way.
If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
However, HTML, done "right" for accessiblilty is just as demanding in its own way.
With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
Creation of all this must start in the authoring environment with the content author.
The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
Without this, AT will not be able to provide the end-user effect utilization of the PDF.
So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
Consider Target and the situation they put themselves in.
Consider submittal of accessible PDF to fedgov or stategov agencies.
They won't be in front of the fan if usability of the PDFs becomes an issue.
Rather, it will be those submitting. After all the agency did say "accessible".
Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
In the final analysis, for PDF, HTML, or any 'format', Accessibility is the Usability + Compliance.
Does it take improvements in professional development/training, adequate hardware/software, *time*?
Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
It can be done. I do it one small step at a time every day. Often, that's what it takes.
Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
the "road" is completed properly.
Don't want wash outs, bridge collapse or what not tomorrow <g>.
(But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
re: function(){Return ....
Good question.
My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
fwiw -
You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
Two Accessible PDF related on demand eSeminars are also available.
Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
http://www.acrobatusers.com/learning_center/eseminars_on_demand
Be well...

Word 2007 - Save as Pdf gives error - This file is in use by another application or user

I have MS Office 2007 Small Business.
For months I have been using the "Save as PDF/XPS" option to save my word documents as PDF files.
All of a sudden, when I click on the publish button within the "save as PDF dialog", I get the error:
"This file is in use by another application or user."
- I have tried creating a new word document and I still get this error when I try to save-as pdf.
- I have tried opening a document that previously was able to be saved-as-a-pdf, and it no longer works either.
- I have tried saving from other office applications (excel, powerpoint) that also get errors now.
I have not personally installed any new software that I recall between when this worked and stopped working for me.
As far as I can tell there have been no updates explicitly for save-as-pdf in office.
Is anyone else seeing this problem all-of-a-sudden?
Thanks.
jlk

I just encountered this problem while trying to save a pdf from Excel 2007. I had recently updated to Adobe Reader 9.1.
I received the same error message you're reporting here when I went to Word 2007 and tried to save a pdf file from it as well.
I uninstalled Adobe Reader 9.1.
Reinstalled the Office 2007 pdf plug-in
Successfully created pdf files from word and from Excel (which is what I needed to do in the first place).
I then reinstalled Adobe Reader 9.1 so I could read the PDF files I had just created in Excel and word.
I then tried to create pdf files from word and excel. Error messages are back and I'm unable to create pdf's from word or excel.
So.. why does Office 2007 pdf plugin not work when Adobe Reader 9.1 is installed?
Frankly I'm getting tired of uninstalling Adobe Reader 9.1 every time I need to create a pdf file in Word or Excel.
Bry

Converted MS Word 2007 to Adobe Acrobat 9 random "Bad Parameter" Error

Question: I Converted MS Word 2007 file which contained 892 pages into Adobe Acrobat 9 Standard afterwards and while needing to update only certain pages I receive the "Bad Parameter" Error. My process is using drop down Document/Extract pages(make my updates)/Replace pages into complete PDF file/ usually with no problem then towards the last pages of the PDF the Error showed up! I believe that it’s possible, the conversion initially may have allowed many tags to be written correctly but some are corrupted. It could be a buffer-overflow failsafe that is having an adverse effect against the two programs because of the file’s size? I have seen some good advice come from many people on this site like "Bill@VT" and "CtDave" and others so I am humbly requesting assistance? Some additional background information is I have to keep the file size the same and I cannot print to PDF file from Word due to a specific format I must keep and most of the PDF is not corrupt: meaning receiving the "Error". I would like to know if the error that seems to be due to the conversion process can be corrected. I have provided some additional similar post below from other customers that may be useful as reference material? R/ Thanks in advance!
“Like 10 others, I get a "bad parameter" pop-up window when I try to delete 1 or more pages from a PDF created from Adobe 8 Pro from Microsoft Word 2007. Of the 3 computers we have tried to delete the pages, we are running Windows XP and Office 2007 on all. But 1 computer has Adobe 7 Pro, one has Adobe 8 Pro, and the 3rd has Adobe 9 Pro. None are able to delete or extract the pages -- we get the bad parameter error each time we try. The PDF has 260 pages and occupies 5.7 MB memory. What additional information can I provide to get a resolution to this problem? Thanks!” “Civilengr10” (posted Aug 17, 2010)
“I am taking adobe files from a database, saving them, and then making changes to them by inserting (from other adobe files from the same database) or deleting pages. Very basic stuff! However, sometimes when I want to insert pages, it will insert them but then say "bad parameter". After that point, I cannot delete any pages. It will give me the "bad parameter" error again and not delete. I have reduced the file size, ran "Examine Document" and removed whatever it wanted me to, and whenever I save a file, I do Save As...instead of Save! Also, under preferences > security I have the "Verify signatures when the document is opened" unchecked. None of these recommendations that I have read elsewhere work. Can someone offer me some guidance? I am working on the files locally. I save the files from the database unto my own folder on the computer. The thing is, some of the files I download from the database are fine and do not give me any error, but others do. Do you know how I can fix the files that are corrupted from the database?” “hoda64” (posted July 22, 2009)
“Problem converting Word 2007 DOC to PDF 9
I have a Word 2007 DOC (not docx) file with pictures and text which converted perfectly with Distiller 8. I installed CS4 Distiller 9, and now the same DOC file flows over onto several extra pages. I am using the default settings. Any idea what has changed? Thanks in advance. “Petrula” (posted Nov 29, 2002) “First, select the Adobe PDF printer in WORD. Then go through the document to check for the flow of the document. It should print the same as you see in the document after the printer has been selected.”

For the replace and delete pages, I can only guess that you are messing up some of the bookmarks or links in the page from what I think you have based on the description. I would work on copies between each stage so that you can at least go back to the last success stage. If possible, you are better to go back and do the modifications in the original page and the recreate the PDF. If that is not possible, then maybe a better explanation of how you are creating the PDF would help folks understand your process fully and suggest a solution.
On the latter, I would do a repair on Acrobat. However, it may be in the process you are using in the conversion from WORD. How are you creating the PDF from WORD? Have you updated AA9 and not simply have 9.0? The confusing point is that you talk about Distiller for getting the PDF from WORD. Distiller is often involved, but only behind the scenes and normally you either print to the Adobe PDF printer, use PDF Maker, or use the MS plugin for PDF creation. So when stating Distiller, it is unclear what process you are using since none of the methods I mention state the use of Distiller even if it is used in the background.

Contribute plugins crash Word 2007

Similar Messages

Maybe you are looking for