IBM Support

LO80343: OUT OF OFFICE FORMATTING ERROR LOGGED BY TRAVELER

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • This error is logged to the console and Traveler error log:
    
    "Formatting error: Out of office date for user <user name> is
    not in the expected format."
    
    This indicates that there are malformed dates in the user's out
    of office profile document. To fix these dates, the user must
    open and save out of office from Notes.
    
    The Traveler client on Android devices will automatically
    retrieve out of office information from the server, even when
    the user is not trying to view or edit out of office. If
    malformed dates are found, the error will be logged. Some
    customers found this error annoying, since the user was not
    aware there was a problem, so a notes.ini parameter was added:
    
    NTS_OOO_LOG_FORMAT_ERROR (default: true)
    If set to false, the error mentioned above will be logged at an
    INFO level, instead of a SEVERE level, and will not appear on
    the console.
    

Local fix

  • Instruct the affected user to change out of office from Notes in
    order to correct the date fields in the out of office profile
    document.
    

Problem summary

  • If there is a malformed date in a user's out of office profile
    document, an error is logged to the console:
    
    "Formatting error: Out of office date for user <user name> is
    not in the expected format."
    
    Some users may find this error annoying
    

Problem conclusion

  • Notes Traveler Server was updated to provide a notes.ini
    parameter NTS_OOO_LOG_FORMAT_ERROR (default true). If set to
    false, the out of office error will be logged at an INFO level
    instead of SEVERE, and will not appear on the console.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LO80343

  • Reported component name

    LOTUS NOTES TRA

  • Reported component ID

    5724E6204

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-12

  • Closed date

    2014-07-21

  • Last modified date

    2014-07-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    LOTUS NOTES TRA

  • Fixed component ID

    5724E6204

Applicable component levels

  • R900 PSY

       UP

  • R901 PSY

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSYRPW","label":"Lotus Notes Traveler"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
21 July 2014