New Participant

Question

Visual Basic Run-time Error 76 on Microsoft Word running on MacOs if I use Acrobat macros

Forum|Forum|6 years ago
January 1, 2020
5 replies
14442 views

Since the last upload of Acrobat Reader pro on my Mac, my Microsoft Word can't use the Acrobat macros anymore.

I receive this message if I try to use the Acrobat function on my last version of Word on MacOs (sign or create and share a PDF Adobe)

"Visual Basic Run-time Error 76 (Path Not Found) "

Crash or freeze

C

cardy_9401

New Participant

It is like the update might have changed or broken the file path the macro relies on. You could try reinstalling Acrobat or checking if the macro settings in Word need to be updated Carxstreetapk. Also, ensuring that Word and Acrobat have the necessary permissions in macOS System Settings might help.

Mentlintech

New Participant

Hey, if you looking for other tutorial you can check out this site:

https://www.mentlintech.com/

Daniel Chirillo

Participating Frequently

I have had the same issue for a long time. I finally figured out a realiable way to reproduce and at least workaround the problem (though the workaround sucks). Perhaps this scenario applies to you as well.

The Symptom: If any ancestory directory other than the immediate parent directory in the complete file path contains any non-Latin ASCII character (such as Š or Д), the Run-time Error 76 Path not Found error is thrown. For example,

1. If you create a PDF from a file with a path of /Users/Danny/Documents/Naš Jezik/Doc1.docx, it works fine: just the parent directory name contains a non-ASCII Latin character.

2. If you create a PDF from a file with a path of /Users/Danny/Documents/Naš Jezik/Test/Doc1.docx, the error is thrown: an ancestor directory name contains an non-ASCII Latin character.

The workaround for this symptom is to thus ensure that no ancestory directory names contain non-Latin ASCII characters.

E

Eli23909137skg7

New Participant

Your solution is exactly the issue for me as well. Adobe really needs to update its support for non-Latin characters in its director. I had the same issue until I took your advice. Another workaround that sucks is to upload the file to Google Drive, and then download it as a PDF. That works really well too, particularly for larger files.

E

Eli23909137skg7

New Participant

*Directory not director

ls_rbls

Community Expert

I think this link can share some additional insights:

https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/path-not-found-error-76

P

pierreb79608372Author

New Participant

I am sorry.

Thank you for your help but nothing worked.

May be with a corrective patch it will work again.

ls_rbls

Community Expert

You're welcome.

See if this helps:

https://support.office.microsoft.com/en-us/article/update-office-for-mac-automatically-bfd1e497-c24d-4754-92ab-910a4074d7c1?ui=en-US&rs=en-US&ad=US

Setting up the appropriate references in your macros:

https://answers.microsoft.com/en-us/msoffice/forum/all/problems-with-running-macros-on-office-for-mac/8d04f91e-a696-4f20-b67c-fe0b22276a0f

Registering a file:

https://apple.stackexchange.com/questions/94954/how-to-properly-register-a-file-extension-on-mac-so-it-will-also-work-by-running

How to update MS Office for MacOS automatically versus manually:

https://support.office.microsoft.com/en-us/article/update-office-for-mac-automatically-bfd1e497-c24d-4754-92ab-910a4074d7c1?ui=en-US&rs=en-US&ad=US

Update to the AutoUpdate package:

https://docs.microsoft.com/en-us/officeupdates/release-history-microsoft-autoupdate

https://docs.microsoft.com/en-us/officeupdates/update-history-office-2010-click-to-run

release notes for targeted 2019 office 365, addresses runtime error issue in excel fix

https://docs.microsoft.com/en-us/officeupdates/semi-annual-channel-targeted-2019

T

Test Screen Name

Brainiac

This doesn't sound like something that ever worked, especially with the free Reader. Did it used to work on the same Mac? Please show the code you are trying to run?

P

pierreb79608372Author

New Participant

It did perfectly work on the same Mac with the Acrobate pro version.

Until I upgrade Acrobat this morning ... 😞

T

Test Screen Name

Brainiac

You said it was Acrobat Reader in your first message. But I guess you meant Acrobat Pro. Ok, please show the code you are trying to run (Macro calls).

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded