Periodically, and more often lately, when I'm in Opus 9, viewing a document such as a PDF file, I get a strange error message.
It just happened now, when I double clicked on a PDF file to open Acrobat reader, while at the same time the viewer pane was also active. When I closed the PDF document, I got an error message relating to an inability to access memory at some location, which as I recall was all zeroes. I should have done a screen capture of the window, but I neglected to do so.
The message box readily is dismissed.
There was a reference to a file named "docsvw32.exe" in this error message window. Googling this filename brought up several hits which seemed to indicate that this is a spyware file.
A search on my C: drive indicated that this file is in the "viewers" folder in the Opus files of the C:\Program Files for Opus.
Does anyone know what this is all about?
Is there a conflict between the Opus viewer, and my install of Acrobat Reader 9.1.1?
The error message re "docsvw32.exe" just happened again. I was viewing a PDF document on the viewer pane, and Acrobat reader was not open.
When I was through reading it, and went to change to focus in the file listing, the error message box came up again. This time I captured that window, and it has been added as a jpg attachment - see below.
I entered the path\filename into the filename field, and then clicked on "Add Attachment". I can only assume that it did get added, as I see no evidence of that jpg image.
"docsvw32.exe" is part of the Opus ActiveX plugin. It's not spyware, it's just listed in some "is it spyware?" pages (like most executables) which shhould all confirm it's not spyware. (If there's one which says otherwise let me know and I'll contact them.)
Are you using an old version of Adobe Reader? If so that's probably the cause of the error.
One of the benefits of docsvw32.exe is that when Adobe's awful code crashes it takes out a throw-away viewer process instead of taking out Opus itself.
I have upgraded to 9.1.1.8 from 9.1.1.7, and I will see if the problem still continues.
The problem does not of course for every PDF file. And, the problem has only been occurring in the past few months. This could indicate that a recent update (of Opus of Acrobat Reader) had some impact on this.
But I will remain alert and cognizant of what I do when viewing PDF files, to see if I can notice any pattern, when it occurs next time.
