![]() If the file indicates why Acrobat Distiller couldn't create the PDF file, use the search text box on Acrobat Help and Support to search for related documents.Somehow the steps identified above forces the memory to flush from the previous scan and readies the new scan preventing the crash. Appears memory isn't being cleared after a document is created, and when a new document is created there are problems with buffer overflows. Looks like I was wrong in my earlier post about a bug in the TWAIN interface. Previously it would randomly crash after one, two or three scans. Don't forget to save the previously scanned documents just in case Acrobat crashes.Īcrobat crashed only once while scanning multiple documents using this method. ![]() Continue to leave at least one previously scanned document open when scanning additional documents. ![]() It must be closed otherwise Acrobat will lockup hard.ī. If you are appending a scan to an existing document DO NOT leave the document for which the new scan is being appended open. Note that if you have previously scanned documents open the default option for this setting is "Append to File".Ī. From the settings page select output of "Create New PDF". Do this even if the settings are what you want.ģ. This will bring up a page to configure specific settings for the scan. When creating the next pdf document using scan select the settings icon next to the document type you will be creating. Make sure you save the previous scan before performing the next scan.Ģ. Is your AV affecting it?Ī quick follow-up and potential work around that has been working for me when scanning multiple documents -ġ. This all probably doesn't help solve it for you, unfortunately, but if it's something you haven't considered yet then you might want to investigate. This was after I uninstalled, rebooted, used the Adobe clean up tool, rebooted, unloaded my AV, reinstalled Acrobat, reloaded my AV. I solved the Acrobat issue by adding it to Trend's "Trusted Program" list (same with Firefox) on my local machine (using IT's password - HA!). I ended up with over 600 of them there should only be one!) (As an aside, the Trend update also locked my prefs.js file in Firefox, which meant that everytime I closed out of Firefox several new prefs.js files were created, each with a new number, eg prefs-1.js. For me, it caused my Acrobat DC to start crashing. I'm in a corporate environment, and our IT made changes to Trend settings on the firewall, and since then it's actually caused no end of problems. In my case, I've subsequently discovered that the cause of the issue for me was interference by my AV software: Trend OfficeScan. I think this BEX error is what's known as a buffer overflow exception, and the cause for it could be literally anything. Anyone have any ideas on this please? Windows 7, I'm sorry you're struggling with this too. This is enormously disruptive to my work. adding the program to the DEP (Data execution prevention) exception list (which it turns out it CAN'T be added to because it must be turned on for this program)Īdditional Information 2: a7aa91f17ea749d42a4de3b390fa5b3dĪdditional Information 4: a7aa91f17ea749d42a4de3b390fa5b3d.Some googling has indicated that this error occurs in other applications, not just Adobe. The Problem Event Name is BEX (Buffer Overflow Exception). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |