• 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 imports crashing

Yup, on 255. Error I get is "object reference not set to an instance of an object"

Note this is happening on 2 realms, game system one that's huge, and world one that's really small in comparison.

Been doing a bunch of testing since I posted. Created new realms with minor changes and imported fine. Seems my 2 big realms are somehow corrupt. One I can rebuild in a couple of hours. The other has over 2000 articles in it, no rebuilding that one... Literally months worth of work in it.
 
With the realm I first noticed the issue with I have no idea. Hasn't been touched in months.

However, part of the testing I did tested this.
Created a blank realm.
Created a new export of the affected realm with no changes.
Imported into the blank realm without issue.
Added a new topic to the source realm and exported. No other modifications.
Imported into the no longer blank realm, and got a crash.

These crashes happen whether I use overwrite settings or not.
 
Just had a couple of successful imports. Downgrade to build 253 did the trick.

Export files created with 253 worked without issue.

Export files created with 255 do not work, however an expected error due to version numbers rather than a crash.
 
Thorkull said:
Good info, just ran into this myself last night. I'll try downgrading when I get home. Has anyone tested with 254?
Click to expand...

254 has its own import/export bug (unsure if related to this) so I didn't try with it.

Side note, I did open a support case when this happened. Haven't had a resolution yet, but have gotten responses. You should open one as well (and anyone else with this) so they're aware it's not just me :)
 
I tried installing 253, uninstalling RW without removing the remaining Realm Works program data then installing 253, and uninstalling RW with full removal of the program data then installing 253. I keep getting the same error message:

"Your Realm Works database version is too new for this version of the Realm Works
software. This version of Realm Works cannot use this database and will exit.

"The build number for Realm Works you are attempting to run is 253. The database has been used with Realm Works with a build number of 254."

What did I do wrong or need to do?
 
I think that other people also deleted their local database, and synced their data back down from the cloud before installing version 253.

You would lose any local changes (that haven't already been synced) if you do this, however.
 
ruhar said:
I tried installing 253, uninstalling RW without removing the remaining Realm Works program data then installing 253, and uninstalling RW with full removal of the program data then installing 253. I keep getting the same error message:

"Your Realm Works database version is too new for this version of the Realm Works
software. This version of Realm Works cannot use this database and will exit.

"The build number for Realm Works you are attempting to run is 253. The database has been used with Realm Works with a build number of 254."

What did I do wrong or need to do?
Click to expand...

Farling said:
I think that other people also deleted their local database, and synced their data back down from the cloud before installing version 253.

You would lose any local changes (that haven't already been synced) if you do this, however.
Click to expand...

This. When I was doing my initial troubleshooting this was part of it before I even downgraded, so didn't think to mention earlier. Just make sure you sync first.
 
I renamed the folder inside the RW folder within AppData folder before installing 253 and it took care of the issue. Thanks guys.
 
I'm having the same error now.

This whole import-export thing is a huge nightmare! Wasn't 255 supposed to fix those errors?

Anyway, I take it that 253 is the version number to have? What's with the crashes 254 are supposed to fix? I just have to live with them as an inconvenience?
 
ppl should have tried hout the whole import export things when they still were in live development :(

Hope they still wake up from their hiatus. It's sad to see a nice idea slowly wither away...
 
Acenoid said:
ppl should have tried hout the whole import export things when they still were in live development :(

Hope they still wake up from their hiatus. It's sad to see a nice idea slowly wither away...
Click to expand...
People did, Josh, GTHiel and I reported plenty of import/export issues to LWD 2 years ago when we were all working on Nibirum.

I'm sure you know how much response we got.
 
Merion said:
I'm having the same error now.

This whole import-export thing is a huge nightmare! Wasn't 255 supposed to fix those errors?

Anyway, I take it that 253 is the version number to have? What's with the crashes 254 are supposed to fix? I just have to live with them as an inconvenience?
Click to expand...

Only issues I've had with 253 so far is the annoying there's an upgrade popup, and self-inflicted importing issues.
 
You must log in or register to reply here.
Back
Top