Member
Join Date: Jul 2014
Location: Germany
Posts: 46
|
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 |
#1 |
Senior Member
Join Date: Dec 2014
Location: Twin Cities Area, MN, USA
Posts: 1,325
|
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.
RW Project: Dungeons & Dragons 5th edition homebrew world Other Tools: CampaignCartographer, Cityographer, Dungeonographer, Evernote |
#2 |
Senior Member
Join Date: Jan 2012
Posts: 122
|
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
|
#3 |
Member
Join Date: Mar 2015
Posts: 34
|
I've had similar, strange crashing problems due to bad links. I'll try re-indexing as well.
|
#4 |
Member
Join Date: Jul 2014
Location: Germany
Posts: 46
|
Thanks Destrin,
rebuilding the index seems to have done the trick. The errors gone. Cheers, Shadowy_one |
#5 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
|
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. |
#6 |
Member
Join Date: Jul 2014
Location: Germany
Posts: 46
|
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. |
#7 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
|
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! |
#8 |
Member
Join Date: Jul 2014
Location: Germany
Posts: 46
|
Hi Rob,
I guess I didn't send my DB. Where should I send it to? Should I also send my backups as well? |
#9 |
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 8,232
|
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! |
#10 |
|
|