• 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

Realm Works 1.0.43 Now Available!

L

liz

Ex-Staff
A new release for Realm Works is now available! This update addresses a number of the issues that users came across following the major release earlier this week .

There are a variety of outstanding bug reports that we’re still working to get fixed. Our first priority has been issues with data corruption following the update earlier this week and users experiencing crashes at startup.

If you encounter any new issues following this update, please update your support ticket by sending a follow-up email or send us a new bug report. To see the full list of changes and enhancements, please take a look at the Release Notes available within the product.
 
Last edited:
Um.....

"An error occured while trying to rename a file in the destination directory:

MoveFile failed; code 183 Cannot create a file when that file already exists."

This is on Win 7 Ent. running Realm Works as Administrator.

Aborting removes the Realm Works .exe requiring a reinstall.
 
If you have multiple computers, here are the steps to follow. They are almost identical to the steps when you first applied the big upgrade.

1. Restore the backup on the computer where you FIRST did the upgrade to the earlier version. That's where the auto-created backup will reside.

2. Complete the upgrade on that computer, then sync up to the server, following the steps outlined in the release notes.

3. On all other computers, sync down the latest version from the server.

That's all there is to it. Once the first computer is restored and synced up to the server, the other computers are no different from any other time. Just grab the latest from the server, and you're good to go. :)
 
Kirsa said:
"An error occured while trying to rename a file in the destination directory:

MoveFile failed; code 183 Cannot create a file when that file already exists."

This is on Win 7 Ent. running Realm Works as Administrator.

Aborting removes the Realm Works .exe requiring a reinstall.
Click to expand...

That's quite surprising. It sounds like something is preventing your existing database file from being replaced. Since you're running Win 7 Enterprise, you're likely comfortable doing more technical operations stuff, so you can try manually performing the restore.

You already know the location of the backup database to use. Copy that file into the following location:
c:\Users\[username]\AppData\Roaming\LWD Technology, Inc\Realm Works
[Alternately: %USERPROFILE%\AppData\Roaming\LWD Technology, Inc\Realm Works]

When you copy the file, make sure to name it "master.realm", overwriting the current file that reside there. Once you copy the file, launch the latest version of Realm Works, and it should initiate the upgrade process on the old copy of the database.

Hope this helps! :)
 
On the fourth attempt it finally worked. The only thing I did differently was I unchecked the 'add a desktop icon' box. How is that for weird? Now to go try my Surface 3 ...
 
I did restore the backup (before 202). The I synced. But RW didn't ask me if I want to keep the local. Therefore I have the lasted version and probably the data corruption. After the update and the restore and the sync, I found my data as before the update but with the crashes I had before.

For your information, I had no problems when I put the 202 as I had no special text, Statblocs, Shadows, ...

But I always have regular crashes.

What should I do? Are these crash I have (for instance, doing a CTRL+T, then CTRL+G, then again a CTRL+T, then crash) linked with the versioon or linked with a corruption of my database?
 
Has the link on the website been updated? I just downloaded the update via the website and got the older version. Downloading through the programs installer is always problematic for me.

UPDATE: I got the download through the programs updater. I just took a long time (patience - not a virtue for me :)).
 
Last edited:
I was opening pages in my realm and checking for new links. After doing this for several pages it crashed when I opened a page and now I can't open that realm. I can open my other realms, but not that one. Every time I try I get a crash report. I don't know if it means something but it said the following:

startIndex cannot be larger than length of string.
Parameter name: startIndex

I did send the crash report as it instructed.
 
Well, we screwed up. I don't know how else to say it, so there it is. :(

It turns out that the restore process isn't behaving the way we thought it was. And our various pre-release tests inadvertently masked the problem, so it looked like it was all working correctly. :(

We are working on a fix right now for the restore process. Until we get this fix out, NONE of the fixes are being retained for any realms that were upgraded to build 201/202 and sync to the server. The correct fixes are being applied, but then the old (wrong) data is being pulled down from the server and overwriting those changes for a net no improvement.

Anyone who upgraded to build 203 and restored from a build 201/202 backup will need to repeat the process again with the forthcoming build 204. Sorry for the headaches on all of this. We're working through the weekend to fix this as quickly as possible.
 
So any work we are doing in Realmworks now will be lost with the new update that you are currently working on?

I have added about 30 topics today alone as I am trying to prep for a convention next weekend.. so I should stop?
 
If you had/have any issues with data corruption after build 201/202 and you want that data recovered, you'll need to revert to the backup again. So I'm guessing the answer to your question is "yes".
 
From a different thread:

99_little_bugs.png
 
rob said:
Well, we screwed up. I don't know how else to say it, so there it is. :(

It turns out that the restore process isn't behaving the way we thought it was. And our various pre-release tests inadvertently masked the problem, so it looked like it was all working correctly. :(

We are working on a fix right now for the restore process. Until we get this fix out, NONE of the fixes are being retained for any realms that were upgraded to build 201/202 and sync to the server. The correct fixes are being applied, but then the old (wrong) data is being pulled down from the server and overwriting those changes for a net no improvement.

Anyone who upgraded to build 203 and restored from a build 201/202 backup will need to repeat the process again with the forthcoming build 204. Sorry for the headaches on all of this. We're working through the weekend to fix this as quickly as possible.
Click to expand...

I do not have no problem with my kingdoms so far, except the shading problem in the tables, which is still put white background when you choose no color background. To fix the problem I'll have to restore the database Realm_Works_Upgrade_To_202_Backup again?
 
We have important news about this release. If you restored your backup following this release, please read this thread. If you have any questions about this information, please also ask them in that thread.
 
Galahan said:
I do not have no problem with my kingdoms so far, except the shading problem in the tables, which is still put white background when you choose no color background. To fix the problem I'll have to restore the database Realm_Works_Upgrade_To_202_Backup again?
Click to expand...

The shading problem was fixed and then sadly overwritten with build 203. So yes, you'll need to restore again once we get build 204 out. We're going to be testing it with clear heads on Sunday before releasing anything.
 
ruhar said:
I was opening pages in my realm and checking for new links. After doing this for several pages it crashed when I opened a page and now I can't open that realm. I can open my other realms, but not that one. Every time I try I get a crash report. I don't know if it means something but it said the following:

startIndex cannot be larger than length of string.
Parameter name: startIndex

I did send the crash report as it instructed.
Click to expand...

As long as you sent the crash report, we'll see it and investigate. I'm not sure what occurred based on the limited information provided here. The crash report will be very helpful in filling in the missing pieces. :)
 
You must log in or register to reply here.
Back
Top