RE: The dreaded Internal Error error meets the dreaded Adobesupport, sigh
Emily/all, Just for the record, this isn't a problem on my system. I still have 20 GB free on my hard drive, although I suppose the existing files could use defragmenting. Deleting FNTCACHE.DAT still seems to be doing the trick for me. Thanks also to Shmuel and Mike for the advice on the batch file. Regards and thanks, ken -Original Message- From: Emily Berk [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 16, 2008 8:04 PM To: Ken Stitzel; framers@lists.frameusers.com Subject: RE: The dreaded Internal Error error meets the dreaded Adobesupport, sigh Hey, Ken: I know that you know that I empathize deeply with the utter frustration you must feel. One suggestion, and I know a number of very helpful ones have been proffered here recently... Is your C drive getting a bit -- crowded? And/or the destination drive of your .ps file? ... ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
The dreaded Internal Error error meets the dreaded Adobesupport, sigh
You could make a simple batch file to delete the two FNTCACHE.DAT files and put on the Quick Start section of the taskbar, or wherever it's convenient for you. This doesn't completely automate the process, but it's close. Regards, Shmuel Wolfson Ken Stitzel wrote: > THANK YOU to the longsuffering Emily for raising the topic and to > everyone who responded to her plea with helpful suggestions. I, too, > have labored under the same massively frustrating problem. Adobe support > had a few suggestions but was largely a useless ineffective joke. The > problem kept recurring, leaving me in hot water with my boss and dead in > the water when trying to meet critical deadlines. AUGH! > > What finally SEEMS to have fixed the problem for me (crossing fingers, > knocking on wood, hoping that Murphy's Law will not now extract a > horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT > file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured > out a way to automate this yet, but I did create some shortcuts to the > relevant directories so I can Eradicate the Evil Badness when necessary. > > Perhaps others can benefit from the key lessons of my saga of agony: > > * The suggestion about going to "Generate Acrobat Data", ticking the > "Generate Tagged PDF" box, and removing most of the objects to tag did > not ever prevent the error/crash for me. However, it does seem to be > good practice to reduce overhead in the PDF generation process. > > * Adobe's suggestion that I save everything as MIF and then reopen it > worked with some books but not others--plus the Internal Error happened > even with Frame files that had never used imported Word files. Clearly, > this is an inconvenient and time-consuming process if you've got a lot > of documents. (I didn't try to automate it since it never fixed the > crash problem.) On the plus side, I think I will use this process > whenever I first import Word documents into Frame, since it seems to > remove some potential problems left over from the conversion. > > * Reinstalling FrameMaker worked, sort of--except that it would only > work for a while before the problem returned, and it didn't work unless > I reinstalled Frame AND Acrobat AND all the latest patches. That's quite > a time-sink by the time you perform both reinstalls and download the > latest patches. (Adobe's servers can run quite slowly during the day). I > think this approach worked only because it got rid of--or temporarily > changed--the FNTCACHE.DAT file, which would then would return in an Evil > form at some point and crash the whole works all over again. > > * Installing Ixgen with Frame 8 brought the Internal Error back. I'm > hoping this is again because of the FNTCACHE.DAT file, and that I can > get Ixgen to work with Frame 8 eventually. When I'm feeling brave > between deadlines, I'll try again. > > * I tried rolling my system back to Frame 7.2 and Acrobat 6, both of > which had worked flawlessly in tandem for more than a year. But, in a > fit of apparent Evil, Adobe saw fit to lobotomize earlier versions of > Acrobat after I had once installed Acrobat 8. Great strategy for making > me feel hostile toward Adobe and extremely suspicious of all of their > software and updates. Thanks, guys. > > It sucks that Adobe broke its own software so badly, putting so many > through software agony while just trying to do their jobs. I hope this > particular tale of woe ends for one and all--or that at least we all > have some decent workarounds in our respective arsenals. > > Kendal Stitzel > > SkyeTek, Inc. (making the physical digital with RFID--or at least trying > to via my tech docs) > ___ > > > You are currently subscribed to Framers as sbw at actcom.com. > > Send list messages to framers at lists.frameusers.com. > > To unsubscribe send a blank email to > framers-unsubscribe at lists.frameusers.com > or visit http://lists.frameusers.com/mailman/options/framers/sbw%40actcom.com > > Send administrative questions to listadmin at frameusers.com. Visit > http://www.frameusers.com/ for more resources and info. > >
The dreaded Internal Error error meets the dreaded Adobesupport, sigh
Emily/all, Just for the record, this isn't a problem on my system. I still have 20 GB free on my hard drive, although I suppose the existing files could use defragmenting. Deleting FNTCACHE.DAT still seems to be doing the trick for me. Thanks also to Shmuel and Mike for the advice on the batch file. Regards and thanks, ken -Original Message- From: Emily Berk [mailto:em...@armadillosoft.com] Sent: Wednesday, January 16, 2008 8:04 PM To: Ken Stitzel; framers at lists.frameusers.com Subject: RE: The dreaded Internal Error error meets the dreaded Adobesupport, sigh Hey, Ken: I know that you know that I empathize deeply with the utter frustration you must feel. One suggestion, and I know a number of very helpful ones have been proffered here recently... Is your C drive getting a bit -- crowded? And/or the destination drive of your .ps file? ...
Re: The dreaded Internal Error error meets the dreaded Adobesupport, sigh
You could make a simple batch file to delete the two FNTCACHE.DAT files and put on the Quick Start section of the taskbar, or wherever it's convenient for you. This doesn't completely automate the process, but it's close. Regards, Shmuel Wolfson Ken Stitzel wrote: > THANK YOU to the longsuffering Emily for raising the topic and to > everyone who responded to her plea with helpful suggestions. I, too, > have labored under the same massively frustrating problem. Adobe support > had a few suggestions but was largely a useless ineffective joke. The > problem kept recurring, leaving me in hot water with my boss and dead in > the water when trying to meet critical deadlines. AUGH! > > What finally SEEMS to have fixed the problem for me (crossing fingers, > knocking on wood, hoping that Murphy's Law will not now extract a > horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT > file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured > out a way to automate this yet, but I did create some shortcuts to the > relevant directories so I can Eradicate the Evil Badness when necessary. > > Perhaps others can benefit from the key lessons of my saga of agony: > > * The suggestion about going to "Generate Acrobat Data", ticking the > "Generate Tagged PDF" box, and removing most of the objects to tag did > not ever prevent the error/crash for me. However, it does seem to be > good practice to reduce overhead in the PDF generation process. > > * Adobe's suggestion that I save everything as MIF and then reopen it > worked with some books but not others--plus the Internal Error happened > even with Frame files that had never used imported Word files. Clearly, > this is an inconvenient and time-consuming process if you've got a lot > of documents. (I didn't try to automate it since it never fixed the > crash problem.) On the plus side, I think I will use this process > whenever I first import Word documents into Frame, since it seems to > remove some potential problems left over from the conversion. > > * Reinstalling FrameMaker worked, sort of--except that it would only > work for a while before the problem returned, and it didn't work unless > I reinstalled Frame AND Acrobat AND all the latest patches. That's quite > a time-sink by the time you perform both reinstalls and download the > latest patches. (Adobe's servers can run quite slowly during the day). I > think this approach worked only because it got rid of--or temporarily > changed--the FNTCACHE.DAT file, which would then would return in an Evil > form at some point and crash the whole works all over again. > > * Installing Ixgen with Frame 8 brought the Internal Error back. I'm > hoping this is again because of the FNTCACHE.DAT file, and that I can > get Ixgen to work with Frame 8 eventually. When I'm feeling brave > between deadlines, I'll try again. > > * I tried rolling my system back to Frame 7.2 and Acrobat 6, both of > which had worked flawlessly in tandem for more than a year. But, in a > fit of apparent Evil, Adobe saw fit to lobotomize earlier versions of > Acrobat after I had once installed Acrobat 8. Great strategy for making > me feel hostile toward Adobe and extremely suspicious of all of their > software and updates. Thanks, guys. > > It sucks that Adobe broke its own software so badly, putting so many > through software agony while just trying to do their jobs. I hope this > particular tale of woe ends for one and all--or that at least we all > have some decent workarounds in our respective arsenals. > > Kendal Stitzel > > SkyeTek, Inc. (making the physical digital with RFID--or at least trying > to via my tech docs) > ___ > > > You are currently subscribed to Framers as [EMAIL PROTECTED] > > Send list messages to [EMAIL PROTECTED] > > To unsubscribe send a blank email to > [EMAIL PROTECTED] > or visit http://lists.frameusers.com/mailman/options/framers/sbw%40actcom.com > > Send administrative questions to [EMAIL PROTECTED] Visit > http://www.frameusers.com/ for more resources and info. > > ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: The dreaded Internal Error error meets the dreaded Adobesupport, sigh
Hey, Ken: I know that you know that I empathize deeply with the utter frustration you must feel. One suggestion, and I know a number of very helpful ones have been proffered here recently... Is your C drive getting a bit -- crowded? And/or the destination drive of your .ps file? As I think about my nightmare, nothing had changed in terms of my Frame doc, fonts, software versions, etc. However, my C drive was very full. My theory about what might have triggered the initial Internal Error is that FM could not find room to store the .ps file. Now, why it decided to overwrite itself on disk when that happened, well, that is between Adobe and its developers. But -- maybe you should try to make sure there is a huge amount of extra space on your C drive and on the destination drive of the .ps before you try to generate the .ps file. Anyway, here's hoping for more reliable PDF-ing for us all. -- Emily At 09:41 AM 1/16/2008, Ken Stitzel wrote: >THANK YOU to the longsuffering Emily for raising the topic and to >everyone who responded to her plea with helpful suggestions. I, too, >have labored under the same massively frustrating problem. Adobe support >had a few suggestions but was largely a useless ineffective joke. The >problem kept recurring, leaving me in hot water with my boss and dead in >the water when trying to meet critical deadlines. AUGH! > >What finally SEEMS to have fixed the problem for me (crossing fingers, >knocking on wood, hoping that Murphy's Law will not now extract a >horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT >file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured >out a way to automate this yet, but I did create some shortcuts to the >relevant directories so I can Eradicate the Evil Badness when necessary. > >... Emily Berk http://www.armadillosoft.com ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
The dreaded Internal Error error meets the dreaded Adobesupport, sigh
Hey, Ken: I know that you know that I empathize deeply with the utter frustration you must feel. One suggestion, and I know a number of very helpful ones have been proffered here recently... Is your C drive getting a bit -- crowded? And/or the destination drive of your .ps file? As I think about my nightmare, nothing had changed in terms of my Frame doc, fonts, software versions, etc. However, my C drive was very full. My theory about what might have triggered the initial Internal Error is that FM could not find room to store the .ps file. Now, why it decided to overwrite itself on disk when that happened, well, that is between Adobe and its developers. But -- maybe you should try to make sure there is a huge amount of extra space on your C drive and on the destination drive of the .ps before you try to generate the .ps file. Anyway, here's hoping for more reliable PDF-ing for us all. -- Emily At 09:41 AM 1/16/2008, Ken Stitzel wrote: >THANK YOU to the longsuffering Emily for raising the topic and to >everyone who responded to her plea with helpful suggestions. I, too, >have labored under the same massively frustrating problem. Adobe support >had a few suggestions but was largely a useless ineffective joke. The >problem kept recurring, leaving me in hot water with my boss and dead in >the water when trying to meet critical deadlines. AUGH! > >What finally SEEMS to have fixed the problem for me (crossing fingers, >knocking on wood, hoping that Murphy's Law will not now extract a >horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT >file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured >out a way to automate this yet, but I did create some shortcuts to the >relevant directories so I can Eradicate the Evil Badness when necessary. > >... Emily Berk http://www.armadillosoft.com
The dreaded Internal Error error meets the dreaded Adobesupport, sigh
> What finally SEEMS to have fixed the problem for me (crossing fingers, > knocking on wood, hoping that Murphy's Law will not now extract a > horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT > file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured > out a way to automate this yet, but I did create some shortcuts to the > relevant directories so I can Eradicate the Evil Badness when necessary. > > Create a plain text file containing the following lines: @echo off REM Delete fntcache.dat del c:\windows\system32\fntcache.dat REM Restart Windows in two seconds C:\WINDOWS\system32\shutdown.exe -r -t 02 Name the file with a .BAT extension and place it on your desktop. Double-clicking the file will run it. I'm not sure it's necessary to remove the fntcache.dat file in C:\i386, but if you also want to do it, use this file text instead: @echo off REM Delete fntcache.dat del c:\windows\system32\fntcache.dat del c:\i386\fntcache.dat REM Restart Windows in two seconds C:\WINDOWS\system32\shutdown.exe -r -t 02 Mike Wickham
Re: The dreaded Internal Error error meets the dreaded Adobesupport, sigh
> What finally SEEMS to have fixed the problem for me (crossing fingers, > knocking on wood, hoping that Murphy's Law will not now extract a > horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT > file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured > out a way to automate this yet, but I did create some shortcuts to the > relevant directories so I can Eradicate the Evil Badness when necessary. > > Create a plain text file containing the following lines: @echo off REM Delete fntcache.dat del c:\windows\system32\fntcache.dat REM Restart Windows in two seconds C:\WINDOWS\system32\shutdown.exe -r -t 02 Name the file with a .BAT extension and place it on your desktop. Double-clicking the file will run it. I'm not sure it's necessary to remove the fntcache.dat file in C:\i386, but if you also want to do it, use this file text instead: @echo off REM Delete fntcache.dat del c:\windows\system32\fntcache.dat del c:\i386\fntcache.dat REM Restart Windows in two seconds C:\WINDOWS\system32\shutdown.exe -r -t 02 Mike Wickham ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
The dreaded Internal Error error meets the dreaded Adobesupport, sigh
THANK YOU to the longsuffering Emily for raising the topic and to everyone who responded to her plea with helpful suggestions. I, too, have labored under the same massively frustrating problem. Adobe support had a few suggestions but was largely a useless ineffective joke. The problem kept recurring, leaving me in hot water with my boss and dead in the water when trying to meet critical deadlines. AUGH! What finally SEEMS to have fixed the problem for me (crossing fingers, knocking on wood, hoping that Murphy's Law will not now extract a horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured out a way to automate this yet, but I did create some shortcuts to the relevant directories so I can Eradicate the Evil Badness when necessary. Perhaps others can benefit from the key lessons of my saga of agony: * The suggestion about going to "Generate Acrobat Data", ticking the "Generate Tagged PDF" box, and removing most of the objects to tag did not ever prevent the error/crash for me. However, it does seem to be good practice to reduce overhead in the PDF generation process. * Adobe's suggestion that I save everything as MIF and then reopen it worked with some books but not others--plus the Internal Error happened even with Frame files that had never used imported Word files. Clearly, this is an inconvenient and time-consuming process if you've got a lot of documents. (I didn't try to automate it since it never fixed the crash problem.) On the plus side, I think I will use this process whenever I first import Word documents into Frame, since it seems to remove some potential problems left over from the conversion. * Reinstalling FrameMaker worked, sort of--except that it would only work for a while before the problem returned, and it didn't work unless I reinstalled Frame AND Acrobat AND all the latest patches. That's quite a time-sink by the time you perform both reinstalls and download the latest patches. (Adobe's servers can run quite slowly during the day). I think this approach worked only because it got rid of--or temporarily changed--the FNTCACHE.DAT file, which would then would return in an Evil form at some point and crash the whole works all over again. * Installing Ixgen with Frame 8 brought the Internal Error back. I'm hoping this is again because of the FNTCACHE.DAT file, and that I can get Ixgen to work with Frame 8 eventually. When I'm feeling brave between deadlines, I'll try again. * I tried rolling my system back to Frame 7.2 and Acrobat 6, both of which had worked flawlessly in tandem for more than a year. But, in a fit of apparent Evil, Adobe saw fit to lobotomize earlier versions of Acrobat after I had once installed Acrobat 8. Great strategy for making me feel hostile toward Adobe and extremely suspicious of all of their software and updates. Thanks, guys. It sucks that Adobe broke its own software so badly, putting so many through software agony while just trying to do their jobs. I hope this particular tale of woe ends for one and all--or that at least we all have some decent workarounds in our respective arsenals. Kendal Stitzel SkyeTek, Inc. (making the physical digital with RFID--or at least trying to via my tech docs)
RE: The dreaded Internal Error error meets the dreaded Adobesupport, sigh
THANK YOU to the longsuffering Emily for raising the topic and to everyone who responded to her plea with helpful suggestions. I, too, have labored under the same massively frustrating problem. Adobe support had a few suggestions but was largely a useless ineffective joke. The problem kept recurring, leaving me in hot water with my boss and dead in the water when trying to meet critical deadlines. AUGH! What finally SEEMS to have fixed the problem for me (crossing fingers, knocking on wood, hoping that Murphy's Law will not now extract a horrible vengeance) is the suggestion about deleting the FNTCACHE.DAT file in the C:\i386 and C:\WINDOWS\system32 folders. I haven't figured out a way to automate this yet, but I did create some shortcuts to the relevant directories so I can Eradicate the Evil Badness when necessary. Perhaps others can benefit from the key lessons of my saga of agony: * The suggestion about going to "Generate Acrobat Data", ticking the "Generate Tagged PDF" box, and removing most of the objects to tag did not ever prevent the error/crash for me. However, it does seem to be good practice to reduce overhead in the PDF generation process. * Adobe's suggestion that I save everything as MIF and then reopen it worked with some books but not others--plus the Internal Error happened even with Frame files that had never used imported Word files. Clearly, this is an inconvenient and time-consuming process if you've got a lot of documents. (I didn't try to automate it since it never fixed the crash problem.) On the plus side, I think I will use this process whenever I first import Word documents into Frame, since it seems to remove some potential problems left over from the conversion. * Reinstalling FrameMaker worked, sort of--except that it would only work for a while before the problem returned, and it didn't work unless I reinstalled Frame AND Acrobat AND all the latest patches. That's quite a time-sink by the time you perform both reinstalls and download the latest patches. (Adobe's servers can run quite slowly during the day). I think this approach worked only because it got rid of--or temporarily changed--the FNTCACHE.DAT file, which would then would return in an Evil form at some point and crash the whole works all over again. * Installing Ixgen with Frame 8 brought the Internal Error back. I'm hoping this is again because of the FNTCACHE.DAT file, and that I can get Ixgen to work with Frame 8 eventually. When I'm feeling brave between deadlines, I'll try again. * I tried rolling my system back to Frame 7.2 and Acrobat 6, both of which had worked flawlessly in tandem for more than a year. But, in a fit of apparent Evil, Adobe saw fit to lobotomize earlier versions of Acrobat after I had once installed Acrobat 8. Great strategy for making me feel hostile toward Adobe and extremely suspicious of all of their software and updates. Thanks, guys. It sucks that Adobe broke its own software so badly, putting so many through software agony while just trying to do their jobs. I hope this particular tale of woe ends for one and all--or that at least we all have some decent workarounds in our respective arsenals. Kendal Stitzel SkyeTek, Inc. (making the physical digital with RFID--or at least trying to via my tech docs) ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
