• 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

Database integrity issue.

D

Daelda

Well-known member
Realmworks was working fine. I then added about a dozen people (just names, I didn't get to their descriptions yet. I tried to open Realmworks on my laptop to sync it with the new changes on my desktop and upon launch I got the following error:

"Database integrity issue. Too many realm starting points defined. Please contact support for further assistance."

I went back to my desktop and got the same error upon launch. I can't even get into RealmWorks at this point. *sigh* Luckily we are on a holiday break from our game and won't be gaming again for another week. Hopefully this issue can be fixed by then.

Bug Report has been submitted.
 
I had something similar where it would crash Realm works after entering. I got an e-mail suggesting that I go to the manage tab and 'rebuild index'. This fixed my issue.

Hope this helps
 
Mmurphy said:
I had something similar where it would crash Realm works after entering. I got an e-mail suggesting that I go to the manage tab and 'rebuild index'. This fixed my issue.

Hope this helps
Click to expand...

Unfortunately, I never get past the initial splash screen to be able to rebuild my index. Thanks though.

I hope I don't lose my 800MB database. I've put a LOT of work into it. Most of that size is coming from maps and pdfs, but I also have a couple dozen persons entered in - some with backstories and other info.
 
Daelda said:
Unfortunately, I never get past the initial splash screen to be able to rebuild my index. Thanks though.

I hope I don't lose my 800MB database. I've put a LOT of work into it. Most of that size is coming from maps and pdfs, but I also have a couple dozen persons entered in - some with backstories and other info.
Click to expand...

I hope you don't loose your data either. Sorry I was not of any help, but I would not do anything drastic until LoneWolf gets a hold of you. They maybe able to save your data, otherwise, you can always restore the backup that was made when you upgraded to build 142.

Again, I would not restore to the previous backup until LoneWolf gets a hold of you
 
Mmurphy said:
I hope you don't loose your data either. Sorry I was not of any help, but I would not do anything drastic until LoneWolf gets a hold of you. They maybe able to save your data, otherwise, you can always restore the backup that was made when you upgraded to build 142.

Again, I would not restore to the previous backup until LoneWolf gets a hold of you
Click to expand...

Not doing anything drastic. I've already been contacted by LoneWolf and sent them my Database so they can give it a "look-see". Hopefully it will be fixed in the next few days. With any luck, my situation will allow them to prevent this from happening to someone else.
 
Problem fixed, thanks to prompt tech support. :) I am back up and running. I just love RealmWorks and the LWD staff! Can't wait for my game to start back up in the new year.:D
 
Having the same issues. It happened right after I 'Synced All' and then exited out of the program. Upon launching, I get the same error. Email my DB to Support and am awaiting a fix. Fingers crossed.
 
I appear to have spoken too soon. I followed the instructions I was given and that seemed to work, however, upon exiting the program and then restarting it again, I get the same error.
 
Fixed!?

Daelda said:
Problem fixed, thanks to prompt tech support. :) I am back up and running. I just love RealmWorks and the LWD staff! Can't wait for my game to start back up in the new year.:D
Click to expand...

I posted my similar issue mere minutes after you said your problem was fixed. What was the fix? Or do I just wait for the Support guys?

Thanks for any info.
 
Amaranth said:
I posted my similar issue mere minutes after you said your problem was fixed. What was the fix? Or do I just wait for the Support guys?

Thanks for any info.
Click to expand...

Given that mine was a very temporary fix...I'd wait for further tech support.
 
just tried to access after syncing when the 142 build came out and have the same error, bug report submitted. Fingers crossed they can fix/find the problem sooner rather than later :)
 
We suspect a part of what has happened is that you started with databases on two machines. You synced up on one machine and then you synced up on the other. Since neither had been synced before, we allowed the syncing of both to go through. This then caused two entry point topics that got created independently on the two computers to get synced to the server. It then causes the problem that occurs.

We probably should have spelled this out better, but the way we had wanted you to get Realm Works on a second computer would be to delete the database and bring everything down from the server or that you did a backup of the first computer AFTER the syncing and then did a restore on the second computer of that backup.

A lot of the errors are occurring because we didn't have starting point topics right from the beginning but added it after databases had been created and then we independently create it on each of the databases on the client after the fact.

We can sort this out for everyone, but it looks like we would have to delete some of the realm starting point topics that have been created which means if you customized the one that isn't hooked up any longer, you could loose those customizations.
 
davidp said:
We suspect a part of what has happened is that you started with databases on two machines. You synced up on one machine and then you synced up on the other. Since neither had been synced before, we allowed the syncing of both to go through. This then caused two entry point topics that got created independently on the two computers to get synced to the server. It then causes the problem that occurs.

We probably should have spelled this out better, but the way we had wanted you to get Realm Works on a second computer would be to delete the database and bring everything down from the server or that you did a backup of the first computer AFTER the syncing and then did a restore on the second computer of that backup.

A lot of the errors are occurring because we didn't have starting point topics right from the beginning but added it after databases had been created and then we independently create it on each of the databases on the client after the fact.

We can sort this out for everyone, but it looks like we would have to delete some of the realm starting point topics that have been created which means if you customized the one that isn't hooked up any longer, you could loose those customizations.
Click to expand...

Ah. I thought that the server would notice that the 2nd computer's database was out-of-date and would thus download the new database. I must have missed the instructions to delete the 2nd database first. Hopefully this won't take too long/be too much work on your part and I won't lose too much/any data. Thanks for everything you do - we appreciate it.
 
Initially I experienced this problem on one computer only. I only installed it onto a second machine after I received the error. Can you explain what I did wrong?
 
Amaranth said:
Initially I experienced this problem on one computer only. I only installed it onto a second machine after I received the error. Can you explain what I did wrong?
Click to expand...

This problem could also occur on a single computer if you go back and restore a backup from before having synced to the server. There may also be some other scenarios.

It is a side effect for how we evolved the realm starting point topics and shouldn't affect users starting with Realm Works for the first time today.

For those of you who have gotten this error, please make sure to open a support case so we can identify you individually.
 
Could you not find a way to let us delete or override our cloud data and resync? I think this is the core of my "sync Error 301" issue. I would rather not loose anything I have done since my original sync as I have done a lot of data entry. I would rather lose the cloud data and resync.
 
Would it be possible to take a recent backup.realm and rename it to master.realm - overwrite the current master.realm and resync? Then, delete the master.realm on the 2nd computer and sync? Would that possibly fix the problem, assuming the backup was created prior to the problem? Or would that just compound the problem?
 
Last edited:
malvernas said:
Could you not find a way to let us delete or override our cloud data and resync? I think this is the core of my "sync Error 301" issue. I would rather not loose anything I have done since my original sync as I have done a lot of data entry. I would rather lose the cloud data and resync.
Click to expand...

We plan to offer this option by the time v1.0 is released. Don't worry, we're not going to leave you stuck.
 
Daelda said:
Would it be possible to take a recent backup.realm and rename it to master.realm - overwrite the current master.realm and resync? Then, delete the master.realm on the 2nd computer and sync? Would that possibly fix the problem, assuming the backup was created prior to the problem? Or would that just compound the problem?
Click to expand...

This could compound the problem.
 
You must log in or register to reply here.
Back
Top