Runtime error popup hiding in Mission Control - not accessible

%3CLINGO-SUB%20id%3D%22lingo-sub-2114549%22%20slang%3D%22en-US%22%3ERuntime%20error%20popup%20hiding%20in%20Mission%20Control%20-%20not%20accessible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2114549%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20running%20Excel%20and%20VBA%20on%20a%20Mac%20with%20a%20couple%20of%20screens.%26nbsp%3B%20If%20I%20receive%20any%20type%20of%20Runtime%20error%20popup%2C%20it%20does%20not%20appear%20on%20either%20of%20the%20screens%20as%20an%20overlay%20on%20my%20worksheet%20or%20VBE.%26nbsp%3B%20I%20can%20locate%20the%20runtime%20message%20by%20pressing%20the%20Mission%20control%20key%20F3%20and%20select%20the%20message%20by%20clicking%20the%20mouse%20on%20it%20or%20pressing%20space.%26nbsp%3B%20However%2C%20none%20of%20the%20buttons%20(End%2C%20Debug%20etc)%20are%20functional%20when%20clicking%20on%20them.%26nbsp%3B%20The%20box%20just%20minimises%20and%20I'm%20stuck%20on%20the%20error.%20How%20do%20I%20take%20control%20of%20the%20box%20and%20progress%20by%20acknowledging%20the%20error%3F%26nbsp%3B%20Esc%20doesn't%20work%20here%20either.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2114549%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExcel%20on%20Mac%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMacros%20and%20VBA%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2120311%22%20slang%3D%22en-US%22%3ERe%3A%20Runtime%20error%20popup%20hiding%20in%20Mission%20Control%20-%20not%20accessible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2120311%22%20slang%3D%22en-US%22%3EI%20am%20running%20into%20the%20exact%20same%20issue%20with%20MS%20Office%202019%20running%20on%20MacOS%20Catalina%20(10.15.7)%20MacBook%20Pro!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2131111%22%20slang%3D%22en-US%22%3ERe%3A%20Runtime%20error%20popup%20hiding%20in%20Mission%20Control%20-%20not%20accessible%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2131111%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI'm%20running%20Office%20365%20V16.47%20%26amp%3B%20Catalina%2010.15.6%3C%2FP%3E%3CP%3EI've%20narrowed%20down%20the%20scenario%20a%20little.%26nbsp%3B%20I%20have%20two%20monitors%20with%20one%20the%20Excel%20sheets%20and%20the%20other%20the%20VBE.%26nbsp%3B%20If%20I%20run%20a%20macro%20with%20a%20code%20error%20from%20the%20Excel%20directly%20(ie%20a%20shape%20with%20the%20macro%20assigned%20to%20it)%20the%20error%20debug%20popup%20appears%20on%20over%20the%20Excel%20sheet.%26nbsp%3B%20No%20problems%2C%20press%20debug%20and%20off%20we%20go%20correcting%20the%20code.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20I%20run%20the%20macro%20from%20the%20arrow%20in%20the%20VBE%2C%20the%20same%20error%20debug%20occurs%20but%20isn't%20visible%20on%20either%20of%20the%20monitors%2C%20behind%20either%20Excel%20or%20the%20VBE%20applications.%26nbsp%3B%20If%20F3%20(the%20Mission%20Control%20feature)%20is%20pressed%2C%20the%20error%20debug%20box%20appears%20where%20it%20can%20be%20selected%20as%20the%20active%20application%20(by%20mouse%20or%20spacebar)%20but%20then%20pressing%20on%20the%20debug%2F%20end%20etc%20buttons%20only%20exists%20out%20of%20Mission%20Control.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20called%20me%20back%20after%20they%20fast%20tracked%20the%20issue%20but%20I%20couldn't%20take%20their%20call%20at%20the%20time%20and%20asked%20them%20to%20call%20me%20back%20later.%26nbsp%3B%20Instead%2C%20they%20just%20closed%20the%20case.%26nbsp%3B%20Good%20stuff%20Microsoft.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESahobbi%2C%20can%20you%20try%20to%20emulate%20the%20above%20and%20tell%20me%20if%20the%20same%20scenario%20is%20tru%20for%20you%20too%2C%20please%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20going%20to%20get%20back%20to%20Microsoft%20as%20my%20feedback%20to%20reopen%20the%20case%20has%20fallen%20on%20a%20deaf%20ear.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F962302%22%20target%3D%22_blank%22%3E%40Sahobbi%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi 

I'm running Excel and VBA on a Mac with a couple of screens.  If I receive any type of Runtime error popup, it does not appear on either of the screens as an overlay on my worksheet or VBE.  I can locate the runtime message by pressing the Mission control key F3 and select the message by clicking the mouse on it or pressing space.  However, none of the buttons (End, Debug etc) are functional when clicking on them.  The box just minimises and I'm stuck on the error. How do I take control of the box and progress by acknowledging the error?  Esc doesn't work here either.

2 Replies
I am running into the exact same issue with MS Office 2019 running on MacOS Catalina (10.15.7) MacBook Pro!

Hi,

I'm running Office 365 V16.47 & Catalina 10.15.6

I've narrowed down the scenario a little.  I have two monitors with one the Excel sheets and the other the VBE.  If I run a macro with a code error from the Excel directly (ie a shape with the macro assigned to it) the error debug popup appears on over the Excel sheet.  No problems, press debug and off we go correcting the code.

 

If I run the macro from the arrow in the VBE, the same error debug occurs but isn't visible on either of the monitors, behind either Excel or the VBE applications.  If F3 (the Mission Control feature) is pressed, the error debug box appears where it can be selected as the active application (by mouse or spacebar) but then pressing on the debug/ end etc buttons only exists out of Mission Control.

 

Microsoft called me back after they fast tracked the issue but I couldn't take their call at the time and asked them to call me back later.  Instead, they just closed the case.  Good stuff Microsoft.

 

Sahobbi, can you try to emulate the above and tell me if the same scenario is tru for you too, please?

 

I'm going to get back to Microsoft as my feedback to reopen the case has fallen on a deaf ear.

@Sahobbi