VBA memory errors on server freeze Word; we need to terminate process

[mattretzer]

In cases where VBA memory errors are hanging Word for a given file, that spawned instance of Word remains frozen until a human clicks on a Window on the GUI on the server.
This is not preventing other Word files from being processed, but it does prevent the rest of the Validator from finishing for that file, which keeps alert emails from getting sent (to the PM and ourselves) until the GUI window is clicked.

I think if we track the PID of the Word process, we should be able to terminate the spawned MS Word process for that one file via the process watcher script.

[ericawarren]

@mattretzer didn't you write a short powershell script for something similar at some point? I remember planning on creating a slack command for it (like /remote-deploy) but guess it fell off the radar, but that would probably be helpful, yes?

[mattretzer]

Yes, though that was to blanket-terminate the WinWord process.. I'm hoping if we have the PID for a particular instance of Word (the one that's hung), we can just terminate that instance? fingers crossed :)

…

On Wed, Apr 19, 2017 at 12:02 PM, Erica Warren ***@***.***> wrote: @mattretzer <https://github.com/mattretzer> didn't you write a short powershell script for something similar at some point? I remember planning on creating a slack command for it (like /remote-deploy) but guess it fell off the radar, but that would probably be helpful, yes? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#99 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGs0zvx_C9904oHUHchcRlF5eRBu22-sks5rxjAtgaJpZM4NBtKy> .

-- *Matt Retzer | *Developer, Publishing Tools | Macmillan 175 5th Avenue – 2nd Floor | New York, NY 10010 [email protected]

[MacmillanWorkflows]

➤ erica.warren commented:

Moving to less urgent because we may not need to run Word on the server anymore in the near future.