karuntsd wrote Still no fix. Disappointing that Adobe did not even bother to reply to this question. Especially when I am asking this for a corporate firm using their products. |
Quite frankly, these forums are not Adobe Technical Support. Responses are typically provided by users who may know the answer to your question or perhaps can provide assistance in tracking down the problem. In this particular case, you probably didn't get an earlier response since none of the usual forum participants encountered the particular printing issue and/or knew how that might be associated with the directory structure you mention.
Also, if you are a corporate licensee, there are other specific channels you can be using to directly connect with Adobe.
In terms of your particular issue, it is definitely not safe to totally delete C:\Users\USERPROFILE\AppData\Local\Adobe if you have multiple Adobe applications installed since it isn't only Acrobat that uses this directory tree.
On the other hand if you delete C:\Users\USERPROFILE\AppData\Local\Adobe\Acrobat you will simply be deleting some directories and cache files used by various Acrobat components to optimize performance, primarily but not limited to font enumeration and caching and icon caching. They are rebuilt (with a performance hit) if they are not found by Acrobat, Acrobat Distiller, or Acrobat PDFMaker when they next execute.
It is interesting that effectively deleting the directory structure resolved network printing issues since as far as I can tell, there is nothing in at least the Acrobat subdirectories that has anything to do with print unless one or more of the font cache files got corrupted somehow with a secondary effect being printer issues. The only way to determine what was really going on would be if this was to happen again, to be able to get a very high level Acrobat Tech Support staff member to be able to examine your system on-line to try to find hints as to what was the underlying problem.
I guess the good news is that at least the print issues seems to have dissipated with zapping the directory, although unfortunately we don't have any good reason to explain why that helped in this instance.
- Dov
AdChoices