New Participant

Answered

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

Forum|Forum|4 years ago
September 28, 2021
8 replies
22799 views

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

Correct answer patrickr69834338

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.

[

[Cosmo]Stranger

New Participant

In Windows Settings/Region/Administrative/Language for non-Unicode programs/Change system locale..., check to use "Beta: Unicode UTF-8 for worldwide language support"

S_S

Community Manager

Hi @[Cosmo]Stranger,

Hope you are doing well.

Thanks for writing in!

Another method here would be to recreate the cache location.

Open Command Prompt as Administrator:
- Press the Windows Key and type cmd.
- Right-click on "Command Prompt" in the search results and select Run as administrator.
Navigate to the Parent Directory:
- In Command Prompt, navigate to the directory where the folder is supposed to be created.
- Run the following command:
  
  cd C:\Users\XXX\AppData\LocalLow\Adobe\AcroCef\DC\Acrobat
  
  Replace XXX with a different name.
Create the Cache Folder:
- Use the mkdir (make directory) command to create the Cache folder:
  
  mkdir Cache
Check if the Folder Was Created:
- You can verify the folder was created by listing the directory’s contents:
  
  dir
Grant Permissions to the Folder:
- If you need to make sure that the folder has proper permissions, use the icacls command. This grants full control to the current user:
  
  icacls "Cache" /grant %username%:F
  
  This command gives your user full control (:F) over the Cache folder.

Hope this helps.

-Souvik

M

Martin Brose

New Participant

For me this was related with the following setting:

Edit - Prefernces - Security (Enhanced) - Create Protected Mode log file

After deactivating this setting, no debug.log was created on the network drive.

L

lee4120

New Participant

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?.........

P

patrickr69834338

Participating Frequently

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).

L

lee4120

New Participant

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.

P

patrickr69834338

Participating Frequently

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.

S

SS5CC1

Participating Frequently

What a wonderful support!

No update no answer...

S

SS5CC1

Participating Frequently

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.

Unfortunately, problem is existing regardless open or edit file.

P

patrickr69834338

Participating Frequently

The issue still exists, which is very annoying.

Will it ever be fixed?

S

SS5CC1

Participating Frequently

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...

P

patrickr69834338

Participating Frequently

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?

P

patrickr69834338

Participating Frequently

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.