Avatar of KDLGates
Flag for United States of America asked on

"Database is corrupt, cannot allocate space" Error Logging in to Notes Locally

Assisting an employee who is receiving the error: "Database is corrupt, cannot allocate space" upon loading her copy of Notes - this immediately after entering her password.

We sent her a new .ID file, renamed the files bookmark.nsf, cache.ndk & desktop6.ndk to backup names, opened notes.ini and blanked out all lines after the first three ("[Notes] KitType=1 Directory=C:\Program Files\lotus\notes\data InstallType=2"), launched Notes and went through the Client Configuration Wizard. On the step of selecting her .ID file and entering her password, the error "Database is corrupt, cannot allocate space" reoccurred and Notes closed.

She had recently copied over her address book (filename names.nsf) but I do not know if there is any chance that this file is the "database is corrupt" database -- without the option of reinstalling Notes, how can I tell which database or file is the problem which is creating the "Database is corrupt, cannot allocate space" error?
Lotus IBM

Avatar of undefined
Last Comment

8/22/2022 - Mon
Felix Grushevsky

View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.

I agree with fgrushevsky, that this is the best approach.

If you can open log.nsf on another machine, you may get some more details.

I hope this helps !

Thanks guys. :) Appreciate the replies. Trying fgrushevsky's steps with user this morning. Will try nfixup on names & log . If this fails, will remove names & log, blank out .ini except for above 3 lines, run configuration wizard. If this is successful, will rename names.nsf to namesold.nsf, try nfixup on namesold.nsf and attempt to copy contacts.

nfixup failed on names.nsf - somehow this file was corrupted, but this still did the job (found what database was corrupt!). Renamed names.nsf to namesold.nsf & log.nsf to logold.nsf, re-ran configuration wizard, client was working fine. Opening namesold.nsf was still corrupt - lost user's Contacts but her Notes is working and she is manually recreating contacts. The client is working again, which is the end goal.

Thanks for the assistance. :)
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes