Automation error Exception occurred

[welchs101]

Hi,

I got this error the other day. It was not on my computer but a friends computer. THey got this error when they try to run a macro. If i run the macro i do NOT get the error.

I have NO idea why this is happening.

Another interesting thing is that if my friend goes to developer menu then visual basic and presses the Run , and Run Macro........macro actually runs to completion.

I have googled this but to be honest i am lost........any ideas would be greatly appreciated.

FYI: i can not post the code.

[jolivanes]

Re: "i can not post the code."
Begs the question "Why not"

[welchs101]

Any thoughts on what to do? What could cause this?

[Artik]

If I tell you that something hurts me, are you able to tell what hurts me? I don't think so. Without analyzing the code, you can't answer that question.

Artik

[jolivanes]

Re: "Any thoughts on what to do?"
Yes, inspect the code.

[welchs101]

ok, while i was hoping for something more let me ask another question.

are any of you aware of what type of an error would/could cause such an error like "Automation error Exception Occurred". Is there a general thing to consider?

[Marc L]

Any thoughts on what to do? What could cause this?

Hi,

obviously just a bad code …

[welchs101]

Just wanted to provide an update on this issue.

Turns out that if macro is run from "hard-drive" it runs fine no issues.

But if it runs from one-drive then one gets the error i mentioned.

I had a few others run from one drive and they had no problems. So it seems like this issue is

isolated to one computer. As long as it runs from physical hard drive on lap top then it runs ok.


Any thoughts on this one?

[Artik]

This is not a forum for fairies. We're not going to guess what you have in code that you haven't even shown one line of.

Regarding OneDrive, take a look at this thread: https://www.mrexcel.com/board/thread.../#post-6124378

Artik

[welchs101]

i have stayed away from childish remarks, i only wish the people here would do the same. 

I have posted valid questions only to be met with immature childish comments, how rude indeed.

Even if the code was posted it would do not good. The error does not occur at the same place every time.

if you have never seen this error before i wish you would just say that instead of calling people fairies or whatever else.

If you have no idea what could cause this type of error i wish you would just say that.

[Marc L]

As any guessing challenge has no place whatever the Excel VBA forum !

So just debug your code in step-by-step mode in order to see where it fails …
You may search on web too according to the environment.

[Artik]

I have posted valid questions only to be met with immature childish comments, how rude indeed.

I answered you that such a described problem can not be answered without analyzing the code. The error message is as generic as "Oops, something went wrong". Your first post could point to 100,000 causes. Your post #8 narrows that number down to 10,000. Without knowing any context of how the code works, it is still impossible to answer fairly accurately about the causes of the error.
Have I seen such an error in the past? Over the course of more than 15 years I've watched it many times, so I know what I'm saying about the impossibility of answering.

Even if the code was posted it would do not good. The error does not occur at the same place every time.

And here you may be wrong. By analyzing the code and knowing where (or which places) the error occurs, perhaps one could point to a solution. But since your project is secret and you can't share even a piece of code, the error problem will still remain yours.
I wish you good luck.

Artik

[jolivanes]

Re: "Even if the code was posted it would do not good"
I honestly can't comprehend why you ask for help because you seem to know it all.
If nothing else, your crystal ball is a lot better then ours.

[6StringJazzer]

welchs101, when you post a question about an error raised by VBA code it is helpful to have the file. If the file cannot be provided for any reason, it is absolutely essential to have the code. Without the code and without knowing what line raised the error, we have no way to even guess what could be causing your problem. This is a very general kind of an error. Even if the error occurs in different places, it is important to know the details. If all you want is a general "These are the possible causes of an automation error" it would be more productive to do a general web search. Asking a question in this forum is better for specific, targeted questions.

To all others posting in this thread

I appreciate the desire to have more information from the OP. If you are not getting what you feel you need to offer a solution, you can simply move on to the next thread. There is no need for sarcastic comments. The following type of comment is not appropriate and repeated occurrences will result in infractions.

Re: "Any thoughts on what to do?"
Yes, inspect the code.

obviously just a bad code …

This is not a forum for fairies.

[TMS]

I know some folk don't like to be advised to "just Google it" but sometimes it is the best way to generate some ideas and suggestions. In this case, it is a very generic error and you will find lots of possibilities and suggested solutions.

I apologise in advance if you have already done this. So, just Google: excel vba Automation error Exception Occurred

This will get pages of suggestions.

Do you get an error number? That could narrow down the options.

[TMS]

I'm not really an advocate of AI based answers but this looks like quite a practical diagnostic approach.

User
Cause of excel vba Automation error Exception Occurred?

ChatGPT
An "Automation error" in Excel VBA can occur for various reasons. It often indicates a problem with interacting with external objects or libraries. Common causes include:

Reference Issues: Check if any referenced libraries are missing or incompatible. Open the VBA editor, go to Tools > References, and ensure all selected references are available.
Version Compatibility: Ensure that your VBA code is compatible with the version of Excel you are using. Some code may not work across different Excel versions.
Object Creation Issues: If you're working with external objects (e.g., creating Word or Outlook objects), ensure that the corresponding applications are installed and accessible.
Security Settings: Excel's security settings might be blocking certain actions. Check macro security settings and ensure macros are enabled.
Memory Issues: Large data sets or inefficient code can cause memory-related problems. Optimize your code and check for memory leaks.
Corrupted Workbook: In rare cases, a corrupted workbook can lead to automation errors. Try creating a new workbook and copying your code to see if the issue persists.
Windows Update: Ensure that your Windows operating system and Excel are up to date with the latest updates.

Debugging using breakpoints and error handling can help pinpoint the issue. If the problem persists, providing more specific details about your code and the context of the error would be helpful for further assistance.



One other suggestion I saw was to add Option Explicit at the start of your code and compile it. Again, if you have already done this, we are guessing in the dark a little.

[Marc L]

To all others posting in this thread

I appreciate the desire to have more information from the OP. If you are not getting what you feel you need to offer a solution, you can simply move on to the next thread. There is no need for sarcastic comments. The following type of comment is not appropriate and repeated occurrences will result in infractions.

That's wrong as my so called 'comment' is very not sacarstic but just a fact according to the very poor initial post !
Did not you notice 'bad' in italic ?!
So the OP should obviously understand he must post his code like indicate which codeline raises the error …
Without any material, this is a guessing challenge which has no place whatever the Excel forum,
he has more chances to find out himself with a web search.

[6StringJazzer]

That's wrong as my so called 'comment' is very not sacarstic but just a fact according to the very poor initial post !
Did not you notice 'bad' in italic ?!]

It's obvious that if the code doesn't work, there is a problem with the code. We don't need to be told the problem is "bad code."

There is no need to post in this thread unless you are going to offer a solution, offer troubleshooting steps, or ask questions. Posting only to say that the initial post is poor is not helpful.

I am not going to entertain any further discussion about this. Any posts that don't move the thread towards a solution in a supportive way will be deleted.