15.0 GroupWise Check Error Codes

GWCheck generates two sets of numeric codes: error codes and problem codes. Both sets of codes are in the same numeric range, but error codes are clearly labeled as errors, for example, “Error 9”.

The GWCheck problem codes are not documented because there is nothing you as an administrator need to do about the problems GWCheck is reporting. GWCheck fixes these problems for you.

This section contains information about the following numeric codes, which are GWCheck error codes:

NOTE:This guide does not include a comprehensive list of all possible GroupWise Check error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.

01 Memory initialization error

Source: GroupWise Check utility (GWCheck).
Explanation: Insufficient memory to run GWCheck.
Action: Run GWCheck where adequate memory is available.

02 WPHOST.DB database read error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot access the post office database (wphost.db) for Address Book information.
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in theGroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

03 Record read error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read records from the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

04 User record has no DS_HOST_NAME

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

05 User record has no DS_OBJ_TYPE

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

06 User record has no DS_FID

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

07 User record has no DS_USER_NETID

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

08 User database read error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read records from the specified user database (userxxx.db).
Action: Perform a structural analyze/fix on the user database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

09 Message database read error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read records from the specified message database (msgnnn.db).
Action: Perform a structural analyze/fix on the message database by supplying the name of the message database in the User/Resource field. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the message database cannot be repaired, manually restore it from backup.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

10 Message record read error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read a specific record in a message database (msgnnn.db).
Action: Perform a structural analyze/fix on the message database by supplying the name of the message database in the User/Resource field. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the message database cannot be repaired, manually restore it from backup. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 2012 Administration Guide.

11 Unable to start database transaction

Source: GroupWise Check utility (GWCheck).
Explanation: The specified database is locked or otherwise inaccessible.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

12 Record failed commit

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot write a modified record back to the database.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

13 Record failed modify

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot write a modified record back to the database.
Possible Cause: The record is unavailable. Another user has the record locked.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Possible Cause: The record is damaged.
Action: Perform a structural analyze/fix on the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the database cannot be repaired, manually restore it from backup. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

14 Record delete failed commit

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot delete a record from the database.
Possible Cause: The record is unavailable.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Possible Cause: The record is damaged.
Action: Perform a structural analyze/fix on the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the database cannot be repaired, manually restore it from backup.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

15 Record failed delete

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot delete a record from the database.
Possible Cause: The record is unavailable.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Possible Cause: The record is damaged.
Action: Perform a structural analyze/fix on the database. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the database cannot be repaired, restore it from backup. See Restoring GroupWise Databases from Backup in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

16 User does not exist in post office

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot locate the specified user ID.
Action: Make sure you typed the user ID correctly in the User/Resource field in GWCheck.
Action: If the user ID is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides.

17 Post office does not exist in domain

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot locate the specified post office.
Action: Make sure you provided the correct information for the post office in the Database Path and Post Office Name fields.

18 Message database open error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot open the specified message database (msgnnn.db).
Action: Perform a structural analyze/fix on the message database by supplying the name of the message database in the User/Resource field. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: If the message database cannot be repaired, manually restore it from backup.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

19 WPHOST.DB database open error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot open the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

20 User record has no DS_DOMAIN_NAME

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

21 Unable to decrypt database

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid user record in the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

23 Unable to rename file for rebuild backup

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot create a backup copy of the existing database.
Possible Cause: All valid backup database file names have already been used.
Action: Check for existing backup databases with extensions .dba through .dbz. If all 26 backup extensions have been used, delete old backup databases so valid backup extensions are available.
Possible Cause: Insufficient disk space.
Action: Free up disk space by deleting unneeded files.
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the database being repaired is located.

24 Path modify error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot create a needed directory path.
Action: Check rights and available disk space.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

25 Database create error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot create a new user database (userxxx.db).
Possible Cause: Insufficient disk space.
Action: Free up disk space by deleting unneeded files.
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the database being repaired is located.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

26 Database rebuild error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot rebuild the database.
Possible Cause: Insufficient disk space.
Action: Free up disk space by deleting unneeded files.
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the database being repaired is located.
Possible Cause: All valid backup database file names have already been used.
Action: Check for existing backup databases with extensions .dba through .dbz. If all 26 backup extensions have been used, delete old backup databases so valid backup extensions are available.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

28 User file already exists or current file inaccessible

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot create a backup copy of the existing database.
Possible Cause: Insufficient disk space.
Action: Free up disk space by deleting unneeded files.
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the database being repaired is located.

29 User database close error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot close the specified user database (userxxx.db).
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the repaired database will be written.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

30 User database not found

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot locate the specified user database (userxxx.db) to check.
Possible Cause: You specified the user incorrectly.
Action: Make sure you typed the user name correctly in the User/Resource field in GWCheck.
Possible Cause: The user database is missing from the post office.
Action: Re-create the user database. See Re-creating a User Database in Databases in the GroupWise 2012 Administration Guide.
Action: Restore the user database from backup.
Action: If the user name is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides.

31 Exclusive access denied to user database

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot get sufficient access to the specified user database (userxxx.db).
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the user database.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.

32 User database open error

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot open the specified user database (userxxx.db).
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

33 Error initializing database engine code

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot initialize the database engine code.
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the database to repair.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

34 Unable to get post office information

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read information from the post office database (wphost.db).
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

35 Memory allocation error

Source: GroupWise Check utility (GWCheck).
Explanation: Insufficient memory to run GWCheck.
Action: Run GWCheck where adequate memory is available.

36 Message database not found

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot locate the specified message database (msgnnn.db).
Action: Restore the message database from backup.

37 Exclusive access denied to message database

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot get sufficient access to the specified message database (msgnnn.db).
Possible Cause: Insufficient rights.
Action: Make sure you have write access to the directory where the message database is located.
Action: Retry. There might have been a timing problem with another database user.
Action: See if another program, such as the POA, has the database open with exclusive access and has hung with the database open.

38 Error writing message record as user outbox item

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot add a message as a received item in a user’s mailbox.
Action: Perform a structural analyze/fix on the user’s message database by supplying the name of the message database in the User/Resource field. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

39 Error writing message record as user inbox item

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot add a message as a sent item in a user’s mailbox.
Action: Perform a structural analyze/fix on the user’s message database by supplying the name of the message database in the User/Resource field. See Maintaining User/Resource and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: For additional information, look up the associated engine error code in Section I, GroupWise Engine Error Codes.

41 All substitute filenames used for rename of database

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck uses file extensions .dba through .dbz for backup copies of databases. All valid backup database names have already been used.
Action: Delete old backup databases so valid backup extensions are available.

42 Invalid database; truncated to nn bytes

Source: GroupWise Check utility (GWCheck).
Explanation: The database has been modified externally to an illegal size.
Action: Perform a structural rebuild on the user database. See Performing a Structural Rebuild of a User Database in Databases in the GroupWise 2012 Administration Guide.
Action: Perform a structural rebuild on the user’s message database by supplying the name of the message database in the User/Resource field. See Analyzing and Fixing User and Message Databases in Databases in the GroupWise 2012 Administration Guide.
Action: Restore the database from backup.

43 Dictionary file missing; cannot continue

Source: GroupWise Check utility (GWCheck).
Explanation: The specified database dictionary (.dc) file is missing from the post office.
Action: Copy the missing *.dc file from the po subdirectory of the software distribution directory to the post office directory. See GroupWise Software Distribution Directory and Post Office Directory in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.

44 Database invalid due to security breach

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot open the specified database because it contains an invalid verification record.
Possible Cause: The database has been modified in some unauthorized way.
Possible Cause: The database has been copied from another post office.
Action: Restore the original database from backup.

47 Error in library sync with host

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck synchronizes information in the library database (dmsh.db) with information in the post office database (wphost.db).
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The post office database is damaged.
Action: In ConsoleOne, rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 2012 Administration Guide.

48 Orphaned QuickFinder index file

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered a QuickFinder index file that was not associated with any library.
Action: None. GWCheck deleted the extraneous index file.

49 Invalid QuickFinder index file

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid QuickFinder index file.
Action: None. GWCheck deleted the invalid index file.

50 Orphaned blob file

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered a BLOB file that was not associated with any library.
Action: None. GWCheck deleted the extraneous BLOB file.

51 Invalid blob file

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered an invalid BLOB file.
Action: None. GWCheck deleted the invalid BLOB file.

52 Blob file missing trailer

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck encountered a BLOB file that did not have a trailer.
Action: None. GWCheck deleted the invalid BLOB file.

53 Blob file truncated to 0 bytes

Source: GroupWise Check utility (GWCheck).
Explanation: The specified BLOB file has been modified externally to an illegal size.
Action: Restore the original BLOB file from backup.

61 Error adding system document type definition

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot add the specified document type definition to the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

62 Error reading system document type definition

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read the specified document type definition in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

63 Unable to update during check error code

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot write changes to the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

64 Unable to complete verify during check error code

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot verify the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

65 Unable to add default system document types

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot add default document types to the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

66 Unable to correct document display name

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot modify the specified document display name in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

67 Unable to correct element without version object

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot correct the specified element because version information was missing in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

68 Unable to synchronize document security

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot synchronize security information for the specified document in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

69 Unable to correct document without version object

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot correct the specified document because the version information was missing in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

70 Unable to correct version without document

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot correct the version information because the specified document was missing in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

71 Unable to correct version without element

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot correct the version information for a document because the specified element was missing in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

72 Invalid user specified for orphan document reassignment

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot locate the user ID specified in the New Author field in GWCheck.
Action: Make sure you typed the user name correctly in the New Author field.
Action: If the user name is typed correctly, make sure you provided the correct information in the Database Path and Post Office Name fields for the post office where the user resides.

73 Unable to remove document storage area

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot delete the specified document storage area.
Possible Cause: Insufficient rights.
Action: Make sure you have rights to the directory where the document storage area is located.

74 Unable to move all blobs; storage area cannot be removed

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot delete the specified storage area because BLOBs still exist in it.
Possible Cause: Insufficient disk space.
Action: Make sure there is free disk space in the directory where you are trying to move the BLOBs to.
Possible Cause: Insufficient rights.
Action: Make sure you have rights to the directory where the document storage area is located.

75 Unable to move blob

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot move the specified BLOB file.
Possible Cause: Insufficient disk space.
Action: Make sure there is free disk space in the directory where you are trying to move the BLOBs to.
Possible Cause: Insufficient rights.
Action: Make sure you have rights to the directory where the document storage area is located.

76 Error accessing document content

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot read the content of the specified document.
Possible Cause: The library database (dmsh.db) is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

77 Error accessing blob for official version distribution list

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot access the specified BLOB file containing the official version distribution list for a document in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

78 Error accessing blob for current version distribution list

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot access the specified BLOB file containing the official current distribution list for a document in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.

79 Error accessing blob for version distribution list

Source: GroupWise Check utility (GWCheck).
Explanation: GWCheck cannot access the specified BLOB file containing the distribution list for a document in the library database (dmsh.db) in the post office.
Possible Cause: The library database is damaged.
Action: Perform a structural analyze/fix on the library. See Analyzing and Fixing Library and Document Information in Databases in the GroupWise 2012 Administration Guide.