GroupWise client doesn't work with other versions of MAPI32.DLL
(Last modified: 28Jan2003)
This document (10072214) is provided subject to the disclaimer at the end of this document.
fact
Novell GroupWise 6 Support Pack 1
symptom
GroupWise client doesn't work with other versions of MAPI32.DLL
GroupWise client doesn't work with the version of MAPI installed by Netscape 4.79 or Microsoft Office 2000.
Error occurs when running setup for the GroupWise 6 client.
Error: Cannot load packing.lst. Please contact system administrator.
cause
GroupWise is not compatible with some versions of the MAPI32.DLL.
fix
This has been submitted to development as a defect.
A workaround is to delete or rename the conflicting versions of the MAPI32.DLL and allowing it to reinstall Windows Messaging.
Another workaround is to put the 1996 version of the MAPI32.DLL in the C:\NOVELL\GROUPWISE directory.
Steps to Duplicate:
1. On a new Windows 2000 Workstation, install Netscape 4.79. That will also install a 2001 version of MAPI32.DLL.
2. Then install the GW 6 client, which will cause the packing.lst error.
3. This can be resolved by renaming the MAPI32.DLL on the workstation. Now GW 6 Setup will install Windows Messaging with a MAPI32.DLL from 1996.
4. After that completes, if you put the 2001 version of the MAPI32.DLL back in place, it will cause various errors with GroupWise.
5. This can be resolved by putting the 1996 version of the MAPI32.DLL in the C:\NOVELL\GROUPWISE directory.
document
| Document Title: | GroupWise client doesn't work with other versions of MAPI32.DLL |
| Document ID: | 10072214 |
| Solution ID: | NOVL80645 |
| Creation Date: | 28Jun2002 |
| Modified Date: | 28Jan2003 |
| Novell Product Class: | Groupware NetWare |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.