I've seen this happen before. I believe there is a bug in the personal preferences code that kicks in if you go through your preferences tickboxes in a specific way the first time you use Notes. Basically the preferences are stored in the database in a "profile" document which is created the first time you go into preferences and click OK to save. It seems in this case that a bad, corrupted profile doc gets created and can't get resolved by subsequent saves of the preferences. In fact I think that when the error message occurs the save is aborted so you can't then make changes to your preferences! What I did to fix my problem was to write a small LotusScript agent which deleted the profile doc. Then I went back into ToolsPreferences and simply clicked "OK" straight away to generate a new clean profile doc. Then I went back in and set my preferences how I wanted which updated the profile doc. I haven't investigated the bug very far as the code is quite complicated. Agent code to delete profile doc would go something like this: Sub Initialize Dim session As notessession Dim db As notesdatabase Dim m_calprofile As notesdocument Set session = New notessession Set db = session.currentdatabase Set m_calprofile = db.GetProfileDocument("CalendarProfile") If Not (m_calprofile is Nothing) then Call m_calprofile.RemovePermanently(True) End If End Sub

I've seen this happen before. I believe there is a bug in the personal preferences code that kicks in if you go through your preferences tickboxes in a specific way the first time you use Notes. Basically the preferences are stored in the database in a "profile" document which is created the first time you go into preferences and click OK to save. It seems in this case that a bad, corrupted profile doc gets created and can't get resolved by subsequent saves of the preferences. In fact I think that when the error message occurs the save is aborted so you can't then make changes to your preferences! What I did to fix my problem was to write a small LotusScript agent which deleted the profile doc. Then I went back into ToolsPreferences and simply clicked "OK" straight away to generate a new clean profile doc. Then I went back in and set my preferences how I wanted which updated the profile doc. I haven't investigated the bug very far as the code is quite complicated. Agent code to delete profile doc would go something like this: Sub Initialize Dim session As notessession Dim db As notesdatabase Dim m_calprofile As notesdocument Set session = New notessession Set db = session.currentdatabase Set m_calprofile = db.GetProfileDocument("CalendarProfile") If Not (m_calprofile is Nothing) then Call m_calprofile.RemovePermanently(True) End If End Sub