MAPI_E_NETWORK_ERROR from ConfigureMsgService

MAPI_E_NETWORK_ERROR from ConfigureMsgService

Post by Robert Swo » Thu, 10 Jul 2003 01:40:42


I have a server which spawns a process to impersonate and create a MAPI
session with Exchange 5.5. A customer has two users who can individually go
through my server and connect to Exchange. However, if the server is running
one user in a process and also tries to start the other user in another
process, the second user fails in ConfigureMsgService with
MAPI_E_NETWORK_ERROR.

We have run several hundred concurrent users in our test lab and other
customers have run multiple users. This is only happening with one
particular customer.

Is there some MAPI or Exchange configuration which will only allow one
session or connection from a machine? The server hasn't actually done a
MAPILogonEx yet for the second user but it has impersonated the second user
at this point.

Thanks.
 
 
 

MAPI_E_NETWORK_ERROR from ConfigureMsgService

Post by Robert Swo » Thu, 10 Jul 2003 04:27:48

Is it possible for the Exchange licensing to prevent multiple connections
from one machine? I have one session for one user and am trying to do
ConfigureMsgService for another user which gets rejected.

Could Exchange be rejecting the ConfigureMsgService due to licensing or some
other Exchange configuration?

Thanks.



go
running
user

 
 
 

MAPI_E_NETWORK_ERROR from ConfigureMsgService

Post by Robert Swo » Sat, 12 Jul 2003 05:19:15

Here is a little update on the situation.

The customer had Outlook 2002 installed on the machine running my code. The
first user was able to connect but a second, concurrent user, got a
MAPI_E_NETWORK_ERROR from ConfigureMsgService. Individually or serially,
both users could connect.

The customer uninstalled Outlook 2002 and installed Outlook 2000 and
everything appears to work.

Does anyone know the difference of MAPI between the two versions? I didn't
think that MAPI changed. Has anyone else encountered problems with MAPI from
Outlook 2002?

The OS in both cases was Windows Server 2000 SP3.

Thanks.