NVDA Goes Silent When Working with Outlook 2016 - Where does the fault lie?


Christo Vorster
 

Good day Group

 

From time to time I find that NVDA keeps quiet while I work in MS Outlook 2016. When I press ALT-Tab twice it start speaking again, but it only reads the message my cursor is on. I copied the view log, hopefully someone can tell me whether it is a NVDA or Microsoft problem.

 

The log look as follows:

 

INFO - __main__ (15:05:18.440) - MainThread (8168):

Starting NVDA version 2020.3

INFO - core.main (15:05:24.668) - MainThread (8168):

Config dir: C:\Users\Christo Vorster\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:05:24.668) - MainThread (8168):

Loading config: C:\Users\Christo Vorster\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:05:25.505) - MainThread (8168):

Using Windows version 10.0.19041 workstation

INFO - core.main (15:05:25.506) - MainThread (8168):

Using Python version 3.7.9 (tags/v3.7.9:13c94747c7, Aug 17 2020, 18:01:55) [MSC v.1900 32 bit (Intel)]

INFO - core.main (15:05:25.507) - MainThread (8168):

Using comtypes version 1.1.7

INFO - core.main (15:05:25.507) - MainThread (8168):

Using configobj version 5.1.0 with validate version 1.0.1

INFO - synthDriverHandler.setSynth (15:05:28.562) - MainThread (8168):

Loaded synthDriver ibmeci

INFO - core.main (15:05:29.097) - MainThread (8168):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:05:29.107) - MainThread (8168):

Braille input initialized

INFO - braille.initialize (15:05:29.109) - MainThread (8168):

Using liblouis version 3.14.0

INFO - braille.initialize (15:05:29.122) - MainThread (8168):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:05:29.167) - MainThread (8168):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:05:29.987) - MainThread (8168):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:05:30.056) - _UIAHandler.UIAHandler.MTAThread (8396):

UIAutomation: IUIAutomation6

ERROR - mouseHandler.initialize (15:05:35.596) - MainThread (8168):

Error retrieving initial mouse object

Traceback (most recent call last):

  File "mouseHandler.pyc", line 236, in initialize

  File "NVDAObjects\__init__.pyc", line 285, in objectFromPoint

  File "NVDAObjects\__init__.pyc", line 225, in findBestAPIClass

  File "NVDAObjects\__init__.pyc", line 224, in findBestAPIClass

  File "NVDAObjects\UIA\__init__.pyc", line 994, in kwargsFromSuper

  File "comtypesMonkeyPatches.pyc", line 26, in __call__

_ctypes.COMError: (-2147467259, 'Unspecified error', (None, None, None, 0, None))

INFO - core.main (15:05:35.876) - MainThread (8168):

NVDA initialized

ERROR - RPC process 12180 (nvda_slave.exe) (15:09:33.469) - Dummy-83 (7612):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 93, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1245, in GetActiveObject

  File "_ctypes/callproc.c", line 935, in GetResult

OSError: [WinError -2147221021] Operation unavailable

 

Regards

 

Christo Vorster (Worcester, South Africa)

Join nvda@nvda.groups.io to automatically receive all group messages.