Menu

#12 Crash on opening Office VBEditor

open
nobody
None
5
2022-03-03
2018-01-16
Jurgen
No

When WD is open and I try to open the VB Editor from an Office 2013/2016 app like Word or Excel my Offce app crashes. It happens on all my machines (incl VM, various win versions). Office 2010 works ok.

Discussion

  • xtal256

    xtal256 - 2018-01-22

    I cannot reproduce. I assume this is what you are referring to:
    vb_editor.png

    Are you on the latest version of WD (3.5.1)?
    Does Office crash immediately after you open the VB editor, or shortly after? Does it happen every time?

    Can you please get the crash dump and attach it here or email it to me. If it's too big we'll have to find a hosting service to upload it to.

     

    Last edit: xtal256 2018-01-22
  • Andrey Lyashchuk

    hi, xtal256
    1.Neither Window Detective nor any of the MS Office applications was launched

    1. First, run the Window Detective application
    2. Then run Excel in safe mode and create an empty workbook.
    3. Re-index windows in Window Detective by executing the "Refresh All Window" command or by pressing F5
    4. Everything works as expected
    5. Opening VBIDE in running Excel (it does not matter if the VBE window was closed after that)
    6. Re-index windows in Window Detective by executing the "Refresh All Window" command or by pressing F5
    7. MS Office Application crashed with message "Excel has stopped working". Closed this message.
    8. After updating windows in Window Detective, new error lines appeared in the log:
    04/27/2020 23:28:14 - Warning: The message 127 sent to window VbaWindow (0x00113308) has timed-out. wParam = 0, lParam = 0
    04/27/2020 23:28:15 - Warning: The message 127 sent to window VbaWindow (0x00113308) has timed-out. wParam = 1, lParam = 0
    04/27/2020 23:28:15 - Warning: The message 14 sent to window VbaWindow (0x00113308) has timed-out. wParam = 0, lParam = 0
    04/27/2020 23:28:16 - Warning: The message 127 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 0, lParam = 0
    04/27/2020 23:28:17 - Warning: The message 127 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 1, lParam = 0
    04/27/2020 23:28:17 - Warning: The message 14 sent to window ScrollBar (0x002C262C) has timed-out. wParam = 0, lParam = 0
    04/27/2020 23:28:18 - Warning: The message 127 sent to window ScrollBar (0x00077446) has timed-out. wParam = 0, lParam = 0
    04/27/2020 23:28:18 - Warning: The message 127 sent to window OfficePowerManagerWindow (0x003D6684) has timed-out. wParam = 0, lParam = 0
    
     

    Last edit: Andrey Lyashchuk 2020-04-27
  • ddk1

    ddk1 - 2022-03-03

    Just got exact same thing. If I have a normal Excel .xlsx file open and I start WD, all is fine. Then in Excel I try to open the VBIDE and Excel crashes.
    Alternatively, if I have a workbook with macros (.xlsm) open (VBIDE not open) and I start WD, Excel crashes.
    WD 3.5.1, Excel 365 desktop.

     

Log in to post a comment.

MongoDB Logo MongoDB