Automation Error

[Sandgroper48]

Operating system::    Windows 10Pro
Outlook version:     2019
Email type or host:    IMAP

---

Would appreciate any guidance on the following problem:

I have a macro to run all my Rules in Outlook 2019 (desktop Ver. 2408 Build 17928.20114) but it keeps going into error at
For Each rule in myRules
code in here ..............
NEXT

It goes into error at "Next" with an error message of "Automation error" -2146664191(800c8101) For loop not inialized"

I know the whole of the code is correct because it runs perfectly on my wife's PC with no errors. For that reason I haven't posted the whole code here because I that it runs without error on another PC. Both PC's are running Outlook 2019 (Ver. 2408 Build 17928.20114) under Windows 10Pro.

The error on my PC seems relate to any call to Next or Loop or iterative code such as For Each, For, with Next or Do While, Do Until with Loop because even a very simple procedure such as below also throws the same error at NEXT:

Sub Error_Test()
Dim st As Outlook.Store
Dim myRules As Outlook.Rules
Dim rl As Outlook.Rule
Dim count As Integer
Dim i As Integer

' get default store (where rules live)
Set st = Application.Session.DefaultStore
' get rules
Set myRules = st.GetRules
i = myRules.count
' iterate all the rules
For Each rl In myRules
Debug.Print rl
Next error throws Here!
End Sub​

Again, this very simple code works perfectly on the other PC.

I have exhausted just about every possible solution I can find on the Internet with no actual solution found. I have also completely removed and re-installed Outlook 2019 (classic on my PC wih no change to the issue.
Now at the hair pulling stage!
Any assistance would be most welcome.

 

[Diane Poremsky]

Hmmm. it works here. Did you delete the Here line and retype it? I've had errors copying code - it seems a character is hidden at the end of the line that triggers the error.

How did you move it from the other computer? Pasting into an email can add the hidden characters but by text file or exported .bas should not cause problems.

 

[Sandgroper48]

Hmmm. it works here. Did you delete the Here line and retype it? I've had errors copying code - it seems a character is hidden at the end of the line that triggers the error.

How did you move it from the other computer? Pasting into an email can add the hidden characters but by text file or exported .bas should not cause problems.

Diane thanks for the response. I moved the code from my PC to my wife's using Export>Module as a .bas file then imported into Wife's PC as the same file. All code in the Module runs perfectly on my Wife's PC but only the Sub MoveTrash() will run on my PC because that code does not involve any calls to a Loop or Next. For your review I have attached the bas file here as a Txt because the site won't accept aa a .bas file.
Strangely, I have many Excel macros involving For or Do Loops on my PC and they all run without issue so the "Automation Error" seems to be confined to Outlook. That is the reason that I took the drastic step of uninstalling and re-installing Outlook on my PC but it hasn't fixed the problem.
Thanks again for your response.

 

[Diane Poremsky]

That works here too. Did you try renaming the OTM file and making a new one? It's at %appdata%\microsoft\outlook. close outlook, rename it then reopen outlook.

Actually, rather than import the bas, open the text file you uploaded - copy and paste the macro from it into the VBA editor.

 

[Sandgroper48]

Thanks again for your reply.
I have tried:-
- deleting OTM file totally them importing .bas file from Wife's PC - no change
- deleting OTM file again then copy and paste from the .txt file that I sent to you - no change
- deleting OTM file again then copied entire OTM file from Wife's PC to mine - no change
Comparing libarary references (Tools>References) bewteen the two PC's; they are exactly the same and comprise:
(1) Visual Basic for Applications
(2) Microsoft Outlook 16.0 Object Library
(3) OLE Automation
(4) Microsoft Office 16.0 Object Library
The only difference that I note between the two PC's is that my Wife's vb visual basic pane has the tree as:
- Project1(vbaProject.OTM)
- Microsoft Outlook Objects
- ThisOutllookSession
- Modules
- Module1
On my PC the "Microsoft Outlook Objects" is missing from the tree (no sure why that would be missing).

Also I have noted that my Outlook version is 64 bit whereas my Wife's PC has 32 bit version. Mine must have got the 64 bit version from my recent uninstall and reinstall whilst trying to fix this issue.
Baffled!

 

[Diane Poremsky]

64-bit is the default install - you need to select the 32 bit version if you need it to support older addins. I'm using 64 bit so its not that... and there is nothing in it that would use another object model, so the references are ok.

For the VB tree - it looks like this? Click the manilla folder icon above 'project1' to toggle the folders between the two views.

 

[Sandgroper48]

64-bit is the default install - you need to select the 32 bit version if you need it to support older addins. I'm using 64 bit so its not that... and there is nothing in it that would use another object model, so the references are ok.

For the VB tree - it looks like this? Click the manilla folder icon above 'project1' to toggle the folders between the two views.
View attachment 4270


View attachment 4271

Yes - my dumb! So mine does include the "Microsoft Outlook Objects". Thanks,

 

[Diane Poremsky]

Yes - my dumb! So mine does include the "Microsoft Outlook Objects". Thanks,

I won't tell you how long it took me to figure out how to get the folder version after deleting the VBA registry key.

 

[Sandgroper48]

SOLVED - Finally, I think I have found a solution to my baffling problem. After countless hours of problem solving I decided to create a new email Profile them added the VBA code to the new profile and the problematic macro now runs to the end without falling over at the "NEXT" line of code. I have tested it against two (2) manually created Rules and it runs without errors but haven't yet imported all my Rules (22) for a complete test. However, if it falls over once the old Rules are imported then at least I will know what is causing the error.
This issue can now be tagged as Solved - many thanks to those that responded with suggested fixes.

 

[Sandgroper48]

Further to last message. After importing my 22 x Rules the "Automation error" has returned. Deleting all imported Rules returns the code to a working state. Must be some unknown bug in one of my rules!
So now to start the process of re-creating all my Rules manually!

 

[Diane Poremsky]

I'm wondering if one rule is corrupt and causing it to error...

I don't think adding error handling will help since it does before it starts. Delete some of the rules or delete all and manually create a couple of rules and see if it works. (The account I tested it on has 5 rules.)

 

[Sandgroper48]

Yes thanks - Diane. See my prevoius post - I am currently in the labourius task of re-creating all 22 Rules manually as I am unsure of how I could identify the "culprit" rule.

 

[Diane Poremsky]

I would do it one of two ways - create rule, test macro.... or delete 1 rule, test macro.

I'd review the rules and look for non-alphanumeric characters in a rule and remove those first.