MAPI_E_NETWORK_ERROR returned from ConfigureMsgService

[Duncan Smith]

Hello,

I am having problems creating MAPI profiles for mailboxes on a Exchange 2007
server.

The code I am using to create the MAPI profile succeeds when the Exchange
2007 server is hosted in a pure Exchange 2007 environment on Server 2003 or
Server 2008. The code fails under the following circumstances:

1) Existing Exchange 2003 environment hosted entirely on 32 bit Windows
Server 2003.

2) An Exchange 2007 server hosted on Windows Server 2008 is added into this
Exchange organisation.

3) Installed the Microsoft Exchange Server MAPI Client and Collaboration
Data Objects 1.2.1 download to provide client MAPI support on the Exchange
2007 server.

4) Installed our application onto the Exchange 2007 server and it always
fails when creating the MAPI profile for our mailbox on the local Exchange
2007 server. It fails when calling IMsgServiceAdmin::ConfigureMsgService and
returns MAPI_E_NETWORK_ERROR.

I have installed MFCMAPI on the Exchange 2007 server to check that profiles
can be created and this also fails to create a valid profile for mailboxes
hosted on the Exchange 2007 server. It can create profiles for mailboxes
hosted on the Exchange 2003 servers so the MAPI client is working but not
when connected to the local server.

Using the MAPI profile creation dialog shows up an interesting feature. When
the "Check Name" button is pressed to check the mailbox exists on the server
it returns an network error dialog box when the Exchange 2007 server's
hostname is used. When the IP address is entered it succeeds.

It looks like the MAPI client is failing to resolve the hostname. Has anyone
else seen this scenario?

I can ping the Exchange 2007 server locally using the hostname and nslookup
successfully resolves the hostname so DNS is working.

Any ideas?

Many thanks for any help you can provide.

Regards
Duncan

[Duncan Smith]

It appears that this is caused by the hostname resolving to the IPv6 address.
It appears that the MAPI CDO 1.2.1 download, that claims to be compatible
with Server 2008, cannot handle IPv6 addresses. Server 2008 will use an IPv6
address in preference to an IPv4 address which is causing the issue.

Is there a workaround for this?

Or even better when will the MAPI CDO download handle IPv6 addresses?

Regards
Duncan

Post by Duncan Smith
Hello,
I am having problems creating MAPI profiles for mailboxes on a Exchange 2007
server.
The code I am using to create the MAPI profile succeeds when the Exchange
2007 server is hosted in a pure Exchange 2007 environment on Server 2003 or
1) Existing Exchange 2003 environment hosted entirely on 32 bit Windows
Server 2003.
2) An Exchange 2007 server hosted on Windows Server 2008 is added into this
Exchange organisation.
3) Installed the Microsoft Exchange Server MAPI Client and Collaboration
Data Objects 1.2.1 download to provide client MAPI support on the Exchange
2007 server.
4) Installed our application onto the Exchange 2007 server and it always
fails when creating the MAPI profile for our mailbox on the local Exchange
2007 server. It fails when calling IMsgServiceAdmin::ConfigureMsgService and
returns MAPI_E_NETWORK_ERROR.
I have installed MFCMAPI on the Exchange 2007 server to check that profiles
can be created and this also fails to create a valid profile for mailboxes
hosted on the Exchange 2007 server. It can create profiles for mailboxes
hosted on the Exchange 2003 servers so the MAPI client is working but not
when connected to the local server.
Using the MAPI profile creation dialog shows up an interesting feature. When
the "Check Name" button is pressed to check the mailbox exists on the server
it returns an network error dialog box when the Exchange 2007 server's
hostname is used. When the IP address is entered it succeeds.
It looks like the MAPI client is failing to resolve the hostname. Has anyone
else seen this scenario?
I can ping the Exchange 2007 server locally using the hostname and nslookup
successfully resolves the hostname so DNS is working.
Any ideas?
Many thanks for any help you can provide.
Regards
Duncan

[Stephen Griffin]

Closing the loop:
http://blogs.msdn.com/stephen_griffin/archive/2008/08/15/mapi-and-ipv6.aspx

Post by Duncan Smith
It appears that this is caused by the hostname resolving to the IPv6 address.
It appears that the MAPI CDO 1.2.1 download, that claims to be compatible
with Server 2008, cannot handle IPv6 addresses. Server 2008 will use an IPv6
address in preference to an IPv4 address which is causing the issue.
Is there a workaround for this?
Or even better when will the MAPI CDO download handle IPv6 addresses?
Regards
Duncan

Post by Duncan Smith
Hello,
I am having problems creating MAPI profiles for mailboxes on a Exchange 2007
server.
The code I am using to create the MAPI profile succeeds when the Exchange
2007 server is hosted in a pure Exchange 2007 environment on Server 2003 or
1) Existing Exchange 2003 environment hosted entirely on 32 bit Windows
Server 2003.
2) An Exchange 2007 server hosted on Windows Server 2008 is added into
this
Exchange organisation.
3) Installed the Microsoft Exchange Server MAPI Client and Collaboration
Data Objects 1.2.1 download to provide client MAPI support on the Exchange
2007 server.
4) Installed our application onto the Exchange 2007 server and it always
fails when creating the MAPI profile for our mailbox on the local Exchange
2007 server. It fails when calling IMsgServiceAdmin::ConfigureMsgService and
returns MAPI_E_NETWORK_ERROR.
I have installed MFCMAPI on the Exchange 2007 server to check that profiles
can be created and this also fails to create a valid profile for mailboxes
hosted on the Exchange 2007 server. It can create profiles for mailboxes
hosted on the Exchange 2003 servers so the MAPI client is working but not
when connected to the local server.
Using the MAPI profile creation dialog shows up an interesting feature. When
the "Check Name" button is pressed to check the mailbox exists on the server
it returns an network error dialog box when the Exchange 2007 server's
hostname is used. When the IP address is entered it succeeds.
It looks like the MAPI client is failing to resolve the hostname. Has anyone
else seen this scenario?
I can ping the Exchange 2007 server locally using the hostname and nslookup
successfully resolves the hostname so DNS is working.
Any ideas?
Many thanks for any help you can provide.
Regards
Duncan