-
Title
GroupWise Corruption -
Description
During a GroupWise to Exchange Migration Groupwise Migrator is unable to migrate certain email messages from the Groupwise database, a few examples of what may be seen in the log file are:
======
Error received when migrating a user mailbox:
ERROR: [4951-14-43-0000120C] Unable to migrate message: #0
Unable to export message; received an exception 0xC0000005 from GroupWise API.
Try running GWCheck on message store.
============
"ERROR: [7272-19-34-00000000] Unable to manage worker processes"
============
ERROR: [4978-24-130-8004010F] Unable to migrate attachment 'AttachmentName.txt' for message:
Msg: (434BA025.GWISE_DOM.GWISE_PO.100.1733177.1.38.1)
Folder: (Documents)
Subject: (AttachmentName.txt)
Sender: ("SenderName" <SenderName@gwise.demo.wingra.com>)
Date: (Tue Oct 11 12:00:00 2005)
OpenStreamOnFile(C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\03DC0004.att):
Error 8004010F
====== -
Cause
This is typically caused by corruption on the Groupwise database.
Database corruption can be caused by many things. Below are some of the most common known causes of corruption are (in no particular order):
Abnormal termination of SoftwarePower failures,
Server hardware problems, NICs, Hard Drives, memory etc.
Backup software trying to backup open databasesVirus scanners scanning open databases,
User’s workstations accessing their mail via direct access – mapped drive (not client/server)
An interruption of a database transaction can cause corruption. -
Resolution
A support engineer may ask you to try and change the version of Groupwise that you are using for the migration to a different version as some versions of Groupwise work better than others against corruption.
There are compatibility charts that state what version of client can connect to what version of the server. Below are Novell links that explain what client can connect to what server:
GW 6.5
http://www.novell.com/documentation/gw65/?page=/documentation/gw65/gw65_install/data/bphm8xb.html
GW 7
==
Table Summary:The GroupWise 6.x Windows client can communicate with the GroupWise 7 POA, but it cannot access a GroupWise 7 post office directly. The general rule is that later POAs can always communicate with earlier GroupWise clients, but earlier POAs cannot communicate with later GroupWise clients.
==
GW 8
==
Table Summary:The GroupWise 7 Windows client can communicate with the GroupWise 8 POA, but it cannot access a GroupWise 8 post office directly. The general rule is that later POAs can always communicate with earlier GroupWise clients, but earlier POAs cannot communicate with later GroupWise clients.
==
-
Additional Information
Also see: SOL59640 - What options should be selected while running GWCheck? Is there any guidance available on this topic? It may help to run GWCheck at least three times against the archive and/or mailbox. Novell advises in its documentation (http://www.novell.com/documentation/gw65/pdfdoc/gw65_tsh1/gw65_tsh1.pdf), "It can sometimes be helpful to run GWCheck multiple times, because as some errors are fixed, others are uncovered."