• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Has anyone ever had a similar error...?

Shadowy_one

Well-known member
Hi!

I was working on one of my realms yesterday (AD&D 1st/2nd Ed. Greyhawk ;)) and stumbled across an error that I can't explain...

In one of my entries there was a word (acutally two " Dwarven Pantheon") that lead to the crash of Realm Works everytime I tried to link it automatically. I had no problems when linking it manually and to make sure that the error didn't have it's source in the entry I was linking to, I deleted it and created it again from scratch with the same result.

I was wondering if any of you have had a similar experience and how you fixed it?

Cheers,

Shadowy_one
 
Never ran into this, but are you using special characters or downloaded fantasy fonts? I use a lot of Dwarven names using Tolkien-based Khudzul with Cirth runes that I get from the Dwarrow Scholar site and I've not had any crashes from them.
 
I had exactly this issue the other day, in my case RW was trying to link to a document that had been deleted every time I included the term in any snippet. The fix was to go to the Manage tab and 'Rebuild Index' that cleared out what I assume was an index entry pointing to the non existent topic. After rebuilding the index it stopped crashing
 
This means there is still some special case that isn't being handled correctly by the name indexing and linking mechanism. When RW crashed, you were prompted to send us the crash report and should have been also asked to send us your database. I can only assume you haven't done that.

We NEED your database so that we can figure out what's gone wrong and get it fixed. There is playback data logged into the database that should make diagnosis possible. But we can't fix the problem without that data. :(

Please help us by getting that data to us. :)
 
Hi Rob,

I sent you the information using the client on the first crash. Didn't do so on the 2nd - 10th though. Will do so in Futur.
 
You only need to send one crash report. However, there's not much we can do with just a crash report for the name indexing engine. Did you also send us your database? If so, I haven't seen it personally, so I'll need to follow-up with others on this end. If you have NOT yet sent the database, please do so. As I mentioned above, I need that database to play back the log data and see if I can recreate the issue. That's the only way I'll be able to isolate and fix the problem. :)

Thanks!
 
Please open a support ticket and provide us with your database. You'll find instructions for both in this thread here: http://forums.wolflair.com/showthread.php?t=48663

You can also place your database into a Dropbox or other folder for public sharing and include the link within the support ticket.

We do NOT need the backups. Only your current database should be necessary.

Thanks!
 
Hi Rob,

just created the support ticket and send the URL to the DB along with it. If you have any problems accessing it. Please let me know.

Regards,

Shadowy_one
 
Rob, if I've done the index repair I assume the current DB won't have the error in any more? I sent you probably about 7 or 8 crash reports when I was struggling to work out what was causing the crash on mine but again didn't send a DB at the time. Is it worth sending my DB now as well or should I attempt to recreate the crashing error before doing so?
 
To repeat: There is playback data logged into the database that should make diagnosis possible.

So please send in your database, even if you've rebuilt the index. The playback log is still present, and I can probably reproduce the error, subject to some other caveats that come into play.

In the future, if you encounter a crash with the name index, please submit your database right away, before rebuilding it, for the maximum probability of my success in diagnosing and fixing the error. :)

Thanks!
 
Back
Top