"Database is damaged and has been closed."

Hi all-
I'm running a 190MB database on FileMaker Server 8, shared by 6 end
users running FileMaker 9, and for the last three days it has crashed
once a day. Everyone gets the "you have been forcefully disconnected"
message, and the server log shows as an event "Database [database
name] is damaged and and has been closed." Event ID 618.
Reopening the file has worked every time. Everything appears to be
normal and there are no errors on startup. But needless to say, this
is quite worrisome. I obviously don't want to continue to back up a
file that is intrinsically damaged. I could run Recover, but I was
under the impression that the Recover utility was only for files that
couldn't be opened.
I can't find any mention of this problem or the error code in previous
messages, so I was wondering if anyone had encountered this before or
had any advice as to my next move.
Thank you all in advance,
Nathan

Re: "Database is damaged and has been closed."

Nathan,

I can't comment on the error. Perhaps someone else can. But I can comment on
the recover. Recover is ONLY meant to acces a database temporarily. To
rescue its data. Good practice developing involves keeping undamaged clones
of the files you distribute (or use). I know not very many people do this,
but it really is the only way. After recovering the file should be used only
for transferring its data into an undamaged clone. Although it may appear
that the recover has worked, you really can't tell. Any error might crop up
at any time again. Recover is NOT a damage-repair unit. Only a
recover-access unit.

Good luck and keep well.

"NScheffey" schreef in bericht
news:c3a45130-5441-459b-a26d-2385cb01734f@l6g2000prm.googleg roups.com...
> Hi all-
> I'm running a 190MB database on FileMaker Server 8, shared by 6 end
> users running FileMaker 9, and for the last three days it has crashed
> once a day. Everyone gets the "you have been forcefully disconnected"
> message, and the server log shows as an event "Database [database
> name] is damaged and and has been closed." Event ID 618.
> Reopening the file has worked every time. Everything appears to be
> normal and there are no errors on startup. But needless to say, this
> is quite worrisome. I obviously don't want to continue to back up a
> file that is intrinsically damaged. I could run Recover, but I was
> under the impression that the Recover utility was only for files that
> couldn't be opened.
> I can't find any mention of this problem or the error code in previous
> messages, so I was wondering if anyone had encountered this before or
> had any advice as to my next move.
> Thank you all in advance,
> Nathan

Re: "Database is damaged and has been closed."

NScheffey wrote:

> Hi all-
> I'm running a 190MB database on FileMaker Server 8, shared by 6 end
> users running FileMaker 9, and for the last three days it has crashed
> once a day. Everyone gets the "you have been forcefully disconnected"
> message, and the server log shows as an event "Database [database
> name] is damaged and and has been closed." Event ID 618.
> Reopening the file has worked every time. Everything appears to be
> normal and there are no errors on startup. But needless to say, this
> is quite worrisome. I obviously don't want to continue to back up a
> file that is intrinsically damaged. I could run Recover, but I was
> under the impression that the Recover utility was only for files that
> couldn't be opened.
> I can't find any mention of this problem or the error code in previous
> messages, so I was wondering if anyone had encountered this before or
> had any advice as to my next move.
> Thank you all in advance,

What OS is the network using?
Event ID 618 means "Encrypted Data Recovery Policy Changed" in Windows.

Re: "Database is damaged and has been closed."

Use of the recover command should be a last resort, including all the
issues that Ursus raises.

Try taking the file off the server (close the db on the server first and
make a backup) and open the file directly with FM9 on your local
machine. Then close it and put it back on the server. See if that helps.

If not, take it off the server again, open locally with FM9 and 'save
as' compacted. This can help, though it can also hurt if the file is
already truly corrupted.

The ultimate solution, though, is to grab an older backup from before
the problems started, and then import your current data into it and make
it live. That's what having good backups are for.




NScheffey wrote:
> Hi all-
> I'm running a 190MB database on FileMaker Server 8, shared by 6 end
> users running FileMaker 9, and for the last three days it has crashed
> once a day. Everyone gets the "you have been forcefully disconnected"
> message, and the server log shows as an event "Database [database
> name] is damaged and and has been closed." Event ID 618.
> Reopening the file has worked every time. Everything appears to be
> normal and there are no errors on startup. But needless to say, this
> is quite worrisome. I obviously don't want to continue to back up a
> file that is intrinsically damaged. I could run Recover, but I was
> under the impression that the Recover utility was only for files that
> couldn't be opened.
> I can't find any mention of this problem or the error code in previous
> messages, so I was wondering if anyone had encountered this before or
> had any advice as to my next move.
> Thank you all in advance,
> Nathan

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg
FM Professional Solutions, Inc. Los Angeles

FileMaker 8 Certified Developer
Member, FileMaker Business Alliance

Re: "Database is damaged and has been closed."

Thank you all for your help,
The OS the server is running on is Windows. I wonder what "Encrypted
Data Recovery Policy Changed" means, guess I'll have to do some
research. Also, I will try the save-as-compacted idea and see if that
helps. We do hourly backups, so I could go back to three days ago
before the first crash and import the new changes, but it's
frustrating not knowing what is causing this problem or how to prevent
it in the future.
Thanks again,
Nate

On Jan 7, 12:43 pm, Howard Schlossberg
wrote:
> Use of the recover command should be a last resort, including all the
> issues that Ursus raises.
>
> Try taking the file off the server (close the db on the server first and
> make a backup) and open the file directly with FM9 on your local
> machine. Then close it and put it back on the server. See if that helps.
>
> If not, take it off the server again, open locally with FM9 and 'save
> as' compacted. This can help, though it can also hurt if the file is
> already truly corrupted.
>
> The ultimate solution, though, is to grab an older backup from before
> the problems started, and then import your current data into it and make
> it live. That's what having good backups are for.
>
>
>
> NScheffey wrote:
> > Hi all-
> > I'm running a 190MB database on FileMaker Server 8, shared by 6 end
> > users running FileMaker 9, and for the last three days it has crashed
> > once a day. Everyone gets the "you have been forcefully disconnected"
> > message, and the server log shows as an event "Database [database
> > name] is damaged and and has been closed." Event ID 618.
> > Reopening the file has worked every time. Everything appears to be
> > normal and there are no errors on startup. But needless to say, this
> > is quite worrisome. I obviously don't want to continue to back up a
> > file that is intrinsically damaged. I could run Recover, but I was
> > under the impression that the Recover utility was only for files that
> > couldn't be opened.
> > I can't find any mention of this problem or the error code in previous
> > messages, so I was wondering if anyone had encountered this before or
> > had any advice as to my next move.
> > Thank you all in advance,
> > Nathan
>
> --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Howard Schlossberg
> FM Professional Solutions, Inc. Los Angeles
>
> FileMaker 8 Certified Developer
> Member, FileMaker Business Alliance

Re: "Database is damaged and has been closed."

I wouldn't put too much faith in the event #618 representing "encrypted
data...". The event code is generated by FM Server, not by WIndows.

Also, be sure you have upgraded Server to the latest version, which for
FMS 8.0 was v4.

If at all possible, I would upgrade your server to 9.0 (v2) since you
are using FM9 clients. Not absolutely necessary, but it will help
ensure against any indexing issues under certain circumstances.



NScheffey wrote:
> Thank you all for your help,
> The OS the server is running on is Windows. I wonder what "Encrypted
> Data Recovery Policy Changed" means, guess I'll have to do some
> research. Also, I will try the save-as-compacted idea and see if that
> helps. We do hourly backups, so I could go back to three days ago
> before the first crash and import the new changes, but it's
> frustrating not knowing what is causing this problem or how to prevent
> it in the future.
> Thanks again,
> Nate
>
> On Jan 7, 12:43 pm, Howard Schlossberg
> wrote:
>> Use of the recover command should be a last resort, including all the
>> issues that Ursus raises.
>>
>> Try taking the file off the server (close the db on the server first and
>> make a backup) and open the file directly with FM9 on your local
>> machine. Then close it and put it back on the server. See if that helps.
>>
>> If not, take it off the server again, open locally with FM9 and 'save
>> as' compacted. This can help, though it can also hurt if the file is
>> already truly corrupted.
>>
>> The ultimate solution, though, is to grab an older backup from before
>> the problems started, and then import your current data into it and make
>> it live. That's what having good backups are for.
>>
>>
>>
>> NScheffey wrote:
>>> Hi all-
>>> I'm running a 190MB database on FileMaker Server 8, shared by 6 end
>>> users running FileMaker 9, and for the last three days it has crashed
>>> once a day. Everyone gets the "you have been forcefully disconnected"
>>> message, and the server log shows as an event "Database [database
>>> name] is damaged and and has been closed." Event ID 618.
>>> Reopening the file has worked every time. Everything appears to be
>>> normal and there are no errors on startup. But needless to say, this
>>> is quite worrisome. I obviously don't want to continue to back up a
>>> file that is intrinsically damaged. I could run Recover, but I was
>>> under the impression that the Recover utility was only for files that
>>> couldn't be opened.
>>> I can't find any mention of this problem or the error code in previous
>>> messages, so I was wondering if anyone had encountered this before or
>>> had any advice as to my next move.
>>> Thank you all in advance,
>>> Nathan
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Howard Schlossberg
>> FM Professional Solutions, Inc. Los Angeles
>>
>> FileMaker 8 Certified Developer
>> Member, FileMaker Business Alliance
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Howard Schlossberg
FM Professional Solutions, Inc. Los Angeles

FileMaker 8 Certified Developer
Member, FileMaker Business Alliance