View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000233 | Wake On LAN Ex | Backend / Core | public | 2018-11-10 11:05 | 2020-01-26 10:02 |
Reporter | AppFramework | Assigned To | BootBlock | ||
Priority | high | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 3.19 | ||||
Target Version | 3.20 | Fixed in Version | 3.20 | ||
Summary | 0000233: `Exception`: Object reference not set to an instance of an object. | ||||
Description | This report has been created by the AppFramework framework on which the Wake On Lan EX application has been built. APPLICATION INFORMATION
EXCEPTIONMESSAGE
SOURCE
TARGET SITE
STACKTRACE
APPFRAMEWORK INFORMATION
SYSTEM INFORMATION
ENVIRONMENT
USER COMMENTS
APPFRAMEWORK LOG
| ||||
Steps To Reproduce | While this may not be the steps required to reproduce the source of this particular error, it seemed to still reproduce the symptom.
| ||||
Tags | Exception | ||||
|
There seems to be an issue with the column editor; I've not encountered this error before, so a little bit of investigating will be required but at first glance, I can't think why something would be missing (eg. the column data itself, maybe?). |
|
I've managed to replicate the issue in that it's giving the same errors, but I'm not entirely sure if that's the way that this error actually occurred. As a workaround while fixing/releasing this problem, you could try deleting the Columns.jso that resides in %APPDATA%\WoLEX3. Then running WoLEX should hopefully work; it seems that the Columns.jso file got corrupted in some way and WoLEX is having a problem correctly interpreting its contents. |
|
The issue has now been fixed! If WoLEX encounters corrupted column data, it'll now just reset that data back to the defaults. It was originally doing this, but it wasn't quite rigorous enough in its detection. Wake On LAN Ex 3.20 should be released within the next few hours with this fix, and a couple of additional fixes to the error reporting as I've noticed some little formatting issues in this submission. |
|
Will mark this resolved once this has been confirmed to be fixed. |
|
Initial testing appears to show that the error is fixed on the client's machine. There are a few other error-checking changes I'd like to make which'll cause the next release to be available in the following few days (as opposed to same-day as the fix), it'll give a bit of time should the fix not actually be a 100% solution to the problem and so I don't release a "faux-fixed" release. If that makes sense. |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-11-10 11:05 | AppFramework | New Issue | |
2018-11-10 11:05 | AppFramework | Assigned To | => BootBlock |
2018-11-10 11:13 | BootBlock | Description Updated | |
2018-11-10 11:20 | BootBlock | Note Added: 0000004 | |
2018-11-10 11:33 | BootBlock | Note Added: 0000005 | |
2018-11-10 11:34 | BootBlock | Priority | normal => high |
2018-11-10 11:34 | BootBlock | Severity | minor => crash |
2018-11-10 11:34 | BootBlock | Reproducibility | have not tried => always |
2018-11-10 11:34 | BootBlock | Status | new => confirmed |
2018-11-10 11:34 | BootBlock | Product Version | => 3.19 |
2018-11-10 11:34 | BootBlock | Fixed in Version | => 3.20 |
2018-11-10 11:34 | BootBlock | Target Version | => 3.20 |
2018-11-10 11:35 | BootBlock | Tag Attached: Exception | |
2018-11-10 11:41 | BootBlock | Note Edited: 0000005 | |
2018-11-10 11:43 | BootBlock | Note Added: 0000006 | |
2018-11-10 11:44 | BootBlock | Status | confirmed => resolved |
2018-11-10 11:44 | BootBlock | Resolution | open => fixed |
2018-11-10 12:03 | BootBlock | Description Updated | |
2018-11-10 12:05 | BootBlock | Steps to Reproduce Updated | |
2018-11-10 12:05 | BootBlock | Steps to Reproduce Updated | |
2018-11-10 12:09 | BootBlock | Status | resolved => confirmed |
2018-11-10 12:09 | BootBlock | Resolution | fixed => open |
2018-11-10 12:09 | BootBlock | Note Added: 0000007 | |
2018-11-10 16:55 | BootBlock | Note Added: 0000008 | |
2018-11-10 16:55 | BootBlock | Status | confirmed => resolved |
2018-11-10 16:55 | BootBlock | Resolution | open => fixed |
2020-01-26 10:02 | BootBlock | Status | resolved => closed |