1  |   Order by index

Aug 14, 2002, 3:30pm

Building Inspector: Unable to store changes! Check server for possible full
disk or write-protected file(s).

whats up with this??

Aug 14, 2002, 7:43pm

What world were you building in?
The error message means what it says. The objects you were building are
stored on a server somewhere...so that is obviously full.

Contact the world owner and pop him an e-mail about this. Of if your the
owner, don't bother e-mailing yourself, just clear some crapola off your
server and try again.
--
- Syntax -
http://www.swcity.net
http://forum.swcity.net

[View Quote]

Aug 14, 2002, 8:16pm

its hosted by haertfell....dunno how they spell it

[View Quote]

Aug 14, 2002, 11:03pm

I've gotten this error for strange reasons before. I don't remember the
exact problem or solution.

The error means exactly what it sounds like. For some reason the world
server could not save your changes to the object database. It could be more
than just the server simply being out of storage.

If it doesn't go away within a few minutes ( which I'm betting it will),
then you'll have to take it up with Insanity. G'luck.... Let us know what
you find out.

-Jeremy

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Jeremy Booker - Owner
JTech Web Systems
www.JTechWebSystems.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Therefore do not worry about tomorrow, for tomorrow will worry about
itself. Each day has enough trouble of its own." -Mathew 5-34
[View Quote]

Aug 15, 2002, 9:05am

This error happens when the world database became corrupt on the server (talking from well established experience)

Andras

[View Quote]

Aug 15, 2002, 5:43pm

Yes and the only way to fix it is to propdump the world, erase world, and
reload propdump. At least that is the only way I know of to fix it. And
this is also why one should keep backups as if the datbase is corrupted
enough so that it won't do a propdump, then you are up a creek as they say.

-DB


[View Quote]

Aug 15, 2002, 9:56pm

Actually the situation is much worse if you have more than one worlds hosted on the same server software. You's best bet is to shut the world down, propdump with the enumerate option (-s), delete the cell and sector files and reload it. Even after this nice excercise you can't be sure another corruption won't come. Sometimes just simply adding a new world or proploading a world can corrupt another (properly working) one.
I found that the only clean-cut solution is to totally wipe out the database, recreate the worlds, prop-,at- and elevload it one by one :( The biggest lost so far was one object in one world in my experiences.

Andras

[View Quote]

Aug 15, 2002, 10:02pm

it has probably been fixed now, everything is still existing, thanks anyways
:)

[View Quote]

1  |   Order by index