Issues with "Playback error: Line 2 - Enumeration error...."

[debo]

Hi

I'm super new to this and I really appologise if this has been sorted out already or if it's a super basic question, but with that said I'm having issues with random errors / fails : "Playback error: Line 2 - Enumeration error: Macro edit detected. A macro cannot be edited during playback."

Now I haven't been able to figure out what happens or when and it's a tad bit random, but even my most basic macros have failed on occasion



And I have hyet to figure out what it thinks is / has been edited. 

Tried setting the pc to never sleep, and no other apps or anything running that might cause issues or wright to those folders. Tried mocing the "install" folder and the macro folder with no effect.

Trying to figure out what I'm doing wrong or what I'm missing / forgetting.

Can anyone help me out a tad? I've searched the forum and not really found anything that helps.

Cheers and thanks in advance!
D

[philranger]

Hi

It looks like you are trying to edit the macro while it is running

[debo]

Yeah, I inferred that from the error message, but the odd thing is I'm not touching it, no one is and as far as I can see the computer isn't doing anything special . I just load the macro and press play. As mentioned it also seems a tad random.  I've tried different paramteres and no mater what I do it fails (randomly, might run fine the first 3-4 times and then suddenly fails with that error)

[philranger]

Would there be a way to be sure that you are in the correct window when it clicks? Maybe using something like

1 | RUN ACTION | SELECT WINDOW BY NAME | New Tab - Mozilla Firefox

Ref: www.turnssoft.com/conditions.html#selectwindowbyname

[debo]

Hi

I'll give that shot, not sure that's the issue, but doesn't hurt to try at this point.

[Steve]

Hi debo

This error occurs when a running macro detects that the macro list has been edited during playback.

"Playback error: Line 2 - Enumeration error: Macro edit detected. A macro cannot be edited during playback."

The "Line 2" in your enumeration error tells us that this edit happened between line 1 and line 2 executing.  This error makes sense considering your macro is waiting 6 hours  'WAIT HOURS | 6'.  

Are you sure you didn't edit the macro sometime in the 6 hours after line 1 executed?

[debo]

Hi



100% sure I didn't edit it or touht as it's suppsoed to run at night I trigger it at 11 PM and it's supposed to wait for 6 hours before triggering a single action ( in this particualr case it's only a single action, it's actually supposed to do a whole set of actions and triggers, but I made it simple for troubleshooting sake). I've also set it to lower wait times and seen it fail while I'm not doing anything to it. It seems there is a chance for it to fail when the wait time is longer than hour, with that said it's very random.



What my screenshot doesn't show is that it actually completes the wait and than fails, regardless of the length of wait condition..



Note as mentioned this is random, I've had it run fine with conditions running from 1 hour to 12 hours, often multiple times, while at random it would fail with no rhyme or reason.


Ps your image link seems broken

[Steve]

Ok that is odd. I can't think of another way to get an error like this without clicking into the macro whilst it's running.
Maybe its something the macro is doing. Are you doing anything advanced or complicated with your macro? For example, are you calling multiple macro's at the same time or running any of MMM's remote control actions? Are you running MMM from within a VM, VNC, or remote desktop session? Is the MMM event log running during these long running macro's? The event log is great for troubleshooting macro's but not great for heavy condition based macro's running for a long time.

Your saying it occurs randomly too. That again is odd. Mini Mouse Macro takes a lot of queues from the local running environment. Would you say your local windows running environment is fairly consistent? Can you think of anything from the environment running, say any other software or bespoke windows tools, that could be getting in the way of MMM?

[debo]

Hi



Sorry for going quiet for so long, been busy with work these last few weeks.



I'd also like to thank both of you for taking the time to reply to my post and help me troubleshoot the issue.



@ Steve



There doesn't seem to be a clear pattern between the complexity of the macro and failure rate. At times a really complex and convoluted macro might work just fine a few times and then fail, while a really simple one (i.e. like the one I screenshotted, wait for X time and move mouse to XY and click)



I've been running it on a server and a vm (note the vm is running on a dedicated hyper -v host but is in many ways almost a clone of the aforementioned server)



I've also been running the MMM logging tool, but it only says the same thing, "Playback error: Line "x"- Enumeration error: Macro edit detected. A macro cannot be edited during playback" so it’s not super helpful in figuring out what might be interrupting the macro.



Additionally I've tried running them at different times of day, different scaling (CPU / mem/SSD combos) and even spun up a "cleaner cloned image" same issue.



It's boggling my mind that I can't figure this out. I have a bare-bones unit that connects to either the server or the host --> vm (RDP or via viewer), but I'm planning on getting a laptop to test this on. My current one died a little while ago, haven't gotten around to buying a new one.



In short, getting rather stuck ....

[Steve]

debo

Have you tried running MMM minimized? or with the 'Auto shrink on play' option enabled?
With MMM minimized there is no way this error can occur. The error only occurs when the macro list changes during playback by something, or someone, changing the list. This is usually a person unintentionally. If the macro is minimized during playback then we have a 0% chance of this being caused by a person....well unless you've got multiple people VNC'ing into your VM. It's just you that logs in right?

Running within a VM shouldn't cause this type of error but still it's something to keep in mind. I'd be keen to see if you get this error in and out of a VM.

[philranger]

On the first macro you screen captured you click at one place and release at a quite different place. Could that click be in the mmm editor, making it believe you want to edit the macro?

[debo]

@steve

I think I've tried it minimized, but I'll give it another shot or two. ( with the setting you mentioned)

And yes, only little old me logging on to the vm and the server.

philranger
I've considered that aswell , but when I re-play the macro(s) they don't get anywhere near the mmm window

[debo]

Hi



Just wanted to give you guys a little update.



None of the tricks worked and I've also taken the time to test the mmm + macro combo on a few other servers and laptops with far more consistency / success. Which leads me to believe there is something specific with that Image one image / server. The sad part is this image is in essence the golden image from which a part of our server park is based off, so leaves us a tad stuck.



With that said the app has worked much more consistently the last 5 days, which I'm attributing to the new mmm update. What it did to (for the most part) sort out the issue is beyond me. And it would be nice to know what was causing mmm to sense a macro change/ interference, just in case the issue keeps cropping up again.



It's been running for just over 5 days and only failed 1 time. The macro is triggered approx. 3 times a day, so failed only 1 out of 15, which obviously is a big improvement. Used to be closer to a 60/40 ( pass / fail)



What I'm getting at is , the issue seems "fixed", tough for the life of me I can't figure out what was the issue , nor can I find anything in the release notes that could have inadvertently fixed my issue.



I'd like to thank both of you for your suggestions and assistance





With some luck this is the end of the story, but please to chime in if you have an idea or two on what might have been the culprit. As of now it is running on our devtest server and will be deployed to the others later on, just a tad nervous it will fail again at the worst possible moment.



Cheers

D

[Steve]

Hi debo

One thing did catch my eye...

None of the tricks worked and I've also taken the time to test the mmm + macro combo on a few other servers and laptops with far more consistency / success. Which leads me to believe there is something specific with that Image one image / server. The sad part is this image is in essence the golden image from which a part of our server park is based off, so leaves us a tad stuck.

It might be something with the .NET framework version on that one image.  If its your golden image then yeah that would mean the problem would be replicated everywhere when MMM runs on that image base. 
Do you think it could be the versions of the .NET framework?  Are they different across the images you've tested with?  MMM is target at .NET 4.5.2 and built on a latest Windows 10 image.

[debo]

A very interesting theory.

Just checked the dot.net framework version on the golden image as well as one of the laptops I used to test on and it seems they have more or less the same version Framework 4.8.4.x.x ( slight variation between the laptop and servers, but as good as the same gen)

As far as I can tell no update has happend on the servers golden image for the last 30 days ( our logs don't go further back than that), so not sure if it got updated recently and I might have deplyed an updated version to our servers over the last few weeks.

We update the images approx 1-3 times every 2 months ( sec updates mostly) and than deploy the updated golden image as needed. The servers them selfs run on a system center controlled update schedule.