Problem 37 LIN_RECORD does not exist in the message database.

  • 7006520
  • 27-Jul-2010
  • 27-Apr-2012


Novell GroupWise 7
Novell GroupWise 8 Support Pack 1
Novell GroupWise 8 Support Pack 1 Hot Patch 1


When running GWCheck a problem 37 is reported and seen as follows:
          Problem 37- LIN_RECORD 150 does not exist in msg132.db
            - Subject:   test subject
            - From:   User A
            - Date:   Apr 15, 2010 - 1:38 pm
          - changing box type to BOX_TYPE_PERSONAL
          - Record 179 updated successfully
This indicates that the message body of the email is missing. When an Analyze/Fix Databases is run from GWCheck with contents and fix selected these items are changed to personal notes. They show up with a push pin in the client and have not message body.


An issue has been found with the POA that occurs when a message has been sent to multiple recipients and a third party application has downloaded the item and the user has not read or taken any action with the item. If all other recpients delete the message the POA would consider the message life cycle as being completed and the message is removed from the message database. This results in a pointer being left in the user database (or a mail message) and corresponding LIN_RECORD is removed from the message database (the message body). If the user were to open this message before GWCheck runs a D107 could occur. A contents check on the user would report a problem 37 and the item would be changed into a push pin.

This has been fixed in GroupWise 8 Support Pack 2.

Two other separate issues were discovered after GroupWise 8 Support Pack 2 shipped. These issues were not new to GroupWise 8 and could have been seen in any previous version of GroupWise. Both issues centered around the auto-delete feature. The auto-delete feature can be applied when a user sends an email. It makes it so that when all recipients of the email have deleted the email, the email is automatically deleted from the user's sent items folder.

The first auto-delete issue occurred when all users have read or downloaded a message that was sent with the auto-delete option. When one of the senders deleted the item it was removed from the message database.

The second auto-delete issue happens after the sender has been renamed or moved. The code was unable to locate the renamed user and thus could not delete the origional sent item.

Both of these issues have been fixed in the post 8.0.2 POA code newer than September 10th, 2010.