Member
Join Date: Aug 2012
Posts: 46
|
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
|
#11 |
Senior Member
Lone Wolf Staff
Join Date: Jun 2011
Posts: 1,090
|
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. |
#12 |
Member
Join Date: Feb 2013
Posts: 62
|
Quote:
|
|
#13 |
Junior Member
Join Date: Apr 2013
Posts: 11
|
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?
|
#14 |
Senior Member
Lone Wolf Staff
Join Date: Jun 2011
Posts: 1,090
|
Quote:
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. |
|
#15 |
Junior Member
Join Date: Aug 2013
Location: San Diego
Posts: 16
|
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.
|
#16 |
Member
Join Date: Feb 2013
Posts: 62
|
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 by Daelda; December 31st, 2013 at 09:57 AM. |
#17 |
Ex-Staff
Lone Wolf Staff
Join Date: Feb 2013
Posts: 95
|
Quote:
|
|
#18 |
Senior Member
Lone Wolf Staff
Join Date: Jun 2011
Posts: 1,090
|
Quote:
|
|
#19 |
Member
Join Date: Aug 2012
Posts: 46
|
Am very surprised and greatful the tech support is working over the holiday season, fingers crossed its a simple fix.
|
#20 |
|
|