Create PDF crashes

Create PDF will crash after clicking on Create PDF and choosing a MS Word (or Excel) file. The words "Starting the application which created..." appear and then "Adobe Acrobat has stopped working." Create PDF Portfolio also doesn't work. But the Acrobat Create PDF tabs in Word and Excel work, as does print to Adobe PDF. Two chat sessions haven't produced any results yet. I have uninstalled and reinstalled twice, using Adobe Cleaner the most recent time, and I've repaired MS Office. Windows 7 Professional, 64-bit operating system. Acrobat 10.1.3. Word 2010, 32 bit, current with updates.

I just noticed that you indicated it happened apparently from Acrobat, but from WORD it seemed to work fine. Is that correct? In that case, I would check the preferences in Acrobat for the conversion from WORD. Also you might try playing with the right click on the DOC file in Windows Explorer to see what happens. I have a guess that it has something to do with the associations in your OS and not either WORD or Acrobat (since it supposedly works from WORD). If I have reread your post correctly, then maybe this will help the search for the solution. I do not have a 64-bit system that I am running things on, so can only guess or observe from the experiences of others.

Similar Messages

Create PDF crashes webapplication

Hi,
We have a website that creates PDF-reports using SAP Crystal Reports runtime engine for .NET Framework 4 (64-bit) SP1. The site runs on Windows 2003 R2 x64.
The site (w3wp.exe) crashes every now and then when a report is generated in PDF. We cannot trace it back to specific reports, users or actions. It seems to be random. We don't have this issue on x86-webservers with the same application and CR-version.
We got a memory dump from one of the crashes. The dump can be found [here|http://www.megaupload.com/?d=ZFVJ7FEZ] (zipped, about 330MB). Microsoft already analyzed this dump and this is the conclusion :
Here is my analysis: as you already noted, the stack goes from the SAP component to msvcr80, based on the method name (without the private symbols we cannot see the arguments passed etcu2026) it looks like they are initializing something which requires memory to be moved around, hence the call to memmove_s
0:076> kpL
Child-SP          RetAddr           Call Site
00000000`27ceec88 00000000`781b6a70 msvcr80!memcpy(unsigned char * dst = 0x00000000`26bbceb8 "???", unsigned char * src = 0x00000000`26bbceb8 "???", unsigned long count = 0)+0x1ec
00000000`27ceec90 00000000`41d69db4 msvcr80!memmove_s(void * dst = 0x00000000`00000000, unsigned int64 sizeInBytes = 2, void * src = 0x00000000`000001c2, unsigned int64 count = 0)+0x80
00000000`27ceecd0 00000000`41d6b2bc crxf_pdf!UXFInitializeW+0x1834
00000000`27ceed50 00000000`37b2d78f crxf_pdf!UXFGetExportFormatsExW+0x10c
00000000`27ceeda0 00000000`37da9c1a crpe32!CRPEConnectionInit+0x365df
00000000`27ceeef0 00000000`37da0b93 crpe32!MWCleanupProcess+0x4ffca
00000000`27ceefd0 00000000`37da54eb crpe32!MWCleanupProcess+0x46f43
00000000`27cef720 00000000`37d27bb4 crpe32!MWCleanupProcess+0x4b89b
00000000`27cef750 00000000`37d38964 crpe32!CRPEConnectionInit+0x230a04
00000000`27cef820 00000000`37d39a8f crpe32!CRPEConnectionInit+0x2417b4
00000000`27cefb90 00000000`37d39dac crpe32!CRPEConnectionInit+0x2428df
00000000`27cefbe0 00000000`37d3a45c crpe32!CRPEConnectionInit+0x242bfc
00000000`27cefd30 00000000`783917cd crpe32!CRPEConnectionInit+0x2432ac
00000000`27cefe20 00000000`781337d7 mfc80u!_AfxThreadEntry(void * pParam = 0x00000000`23e01f80)+0x101
00000000`27ceff20 00000000`78133894 msvcr80!_callthreadstartex(void)+0x17
00000000`27ceff50 00000000`77d6b71a msvcr80!_threadstartex(void * ptd = 0x00000000`77d6b6e0)+0x84
00000000`27ceff80 00000000`00000000 kernel32!BaseThreadStart(<function> * lpStartAddress = 0x00000000`00000000, void * lpParameter = 0x00000000`00000000)+0x3a
First, itu2019s interesting to note that the destination pointer does not look to be valid; the call to msvcr80!memmove_s comes directly from crxf_pdf!UXFInitializeW (there are no u201Chiddenu201D calls in the middle):
0:076> ln 00000000`41d69db4
(00000000`41d68580)   crxf_pdf!UXFInitializeW+0x1834   | (00000000`41d6b1b0)   crxf_pdf!UXFGetExportFormatsExW
The exception (an Access Violation) is actually thrown in msvcr80 while it is trying to copy the memory as a result of the move call:
0:076> .exr -1
ExceptionAddress: 000000007814e38c (msvcr80!memcpy+0x00000000000001ec)
   ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 000000002c78b280
Attempt to write to address 000000002c78b280
Also looking at the thread registers confirms that the memory address is not valid:
0:076> r
rax=0000000000000009 rbx=0000000000000413 rcx=000000002c78b280
rdx=ffffffffff9329f0 rsi=0000000000000000 rdi=0000000000000002
rip=000000007814e38c rsp=0000000027ceec88 rbp=0000000041dd42b0
r8=0000000005500dc0 r9=0000000005500dc4 r10=000000002728a4c0
r11=000000002728a4c0 r12=0000000041dd42b0 r13=0000000000000001
r14=000000002728a4c0 r15=000000002c78b284
iopl=0         nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b             efl=00010204
msvcr80!memcpy+0x1ec:
00000000`7814e38c 8901            mov     dword ptr [rcx],eax ds:00000000`2c78b280=????????
Unfortunately without the private symbols we cannot see what that memory belongs to.
Anyway since I have access to all Microsoft private symbols, the fact that I cannot find this specific one I think means this is part of the SAP components. I think we can conclude the problem originates from the crxf_pdf.dll and manifests itself in msvcr80.dll because of some wrong parameter passed into that call.
All help would be very much appreciated.
Many Thanks,
Thomas

Hi Thomas,
Since you have RAS available use this code and test again:
private void ExportToPDFRAS_Click(object sender, EventArgs e)
    //CrystalDecisions.CrystalReports.Engine.ReportDocument rpt = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
    ISCDReportClientDocument rcd;
    //rpt.Load("c:
Reports
Group.rpt");
    rcd = rptClientDoc;
    // Declare a PrintOutputController to allow documents to be exported to PDF
    PrintOutputController rasPrintOutputController;
    CrReportExportFormatEnum rasReportExportFormat;
    CrystalDecisions.Shared.DiskFileDestinationOptions diskOpts = CrystalDecisions.Shared.ExportOptions.CreateDiskFileDestinationOptions();
    diskOpts.DiskFileName = "c:
reports
reports1.pdf";
    // Set the CrReportExportFormatEnum to export the report as a PDF file.
    rasReportExportFormat = CrReportExportFormatEnum.crReportExportFormatPDF;
    rasPrintOutputController = rcd.PrintOutputController;
    // Use the Export() method of the PrintOutputController to export the report to a ByteArray.
    ByteArray tempByteArray = rasPrintOutputController.Export(rasReportExportFormat, 0);
    Byte[] byteStreamOutput = tempByteArray.ByteArray;
    System.IO.Stream oStream;
    byte[] byteArray = null;
    oStream = rpt.ExportToStream(CrystalDecisions.Shared.ExportFormatType.PortableDocFormat);
    byteArray = new byte[oStream.Length];
    oStream.Read(byteArray, 0, Convert.ToInt32(oStream.Length - 1));
    // this is used to verify the file so I saved it to disk
    System.IO.File.Create(diskOpts.DiskFileName, Convert.ToInt32(oStream.Length - 1)).Close();
    System.IO.File.OpenWrite(diskOpts.DiskFileName).Write(byteArray, 0, Convert.ToInt32(oStream.Length - 1));
    System.IO.File.SetAttributes(diskOpts.DiskFileName, System.IO.FileAttributes.Directory);
    oStream.Close();
CR requires contiguous memory space so for large reports IIS may not be able to handle cleaning up it's memory fragmentation when objects are freed up. It's a common problem with Java app's also, Java doesn't have a good memory manager either.
Because of the lack of ability to pass files through Forums I suggest you purchase a support case if you don't have a Support Contract and work with a Support engineer here to debug the problem. We can get the PDB's for those files to you if that helps MS determine what their issue is...
Thanks
Don

MSWord items that crash Adobe Acrobat 9.0 add-in (Create PDF function)

I just want to include a tip I discovered after two days of troubleshooting a colleague's MS-Word (2007 - docx) document. I tried going through the forums to see if anyone else has posted this.
Obviously, my colleague would try to use the Acrobat add-in within Word through the "Create PDF" button. But doing so causes MS-Word to crash. The crash involves the dialog box for sending an error report to MS (which I cancel).
I then attempted this on another PC and got the same result.
Another colleague on the support team suggested trying to convert only sections of the document to try and pinpoint the issue to an element within the document. The result of trial and error pointed me to a particular graphics element on Page 11 of the 46 page document. The graphics element was composed of 4 clock diagrams that were made up of smaller elements (arrowheads and lines for the clock-hands, separate textboxes for the numbers 1 - 12 on each circular clockface, etc.) Deleting the whole graphic allowed the document to be converted to PDF.
I then reverted to the original document and clicked on the graphic. I was about to investigate if there was a particular element within the grouped graphic that caused the crash, but, by luck, I was able to discover that just by ungrouping the graphic into its elemental components "Create PDF" was able to render the PDF successfully.
Perhaps this is something to try in the future should anyone run into this issue. I hope this helps someone else.

It may be something that Adobe did not catch in the way that MS did the graphic processing (and to be sure MS does not always do things by the book). It may have been fixed. I note that you only have AA9.0. The current version is AA9.3.4, so an update might be in order. Potentially that would resolve the problem.
In any case, I have found the graphic processing done by WORD 2007 to be strange. Taking the same file to WORD 2003 (saving to a DOC format if required) has no problem with the conversion. So there are likely problems from both MS and Adobe.

Adobe Acrobat XI Standard crashes when we create pdf from scanner

We are using adobe acrobat XI standard, version 11.0.06
WIndows 7 Pro 64 bit
scanner: Xerox documate 4799
Acrobat crashes when we create pdf from scanner

Spent quite a while on this one.. My problem was related to twain drivers which reside in c:\windows\twain_32. I'm running windows 7 64-bit. First it's usually possible to scan in windows 7 maybe vista and from adobe without even using twain (using WIA). So try renaming the twain_32 folder to _twain_32 and see what happens... If that stops the crashing look at the contents of the twain folder. I had a Dell folder for some printer I wasn't even using. That was causing the crash. I removed the dell folder and renamed the twain folder back to twain_32. Now everything works as designed.

"Create PDF from scanner" causes Adobe 8.1 to crash

Can anyone help us repair Acrobat 8? Or upgrade/reinstall Acrobat 9? We've got WinXP, running SP 3.
When we moved our PC to our new office, the create PDF from scanner function quit working, and now makes the entire program crash. We can still create PDFs other ways, but from scanner isn't working - the "Acrobat Scan" dialog box opens, but after about 5-10 seconds, the crash window comes up. Repairing, updating, uninstalling, and reinstalling the software all fail. Here are the errors for each attempt:
Repairing: "Preparing to install" dialog pops up but immediately disappears and no further action takes place.
Updating: It attempts to install update to 8.1.4, and the process begins, but after 5-10 seconds quits with error dialog "The installation process has encountered a problem. Please choose from the following options:" with 3 choices - run again, stop and start later, or cancel and quit. Selecting "run update again" just causes the error dialog to come up again. The other 2 quit the install entirely.
Uninstalling (via add/remove programs) and reinstalling (via downloading the software from the Order ID site again) both fail independent of each other with the same error: “The installation source for this product is not available. Verify that the source exists and that you can access it.”
We do a lot of scanning to PDF's ... how can we fix this? There've been no other PC problems whatsoever, otherwise ...
My name is Scott Knowles, tech support guy for my sister's PC ... whose account this is.

The scanner is an all-in-one printer, in perfect working order otherwise. Good idea though - I tried scanning *outside* the Acrobat software ... that proved the scanner software *is* faulty ... I'll repair that. Thank you !

Acrobat 8.1 Crashing when creating PDF from webpage

www.sec.gov/Archives/edgar/data/910569/000091056909000016/form6-k15june09.htm
I have been trying to create a PDF from the above URL using Acrobat 8.1 using the "Create PDF from Web Page" function. The Download Status form opens and shows the progress as files are downloaded and converted. However Acrobat 8.1 always crashes before completing the task. Acrobat 5.0 successfully completes the task although the formatting leaves a lot to be desired but that's another issue.
I've tried various values for settings such as processing 1 level or getting entire site but the crash is consistent.
I have also tried a couple of other machines in the office with the same crashed result.
Can anybody suggest why Acrobat 8.1 would fail to render this URL into a PDF and what would cause it to crash so consistently? Is there an alternate method of creating a PDF from this URL aside from loading it into Word and printing to a PDF?
Any clues appreciated!

The problem is likely that the web page does not conform to standard HTML. AA8 crashed on me also. You can print the file from your browser. The only thing that would be missing would be the 3 links near the bottom and they are easy to add.

Acrobat Standard 9.1.1 crashes on Create PDF from scanner

All options under the Create PDF from scanner sends Acrobat Standard 9.1.1 crashing.
Faulting application Acrobat.exe, version 9.1.0.163, time stamp 0x49a88b32, faulting module dlbatwds.ds, version 3.107.0.0, time stamp 0x45df4d3d, exception code 0xc0000005, fault offset 0x00004da2, process id 0xce4, application start time 0x01c9dca1b4c4360b.
Tried with both scanners CanoScan LiDE 600F and Dell 920A
I am using Vista Ultimate x64.Have tried turning off UAC and also tried running as Administrator.
No luck yet. Anyone have the same issue?

This might be a scanner issue. Have you tried scanning using other applications?
If not, can you try the following steps once?
1. Download TWACKER (Twack_32.msi) from http://www.twain.org/downloads.shtm
2. Install it.
3. Go to <Program files>\TWAIN Working Group\Twacker 32 and invoke Twack_32.exe.
4. Go to File menu > Select Source.
5. Select the TWAIN driver (not the WIA driver) for HP M1212nf and Click OK.
6. Now, invoke File > Acquire menu.
Please update with the result.

Unable to create pdf files after upgrade to acrobat dc, acrobat crashes

Since I just upgraded to Acrobat DC I am not able to create PDF files any more. Whatever program I tried, the PDF-printing process always crashes. Deinstallation and reinstallation does not help in any way. Even worse, there is no option to install any former version of Adobe Acrobat through the Creative Cloud App. Any office or CAD software from which I am trying to print also totally stucks from the PDF printing process. I am a freelancer and have some urgent deadlines tomorrow, so the last thing I need right now is trouble with my pdf-printer. Any help is highly appreciated. (Windows 7 Professional, HP ZBook 15 Mobile Workstation).

For those of you who are Creative Cloud members and are facing the same problem, this is the way to reinstall Acrobat XI Pro (you will not find this option within the Creative Cloud App):
1. Make sure you uninstalled Acrobat DC.
2. Log in with your account data on https://creative.adobe.com
3. Go to https://creative.adobe.com/de/products/acrobat
4. Choose Acrobat XI Pro from the dropdown menu and click the download button.
5. An event handler will ask you in a popup window if you want to open the link within the Adobe Creative Cloud App. Choose CreativeCloud(URIHandler) from the list and hit okay.
6. The Download will now apear in the Apps list of the Creative Cloud App and can be installed by hitting the Install button.
Took me some time to figure that out and I would prefer to use the latest Acrobat version. But as long as Acrobat DC causes my other applications to crash, Acrobat XI Pro will do the job.

Adobe Standard 9.1.0 crashes when attempting create .pdf from scanner

Adobe Standard 9.1.0 crashes when attempting "create .pdf from scanner" from a Kyocera Mita KM-2550 using the twain driver. The error encountered is 0xc0000005 at address 0x0000000002d78e70. I have downloaded and installed the latest updates. This is happening on two new PCs with the same configuration. Is anyone else having this problem? Any suggestions?

Spent quite a while on this one.. My problem was related to twain drivers which reside in c:\windows\twain_32. I'm running windows 7 64-bit. First it's usually possible to scan in windows 7 maybe vista and from adobe without even using twain (using WIA). So try renaming the twain_32 folder to _twain_32 and see what happens... If that stops the crashing look at the contents of the twain folder. I had a Dell folder for some printer I wasn't even using. That was causing the crash. I removed the dell folder and renamed the twain folder back to twain_32. Now everything works as designed.

Acrobat 10 crashes when "create pdf with scanner" command attempted.

Hello
For many months I have employed Acrobat 10 and an Epson V700 photo scanner successfully on a win 7 64 platform. I employ the create pdf from scanner command, select the custom scan option and allow the Epson scanning application to launch. Again this has worked without a problem.
For over a week, however, just as I am about to hand off scanning to the Espson scanning app, Acrobat crashes!!!
I have followed other threads in the Adobe Community with total reinstall of Acrobat 10, bcdedit command line commands, and a repair process through control panel of Acrobat 10. Nothing has worked.
I now have captured the process crash file with Sysinternals procdump.exe employing the c:\temp>prodump -e -ma Acrobat.exe c:\temp\01.dmp that I found on a similar Adobe Community thread. The file is over 154 mb!
Please advise me on how to provide diagnostic data and steps to take to recover this extremely important function of my Acrobat 10!
Thank you
H Flemming
Message was edited by: HFlemming

Hello
For many months I have employed Acrobat 10 and an Epson V700 photo scanner successfully on a win 7 64 platform. I employ the create pdf from scanner command, select the custom scan option and allow the Epson scanning application to launch. Again this has worked without a problem.
For over a week, however, just as I am about to hand off scanning to the Espson scanning app, Acrobat crashes!!!
I have followed other threads in the Adobe Community with total reinstall of Acrobat 10, bcdedit command line commands, and a repair process through control panel of Acrobat 10. Nothing has worked.
I now have captured the process crash file with Sysinternals procdump.exe employing the c:\temp>prodump -e -ma Acrobat.exe c:\temp\01.dmp that I found on a similar Adobe Community thread. The file is over 154 mb!
Please advise me on how to provide diagnostic data and steps to take to recover this extremely important function of my Acrobat 10!
Thank you
H Flemming
Message was edited by: HFlemming

Acrobat 9.5 hangs creating PDFs.

Why does my Adobe Acrobat 9.5 hang when creating PDF? The progress bar just stop about 2/3 through. I have Windows 7. Thanks.

Say for example... I want to print an online "order" receipt to PDF. Or print to PDF a web page of any sort. It didn't used to hang up.
Date: Fri, 18 Jan 2013 13:27:24 -0700
From: [email protected]
To: [email protected]
Subject: Acrobat 9.5 hangs creating PDFs.
    Re: Acrobat 9.5 hangs creating PDFs.
    created by Daniel Flavin in Printing & Prepress - View the full discussion
Is this global to Create PDF or (more likely) for a particular file?
Is this Create PDF from
- multiple pdf's?
- from file(s)?
Crashes/Hangs related to Create PDF from file could indicate a corrupt image file within the source document.
Chop the document in half, try to Create PDF, try the other half of the file. It would not take long to isolate a bad page or graphic.
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5005329#5005329
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5005329#5005329
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5005329#5005329. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Printing & Prepress by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Problem with creating pdf from Microsoft Publisher 2013

We are having problems in creating pdfs from Microsoft Publisher2010- When the function 'Adobe PDF' is selected and 'Print' is clicked on nothing happens. The progress bar just sits there for several minutes without creating a pdf. We have to click on cancel and when this is done this crashes Microsft Publisher.
I have repaired this using the repair facility in Acrobat 9. I have also uninstalled Acrobat 9 and reinstalled this.
I have also uninstalled Adobe Reader XI and reinstalled Adobe Reader 9.
Before uninstalling Acrobat I also ran the updates but this didnt help either.
This is on a Windows 7 PC (64-bit)
Adobe Acroabt 9 Pro Extended
Microsoft Publisher 2010.
Any help is appreciated.
Thanks

MS Publisher 2010 is not supported by the Acrobat 9 Family; and the PDFMaker extension for Publisher has been removed completely from the Acrobat XI Family, so upgrading won't help either. Sorry!
See http://helpx.adobe.com/acrobat/kb/compatible-web-browsers-pdfmaker-applications.html#main_ PDFMaker_compatible_applications

Save as PDF crashes every application

When I select Print > Save as PDF, it immediately crashes any application that I am in. I cannot create PDFs anymore, tried Safari, Mail, Chrome, TextEdit, Word.
Word's Error Reporting tool gave this error info:
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2014-10-07 22:37:06 +0000
Application Name: Microsoft Word
Application Bundle ID: com.microsoft.Word
Application Signature: MSWD
Application Version: 14.4.4.140807
Crashed Module Name: libobjc.A.dylib
Crashed Module Version: unknown
Crashed Module Offset: 0x000044a7
Blame Module Name: FXPSACEAccount
Blame Module Version: 1.71
Blame Module Offset: 0x000139db
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Crashed thread: 0
Anyone has any ideas how to fix this? Thanks!

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the name of the crashed application or process. For example, if Safari crashed, you would enter "Safari" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ User Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of crash reports. The name of each report starts with the name of the process, and ends with ".crash". Select the most recent report related to the process in question. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Can't create PDFs from Acrobat or Word?

Downloaded the 8.1.4 update and now I can't create PDFs from Acrobat or Word. If I try to create a PDF from the print menu, I get a message indicating that there are no print drivers for this...any ideas?

Thanks for responding. Yep, I tried repairing it...no dice. Then I realized that I'd re-installed AA Pro 8 (having completely given up on the AA Pro 9 upgrade that crashed my system) but not the updates. So I went through and re-installed each update. Still no dice. Then I did another repair. Nope. When I try to create a PDF via the print menu, I get a "Windows cannot print due to a problem with the current printer setup." This tells me that I have driver problem. But everything else prints fine, and I'm pretty sure Acrobat doesn't have drivers. I'm stumped...

Creating .pdfs

I am having trouble creating pdfs.
I am running the latest flavour of Leopard, Office Mac 2008, together with Acrobat Professional 8.1.2.
If I try and create a pdf from within Acrobat using the Create command I get an error telling me that
the document is not a supported file type of has been corrupted. (It is a .doc file)
If I open Word and print using Adobe 8.0 printer, it appears to print the .doc file, but I can't find it afterwards.
If I use distiller to try and create fails to create the .pdfs and gives an error message.
The only way I can creat .pdfs is by highlighting the document in Finder and using the print command with Adobe 8.0 set as the default printer. It then dumps them all on the desktop with amended file names. It adds WORD DOCUMENT as a prefix and keeps .doc as well as .pdf.
Am I doing it wrong or do I have a problem?
Thanks
Tony

Tony,
Try to keep track of what is open, where the file is located and where
you are trying to save. It could be that an application you are using
has a memory leak and that you run out of RAM. Check our the available
RAM, when the pdf is not produced. See if there are any applications or
process that is running that be coincidental to the problem. The
Activity monitor can be helpful in tracking things down. Make sure that
Distiller is always set to keep the log file so that you can see what is
happening.
I remember an ancient issue with Microsoft Word. When you quit Word,
the next application would crash the system. Trying to track down the
problem with crashes was tough, because it wasn't the application you
were running that caused the problem, but the one you weren't.
In your case since the issue seems sporadic, it will take detailed notes
and patience to track down the problem.
Mike

Create PDF crashes

Similar Messages

Maybe you are looking for