When open a pdf file, a file created "debug.log".

Report · Sep 28, 2021

Hi!

When I open a pdf file in a network folder, a file"debug.log" appears in the same folder.

Use Abobe Acrobat DC 21.007.20091

Report · Sep 28, 2021

Hi Евгений,

Thank you for reaching out.

Please let us know if this happens only when you try to open the file from network drive.

Check if the issue occurs with all files or with some particular ones.

Share the OS version used on the machine.

Thanks,

Meenakshi

Report · Sep 28, 2021

Yes, this happens only when opening files from a network drive.

Yes, this issue occure with all PDF files.

I use Windows 10 Home 20H2.

Report · Oct 25, 2021

Hi,

Same problem here since few weeks.

Special character in user name too.

Only append with pdf open from network storage.

Desinstall and reinstall not solving the problem.

Adobe Acrobat Pro DC version 2021.007.20099

Please find a solution, it's really annoying to take 1 hour at the end of the day to delete all the debug.log created by this bug...

Report · Mar 13, 2022

This issue occurred while Acrobat attemped to use local drive as a cache location when you tried to open a network file.
The default cache_path is under the username and it can not be created if the username contains special characters.
There may be some workarounds:
1) In Windows Settings/Region/Administrative/Language for non-Unicode programs/Change system locale..., check to use "Beta: Unicode UTF-8 for worldwide language support". It will use codepage 65001.
2) Login Windows with a username without any special character.
3) Wait for Adobe to offer a setting to assign cache_path to a different path without any special character.

Report · Oct 06, 2021

Hello,

I've exactly the same problem.

Can you tell me if you have found a solution?

I noticed that we have "unknown characters" with the "?" in the path C:\Users\???

Thank you everybody!

Report · Oct 06, 2021

Hi,

Unfortunately, I haven't found a solution yet.

Report · Oct 20, 2021

Hi,

I had the same issue.

I have uninstalled Adobe reader dc and reinstalled from the website.

Problem solved for the end user.

Also my user had a special character in the username, namely é

Regards,

Peter

Report · Oct 21, 2021

I have the same issue since several weeks. I have also a special character in the user name, but re-installing Adode Acrobat DC did not help. Our network storage is quasi floated by "debug.log" files, because I need to open many PDF files per day on our network storage. The content is always the same:

[1021/093942.227:ERROR:context.cc(150)] The cache_path directory (C:\Users\R�der\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat\Cache) could not be created.
[1021/093942.229:ERROR:context.cc(165)] The cache_path is invalid. Defaulting to in-memory storage.

Moreover, it is not always possible to delete that log file until I restart my computer. That's very annoying and disturbs the workflow. And to be honest, such a bug is not acceptable for daily used software which is monthly paid.

By the way, that's the second time this bug happens. It was solved a log time ago, but came back in September.

Is there any solution in work, or any work-around to fix it temporary?

Report · Oct 22, 2021

I found a workaround by myself: at the very first, just open one arbitary PDF file in Acrobat DC which is locally stored on your computer, and keep it open in the background all the day. Then you can continue as usual with network stored files without having the "debug.log" file issue anymore. This works fine until you close the last local PDF file in Acrobat DC.

Anyway, I think, this workaround is not very user-friendly and the bug should be fixed by Adobe anyway and as soon as possible.

Report · Nov 04, 2021

The issue still exists, which is very annoying.

Will it ever be fixed?

Report · Nov 08, 2021

Dear Adobe Team,

Problem is existing for more than a month and there is no update or information about that will be fixed with next release.

Feedback please...

Report · Nov 18, 2021

Dear Adobe Team,

the problem still exists and there is still no update! Even no message that there is somebody working on it. Please fix it as soon as possible, or give at leats some feedback how you plan to continue on this matter.

Thanks.

Report · Dec 26, 2021

What a wonderful support!

No update no answer...

Report · Jan 02, 2022

@Meenakshi Negi

Why are not you giving any feedback!?

Report · Jan 11, 2022

Problem is still ongoing (21.011.20039) in other way.

Previous version was creating debug.txt when you open PDF in server.

(21.011.20039) is creating debug.txt when you edit PDF instead of open.

Report · Jan 11, 2022

Debug text is below:

[0111/142231.003:ERROR:context.cc(150)] The cache_path directory (C:\Users\XXX\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat\Cache) could not be created.
[0111/142231.019:ERROR:context.cc(165)] The cache_path is invalid. Defaulting to in-memory storage.

Report · Jan 11, 2022

Unfortunately, problem is existing regardless open or edit file.

Report · Mar 08, 2022

The problem is existing with version 22.001.20085 dated 07 March 2022.

Why isnt this problem being solved for 6 months?

Report · Mar 08, 2022

It is so crazy that a full paid software do not get any support an such a serious issue. I just found another workaround which solves the matter permanently. So for all people with special chars in their names, just create the path manually which the debug.log file is requesting. So if the debug.log file shows

The cache_path directory (C:\Users\R�der\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat\Cache) could not be created.

then just create exactly that path manually, including all black question marks in the user name, and give it full access to "everyone". It works fine for me.

Report · Mar 08, 2022

Hi Patrick,

Thank you for your fixing solution, it works for me well.

And Dear Adobe Team, now you know how you can fix it in next version, atleast do your job!

Report · May 24, 2022

Thank you @patrickr69834338 for your solution it works for me too, the debog.log file doesn't appear anymore.

But my main problem with that is the fact that Adobe Reader was completely shutting down... and making appear this debug.log file.

Now I don't have this file anymore, but Adobe Reader is still not working, it's impossible for me to read pdf, it's shutting down after a few seconds. I've tried to uninstall/re-install completely the software but it still doesn't work.

Will one day the Adobe Team react to this topic?.........

Report · May 24, 2022

I think the solution only works for Adobe Acrobat Pro DC at the moment. I haven't tested it with Acrobat Reader. It's just a workaround and not a final solution. I am also still waiting for the Adobe Team to fix the problem finally. Until then, you might want to open your PDF files only in Adobe Acrobat Pro DC (if you are not absolutely dependent on Acrobat Reader).

Report · May 24, 2022

Yes sorry, my bad, I'm using Adobe Acrobat DC also, and your tip is working for the debug file 🙂

But the Software doesn't work since a few weeks.

That's why I am so dissapointed, I'm paying for the full Adobe Creative Cloud Suite and it's impossible for me to open pdf's.

Report · May 24, 2022

Never mind. 😉 I don't have any similar issue with Adobe Acrobat DC like you. Have you tried to disable the workaround? You can do this by just renaming the fake folder in C:\Users\ to something else, e. g. appending ".bak" to the name.

By the way, I just updated to the latest version of Adobe Acrobat Pro DC, and it seems that the workaround is not needed anymore. Now it works fine without the fake folder in C:\Users\, and no debug file appears anymore. Please check if you have really the latest version of Acrobat which is 2022.001.20117 for me.