Does Opus Use Easyd.SystemService & Event ID 6969 - Line 34

I don't know for sure if Directory Opus is the cause for this Event ID & obscure module, Easyd.SystemService, but I vaguely traced the following information to it. Can someone verify if Opus is the cause for this?


Event 6969, Easy.SystemService

General:
The description for Event ID 6969 from source EasyD.SystemService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

The message resource is present but the message was not found in the message table

Log Name: Application
Source: EasyD.SystemService
Event ID: 6969
Level: Information
User: N/A
OpCode: Info
Logged: 7/20/20 10:20:20 AM
Task Category: None
Keywords: Classic
Computer: IENIUE

There's also a script error pop-up when I was booting. idk if that's related.

Script Error: 'An error has occurred in the script on this page'
Line: 634
Char: 1
Error: Object doesn't support property or method 'on'
Code: 0
URL: about:blank
Do you want to continue running scripts on this page?

I have never heard of EasyD.SystemService before.

What makes you think Opus is involved in that event? Why are you interested in the event? There's probably some key information missing here which might clarify what you're trying to solve.

The script error could be triggered by the viewer pane being asked to display a web page with that error on it, perhaps. But nothing in Opus itself should trigger that error otherwise. It looks like something coming from Internet Explorer (which the viewer pane can use for web content) when it runs a script that fails.

It could be from the viewer pane bc a mapped drive is online but Opus can't connect. I'm sure I caused that with some firewall & networking I'm doing. I also found relevant registry entries. The GUIDs are for ieproxy.dll & Windows.Storage.dll. Nothing on the Interwebs.

If you're just trying to track down the script error, I don't think the event log message is connected. That's coming from something Internet Explorer (or something using the "Trident" engine that IE is built on top of) is doing. IE doesn't log events when script errors occur.

The event log is full of things, many of them coming from the OS, which are best ignored, including lots of errors (not just informational things but errors with red icons that make you thinks something is wrong) which turn out to be completely "normal" if you go hunting for the causes of them. It's a place to look if you're troubleshooting, but I wouldn't worry about events that aren't relevant to the problem you're trying to solve, and definitely not if there isn't a problem and you're just trying to investigate things in the event log proactively. You'll go mad if you do that, from my own experience. :slight_smile:

Ha, so true. I have good event log software but no definite answer. The timeline showed gpupdate, syncing, and other ie, I can't remember or figure out how to get the script. The dialogue box is still open but can't trace it...didn't find it in ProcMon, procexp cmdline, Internet Options, and others? Do you how to get the source or code for this classic IE Script Error pop-up? Also, I'm going to edit/remove that hyperlink I posted. I don't see a reason to leave it up unless you think I should.

If the dialog box is still open, Process Explorer has a crosshair icon on its toolbar which you can drag over a window to find out which process owns the window. That might point to where it's coming from.

Although it may just be iexplorer.exe in which case the question which be what is running it. But the command-line might reveal the URL it's been asked to show in that case.

Is IE your default web browser? It might just be something opening a web page, and since IE is so outdated now the webpage is triggering an error when IE doesn't know how to run newer javascript code.

(It could even be Opus, since it can show the release notes after a new version is installed, although I think that is off by default these days, due to issues like this!)

Great, I found the source of the script with the crosshair target in procexp. It was a ccleaner update. There were failures when I was running the msi yesterday. I went into the strings on procexp and there's dozens of enteries for 'easy'. I'm sure this is the source of the Easyd.SystemService. The script must be embedded. I'd have to debug which isn't necessary. Thanks for all the help confirming its not opus.