Strange problems with ODS 52 and calendar entries

22 July, 2014 06:12:29 AM Miguel Calvo  Domino9  |  Comentarios (2)

After upgrading/migrating a server in one of our customers from Linux 8.5.2 to Windows 2008 64bits 9.0.1FP1, we had some problems not discovered in the testing phase, where everything was smooth.

A user could create and schedule a calendar meeting entry, but was unable to cancel it. The problem happened both from iNotes and IBM Notes.

Image:Strange problems with ODS 52 and calendar entries

When selecting the action Owner options > Cancel in the calendar entry document, the user got a cryptic message "special database object cannot be located".

After further testing we were able to find more situations where we got the same errror message. The problem didn't happened in all mail databases, just randomly. The problem was suspected to be caused by a corrupted design, so we replaced it again and checked the desing elements with no luck.

The only difference with the original testing phase was that we had upgraded ODS to 52 in the final deployment.

The solution


After reverting the ODS to a previous one, ODS 48, all problems dissapeared. So, be careful with ODS 52, that could have undesired side effects.

Gravatar Image
1) Strange problems with ODS 52 and calendar entries
Lars Berntrop-Bos 07/22/2014 9:40:05 AM

Going back to an older ODS also means a copy-style compact happened => that may have fixed the problem as well...

Did you have a chance to recheck a database reverting the ODS to 52 again?

Was the error, when it occurred, always prsent, I mean was it randomly affecting som mail databases, but on those databases affected it occurred always?

Or did a known problem database display the problem only some of the time? (a real pain if problems are not consistently reproducible...)

Gravatar Image
2) Strange problems with ODS 52 and calendar entries
Miguel Angel Calvo 07/22/2014 12:04:50 PM

Hi Lars,

Before downgrading the ODS, we had made a compact -c with no luck. So, we didn't think of going back to ODS 52 after solving the problem.

In databases affected, a meeting with no invitees could be cancelled with no problem. We thought of a relation between the invitees databases and the problem, but I can not confirm that.

We didn't find a pattern.

Deja una respuesta


Nota:  (No HTML - Los enlaces serán convertidos si están precedidos por http://)

¿ Recuérdame?