Corrupt .nsf file

HelloMy archive file (which contains all my old emails) shows the following message when i try to acess it “Database is corrupt – cannot allocate space”.

Is there anyway i can try and recover this?

Many thanks

Ranjit

Subject: Corrupt .nsf file

Run fixup. If that doesn’t work, try to create a new copy or replica of it.

Subject: RE: Corrupt .nsf file

The best way to do it is to rename the file then force a replication from a known good server.

If it is not too corrupted you can do an updall -r and it will rebuild the indexes.

Try running nfixup.exe against it. If that doesn’t work, try ncompact -c against it.

Note: ncompact exists in all workstation installs. nfixup is not part of the client — you can copy it off a server that runs at a similar NBotes version.

Make sure to use the -c option with compact (ncompact -c whatever\your\file.nsf)

Subject: RE: Corrupt .nsf file

what is fixup?

tried creating a new copy, still did not work. also tried opening a new copy on another machine. that did not work either.

Subject: RE: Corrupt .nsf file

Fixup is a program that does what the name would seem to indicate – it tries to repair corrupted Notes databases. On Windows, the program is “nfixup.exe” (in your Notes program directory). You can run it from Start->Run or from the C:> prompt. From Run, the syntax would be something like this:

“C:\Program Files\lotus\notes\nfixup.exe” database.nsf

if the database is in your Notes data directory, or like this:

“C:\Program Files\lotus\notes\nfixup.exe” archive\database.nsf

if the database is in data\archive.

Subject: RE: Corrupt .nsf file

many thanks for that. i was able to do that but got the following messages:

****DbMarkCorruptAgain (Both SB copies are corrupt), DB=C:\Lotus\Notes\Data\archive.nsf TID=[0D0C:002-01E0] File=dbsuper.c Line=398 ***

Unable to fixup database C:\Lotus\Notes\Data\archive.nsf : Database is corrupt – Cannot allocate space

Subject: RE: Corrupt .nsf file

Well, sometimes toast is toast – there’s no way to turn it back into fresh bread. Local databases are more prone to accumulating damage that might make them unfixable because they don’t have scheduled maintenance tasks (compact, updall) running against them regularly the way server-based databases usually do.

Subject: RE: Corrupt .nsf file

damnation!thanks anyway…

i guess its lost forever then…