Mail file upgrade failed

We are rolling out the 8.0.2 upgrade to about 1000 off-site users. So far, we have one user experiencing a problem. During the upgrade, and now when he launches the 8.0.2. Notes client, he receives an error: Mail file upgrade failed

I (the Admin) am also receiving an E-Mail notification of the error:

Subject: Mail file upgrade failed for: Username

Body: Please check your local log database for the cause of the failure.

I don’t have access to the local log database, and nothing appears on the server log.

I have verified the user has Manager ACL rights. I have manually converted and refreshed the mail file design on the server.

The error continues to appear.

Has anyone experienced and resolved this issue ?

david r noble

Subject: Can you post error from user’s local log?

Have the end user send you their log so you can find the error listed there. Without knowing that, it’s hard to say what the problem might be.

Subject: Did you find a solution to this?

Hi

I am gettign the same error message.

The only thinsg in the log I can see are…

01/13/2009 01:53:24 AM Dynamic Client Configuration updating policy information

01/13/2009 01:53:24 AM Dynamic Client Configuration: Returned an error adding policy information to the address book: Note item not found

and also

01/12/2009 03:26:58 PM WEB(4): Initializing

01/12/2009 03:35:43 PM Unable to write to database - database c:\Documents and Settings\damopus\Local Settings\Application Data\Lotus\Notes\Data\Cache.NDK would exceed its disk quota of 10240 KB by 256 KB.

Any ideas?

Subject: Mail file upgrade failed

Hi I had the same problem after an upgrade from 6.5 to 8.5. For one user only. I couldn’t figure it out. Did all kinds of server commands, complete re-installation also did not work. Come to find this out on my own, that the user had 93 folders. That’s fine. However, one of the folders did not have a title. I asked permissions to remove the folder, after I moved the contents to another named folder. Attempted template replace and convert, and BAM! worked like a charm. Error is gone, and has not come back in over a week now.

Subject: Mike’s solution worked for me

Thanks for posting your solution, Mike. My user also had a folder with no name. After removing it the upgrade worked on the next attempt.