Figured it out :)
Had to turn off the Add-in called "Acrobatexceladdin" and the errors stopped.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Everytime I create a new Excel document it opens with a Visual Basics for Applications Error Run-time error '1004': Method 'Name' of object 'AddIn' failed message.
I have to press End to close the error before I can start a worksheet.
This is new behavior in the last couple of days. I tried uninstalling and reinstalling Excel but the error still appears.
I am using Excel for Mac Version 16.89 (24090815)
MacOS Sonoma version 14.4.1
Any ideas on how to get the error to stop popping up whenever I create a new worksheet or open a saved worksheet?
Thanks
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Figured it out :)
Had to turn off the Add-in called "Acrobatexceladdin" and the errors stopped.
Figured it out :)
Had to turn off the Add-in called "Acrobatexceladdin" and the errors stopped.
Man, you are a genius! I loved that you were able to solve this without help. These kinds of errors are the ones that take a lot of time, and experts who have never experienced this issue will never understand. They’ll say things like: "First, make sure your computer is turned on.".
Anyway, you solved my problem. Thanks!
Likewise. This just started happening to me a couple of days ago. Turned that add-in off and the error is gone!
Figured it out :)
Had to turn off the Add-in called "Acrobatexceladdin" and the errors stopped.
Man, you are a genius! I loved that you were able to solve this without help. These kinds of errors are the ones that take a lot of time, and experts who have never experienced this issue will never understand. They’ll say things like: "First, make sure your computer is turned on.".
Anyway, you solved my problem. Thanks!
Likewise. This just started happening to me a couple of days ago. Turned that add-in off and the error is gone!
It did solve my problem instantly, truly genius John
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more