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)


 

Christo,

            I have retitled your post for both clarity and archive maintenance purposes.  I hope that someone will be able to assist in figuring this issue out.

            That being said, it has been asked that logs not be posted to the group, and I would ask you, and all members, to refrain from doing so in the future.  If an assistant needs a log or log segment, they will request it and it should be sent privately.  There are many times when NVDA logs can contain information that would be sensitive and that the end user would really not want to have out in public, and they'd have no way of knowing it's even there, and this is why we do not want public posting of full logs or log segments.  That, and there are mighty few members who have the expertise to interpret them, too.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

If you think that you can think about a thing, inextricably attached to something else, without thinking of the thing it is attached to, then you have a legal mind.

        ~ Thomas Reed Powell

 


Quentin Christensen
 

Hi Christo,

The error in the log appears to be to do with the mouse, although more context would be useful to help track down exactly what is going on there.  Could you get me a copy of your NVDA log to have a look at please, ideally at debug level?
Please send it attached to an email to info@....  Include a description of what you have done and what isn't working as it should (so I know what it's about in case I don't get to investigate today).

First of all, your NVDA key is either INSERT or CAPS LOCK, depending on how you have NVDA setup.  So, to set your log level:
1) Press NVDA+control+g to open the general settings
2) Press TAB until the focus is on 'Log level'
3) Press DOWN ARROW to get to 'Debug'
4) Press ENTER to close settings
5) Press NVDA+control+c to save settings.

To restart NVDA with add-ons disabled:
1) Press NVDA+Q
2) Down arrow to 'Restart with add-ons disabled'
3) Press ENTER

Next, recreate the issue - do whatever causes problems (or wait for the problem to recur in this case)

To get NVDA's log after that, there are several ways:

If NVDA is still running and usable:
1) Press NVDA+F1 to open the log viewer
2) Press CONTROL+A to select all.
3) Press CONTROL+C to copy.
4) Open your email and start a message to info@..., type a little about what you have done and what has happened in the body of the message, then leave a space and:
5) Press CONTROL+V to paste the copied log.

Instead of using the log viewer, or if NVDA has stopped and you needed to restart it or the computer:
1) Press WINDOWS+R to open Windows' Run dialog
2) Type %temp% and press ENTER (that's the percent sign, the letter t e m p and another percent sign).  Windows Explorer should open to the temporary folder.
3) Press TAB to move to the file list
4) Press N and move down to find up to three files:  nvda.log (the log file for the current or most recent NVDA session), nvda-old.log (the log from the previous session) and nvda-crash.dmp (a crash dump with more information created if NVDA itself crashes).
5) Depending on what email program you use, the steps will be different, but attach as many of those three files to an email to info@... as will be useful, and again in the body of the message describe a bit about what has happened.

On Wed, Nov 11, 2020 at 12:23 AM Christo Vorster <cvklaviere@...> wrote:

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)



--
Quentin Christensen
Training and Support Manager


Christo Vorster
 

Hi Brian

 

Thanks for the correction, I truly was not aware of that.

 

Thanks again

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: Tuesday, 10 November 2020 18:41
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Goes Silent When Working with Outlook 2016 - Where does the fault lie?

 

Christo,

            I have retitled your post for both clarity and archive maintenance purposes.  I hope that someone will be able to assist in figuring this issue out.

            That being said, it has been asked that logs not be posted to the group, and I would ask you, and all members, to refrain from doing so in the future.  If an assistant needs a log or log segment, they will request it and it should be sent privately.  There are many times when NVDA logs can contain information that would be sensitive and that the end user would really not want to have out in public, and they'd have no way of knowing it's even there, and this is why we do not want public posting of full logs or log segments.  That, and there are mighty few members who have the expertise to interpret them, too.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

If you think that you can think about a thing, inextricably attached to something else, without thinking of the thing it is attached to, then you have a legal mind.

        ~ Thomas Reed Powell