Solved Lotus 123 v9.5 giving File is Corrupt when trying to save

Lotus Notes r5 software
April 26, 2015 at 11:39:38
Specs: Windows 64
One of our Lotus 1-2-3 v9.5 users running Windows 98 is getting a "File is Corrupt" error when trying to save to our network server running Windows 2000 Server. However, after the user gets that message and clicks "Ok" to get out of that dialog box, she can use the "Save As..." file option and save the file to her local hard drive. From there, she can move it back to the server. Things work, but in a very tedious process. At times, the user will not get the error, and it will save directly to the network server. The rest of the user's department doesn't seem to be having similar problems.

We did think that it could be a network problem, however, the user never has problems getting disconnected from our Novell Groupwise email server, or when accessing Excel, Word, Access, other files etc. It seems like Lotus is the only program that the machine is having trouble with.

Could it be that either something causes 123 to close it's network connection, 123 running on Win98 does not for some reason like the connection to the Win2k server? Can anyone suggest some sort of network/NIC analyzer software (prefer GNUish/Freeish, as this is only 1 client, so large expensive software packages are out of the question) that we could possibly use to see what's going on with the connection from the user's Win98 machine, to the Win2k server while accessing a Lotus 1-2-3 file? As I said before, strange thing is everything else seems to work, the user could leave an excel file open for 3 hours and still be able to save, but a lotus file that's open for 15 minutes won't save from hitting the save button or selecting file->save. If anyone has any other suggestions or questions, please let me know.


See More: Lotus 123 v9.5 giving File is Corrupt when trying to save

Report •

April 26, 2015 at 21:43:40
This is a shot in the dark but how long is the name of the spreadsheet file? If it isn't in the old 8.3 naming convention try saving it to the network with the 8.3 convention and see if that works.

Report •

April 27, 2015 at 02:41:58
✔ Best Answer
Try one of the suitable solutions:
(1) If possible, delete the damaged document.
(2) Execute fixup command to Repair Lotus Notes database.
(3) Make a new database replica and use it to replace the corrupted database. Since the corrupted document has not been replicated, this will be recreated when you will again perform the LEI activity.
(4) Use your previous good backup to restore the Notes database.
(5) Visit following thread http://itknowledgeexchange.techtarg... where you find more variants for recovering Lotus Notes files.

Report •
Related Solutions

Ask Question