Sqlite Error Solution Guide

[David819]

That's a pretty general response. When you try this, I understand the Sqlite error still shows up. The only thing I can suggest is to delete the cache.db, though I'm told this does not fully solve the issue. If the OP didn't solve it, I'm not sure what will exactly besides what I mentioned, perhaps other members who have contributed may have an idea.

That's still a pretty general comment though...so...sorry if I'm not too helpful.

ummm also i cant find where it says"run as administator box"

[Ad Bot]

[Trifax]

Look around it'll be there. If you can, post screenshots of the window just in case.

[SPooK]

To be very honest. I don't think this deserves a sticky. I'm not trying to be mean, I understand that you are trying to help members to the fullest of your ability. But in most cases I find that this does not solve the Sqlite error; and removing the cache.db will not solve the problem either. We just have to wait until Badspot releases v20 that will, hopefully, resolve this issue.

[Trifax]

Until that happens, this is the closest thing to a working solution. Even though it doesn't work 100% of the time, it works for most people. I agree to a certain extent, in that we can only wait until Badspot released a permanent fix, but until then I'm glad this solution is available to users at the top of the board.

I would expect it to be de-stickied when version 20 is released.

[SPooK]

Until that happens, this is the closest thing to a working solution. Even though it doesn't work 100% of the time, it works for most people. I agree to a certain extent, in that we can only wait until Badspot released a permanent fix, but until then I'm glad this solution is available to users at the top of the board.

I would expect it to be de-stickied when version 20 is released.

I couldn't agree more sir. :)

[Blaze0]

Mac OS X

• Macintosh HD > Applications > Blockland v19
• Locate the file "cache.db"
• Right-click this file
• Select the option "Get Info"
• At the bottom of the window that pops up, you should see a section for "Sharing & Permissions". Change the privileges for the name "everyone" to "Read & Write"
• Close this window, and start up Blockland. The issue should be repaired.

This doesn't fix it for me.

[SPooK]

This doesn't fix it for me.

That is what I meant.

[Trifax]

This doesn't fix it for me.

Even though it doesn't work 100% of the time, it works for most people. We can only wait until Badspot released a permanent fix.

[David819]

Look around it'll be there. If you can, post screenshots of the window just in case.

heres a screen shot trifax

[David819]

heres a screen shot trifax

oops sorry here's the screenshot

[SPooK]

oops sorry here's the screenshot

That sir is microscopic and nobody will ever be able to tell what it is.

[David819]

That sir is microscopic and nobody will ever be able to tell what it is.

here

[wicke]

I get the same error on Ubuntu Linux 10.10/11.04 (WINE 1.2.2) when I have disconnected from a server and I join another. Of course I can, as a workaround, restart Blockland every time I want to switch servers.

[Miga]

I get the same error on Ubuntu Linux 10.10/11.04 (WINE 1.2.2) when I have disconnected from a server and I join another. Of course I can, as a workaround, restart Blockland every time I want to switch servers.

Well, that is a Windows compatibility layer for Linux, so of course it's going to have issues like that. But, that's a good thing for Linux users to know if they want to play Blockland, I guess.

[Doomonkey]

For windows users, start Blockland with a Batch file containing this:

Code: [Select]

attrib C:\"Program Files"\Blockland -r /d /s
attrib C:\"Program Files"\Blockland\Add-Ons -r /d /s
attrib C:\"Program Files"\Blockland\Cache.db -r
start C:\"Program Files"\Blockland\Blockland.exe

Replace the directory with your directory.