daplunk
November 9th, 2016, 01:51 AM
Hi Team,
Last couple of week's I've been banging my head against the proverbial wall.
I keep crashing Realm Works. Receiving the following error.
No element with matching id was found.
It causes Realm Works to crash out completely. (I have submitted numerous reports to LW). From my testing it happens when I attempt to save a snippet that contains the word 'Triboar'.
Now interestingly I had 2x articles earlier today called 'Triboar'. I renamed one 'Triboar - SKT' to reduce the duplication issues. Everything was working when I saved and synced.
Then I transitioned to my other PC. Synced up and boom, now I can't save 'Triboar'.
Now I know I can restore from backup. This this exact same issue happened to me last week (happened with the word 'leather'). It took me a good day to restore from backup only to have the same issue repeat a week later.
What sparks my interest is I seem to be getting around the same amount of work done in entering the module each time the crash happens. My database isn't small, 1.18GB, I'm guessing the larger it becomes the more that can go wrong.
Has anyone had this issue previously?
Original Bug Report: 108253_amvhrlfeihul55qa
Latest Bug Report: 108740_atfle419212t3nv6
I'll start uploading my backup file to the cloud. Gonna take a long time.
SOLUTION PROVIDED: Manage Tab > Rebuild Index :)
Last couple of week's I've been banging my head against the proverbial wall.
I keep crashing Realm Works. Receiving the following error.
No element with matching id was found.
It causes Realm Works to crash out completely. (I have submitted numerous reports to LW). From my testing it happens when I attempt to save a snippet that contains the word 'Triboar'.
Now interestingly I had 2x articles earlier today called 'Triboar'. I renamed one 'Triboar - SKT' to reduce the duplication issues. Everything was working when I saved and synced.
Then I transitioned to my other PC. Synced up and boom, now I can't save 'Triboar'.
Now I know I can restore from backup. This this exact same issue happened to me last week (happened with the word 'leather'). It took me a good day to restore from backup only to have the same issue repeat a week later.
What sparks my interest is I seem to be getting around the same amount of work done in entering the module each time the crash happens. My database isn't small, 1.18GB, I'm guessing the larger it becomes the more that can go wrong.
Has anyone had this issue previously?
Original Bug Report: 108253_amvhrlfeihul55qa
Latest Bug Report: 108740_atfle419212t3nv6
I'll start uploading my backup file to the cloud. Gonna take a long time.
SOLUTION PROVIDED: Manage Tab > Rebuild Index :)