Microsoft KB Archive/174168: Difference between revisions
(importing KB archive) |
m (Text replacement - """ to """) |
||
Line 55: | Line 55: | ||
== CAUSE == | == CAUSE == | ||
This is usually caused by messages that have the GroupWise | This is usually caused by messages that have the GroupWise "deleted" flag set, but have not been placed in the GroupWise Trashbin. When the Migration Wizard brings these messages across, it places them in the Exchange Server Deleted Items folder. This behavior is by design. | ||
</div> | </div> |
Latest revision as of 11:07, 21 July 2020
Article ID: 174168
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q174168
SYMPTOMS
After migrating messages from GroupWise into Microsoft Exchange Server, users may report that messages from their GroupWise inbox do not show up in their Exchange Server Inbox. When looking at the .pri file created during migration, the administrator may notice the following:
Deleted Items,,,,,,,,,FALSE,FALSE,#00000002.SEC(1497),0,0 Deleted Items,,,,,,,,,FALSE,FALSE,#00000002.SEC(1593),0,0 Deleted Items,,,,,,,,,FALSE,FALSE,#00000002.SEC(1689),0,0
CAUSE
This is usually caused by messages that have the GroupWise "deleted" flag set, but have not been placed in the GroupWise Trashbin. When the Migration Wizard brings these messages across, it places them in the Exchange Server Deleted Items folder. This behavior is by design.
MORE INFORMATION
GroupWise is manufactured by a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.
Additional query words: migwiz gwise
Keywords: kbtshoot kbusage KB174168