MAPI/WMS issues under XP.

[david howes]

Hi,

We have several applications (ClearQuest and Python Scripts for example) that use MAPI to send email.
Under our Windows 2000 workstations this isn't a problem, WMS (Windows Messaging Subsystem) installs correctly and mdisp32.exe takes care of the "MAPI.session" part of things.

Under Windows XP WMS "seems" to install correctly but MAPI functionality using "MAPI.session" doesn't seem to work. The only 'work around' for this is to manually register a new WMS/CDO DLL library that contains MAPI.session (in this case OLEMSG32.DLL) this however creates a new problem, messages are not sent (by MAPI) if GroupWise is in offline mode.

Ideally I'd like to get the WMS installation working correctly, but a fix for the offline issue would be a second best alternative.

Can anyone provide any suggestions?

Regards,
David Howes

[David Tracy]

Have you tried using the FIXMAPI Utility? Novell has found many of the MAPI
Inconsistencies are due to the different MAPI DLL's that can be placed on a
system. For example, the GroupWise MAPI WMS.Exe installs a version of the
Windows Messaging System based on Windows NT code. This version of WMS.Exe
will install the MAPI DLLs into the Windows System32 directory. However,
newer versions of MAPI from Microsoft install in a different directory. On
Windows XP, this directory is normally "c:\Program Files\Common
Files\System\MSMAPI\1033". The FIXMAPI utility installs the newest MAPI DLLs
into both directories.

Post by david howes

On Monday, May 15, 2006 at 4:01 PM, in message

Hi,
We have several applications (ClearQuest and Python Scripts for example)
that use MAPI to send email.
Under our Windows 2000 workstations this isn't a problem, WMS (Windows
Messaging Subsystem) installs correctly and mdisp32.exe takes care of the
"MAPI.session" part of things.
Under Windows XP WMS "seems" to install correctly but MAPI functionality
using "MAPI.session" doesn't seem to work. The only 'work around' for
this is to manually register a new WMS/CDO DLL library that contains
MAPI.session (in this case OLEMSG32.DLL) this however creates a new
problem, messages are not sent (by MAPI) if GroupWise is in offline mode.
Ideally I'd like to get the WMS installation working correctly, but a
fix for the offline issue would be a second best alternative.
Can anyone provide any suggestions?
Regards,
David Howes