none
Standalone MAPI cannot access Exchange 2007 - ecDoConnect returns ecClientVerDisallowed RRS feed

  • Question

  • Hi all,

    One of our customers has a problem with MAPI access to Exchange 2007.
    They use the standalone MAPI (ExchangeMAPICDO 6.5.8069.0).
    Even the MFCMAPI32 application fails when opening the mailbox store.

    A network trace shows that the error occurs during ecDoConnect (organization name changed):

    Exchange 5.5 EMSMDB, EcDoConnect: /o=ABCDEFGH/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=sa-tcvoiceserv
    Operation: EcDoConnect (0)
    Max Count: 95
    Offset: 0
    Actual Count: 95
    Name: /o=ABCDEFGH/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=sa-tcvoiceserv
    Unknown1: 32768
    Unknown1: 2935682502
    Unknown1: 0
    Code Page: 1252
    Input Locale
    Language: 1033
    Method: 1033
    Unknown2: 4294967295
    Unknown3: 1
    Emsmdb Client Version: 6
    Emsmdb Client Version: 8069
    Emsmdb Client Version: 0
    Pointer to Alloc Space (uint32)
    Alloc Space: 2088935296




    The response is:


    Pointer to Handle (policy_handle)
    Policy Handle
    Handle: 0000000000000000000000000000000000000000
    Unknown4: 60000
    Unknown4: 60
    Unknown4: 1000
    Pointer to Session Nb (uint16)
    Session Nb: 0
    (NULL pointer) Pointer to Org Group (uint8)
    (NULL pointer) Pointer to User (uint8)
    Store Version: 2049
    Store Version: 33106
    Store Version: 0
    Emsmdb Client Version: 6
    Emsmdb Client Version: 8069
    Emsmdb Client Version: 0
    Pointer to Alloc Space (uint32)
    Alloc Space: 3673370024
    MAPISTATUS: Unknown (0x000004df)

    There is a public folder store defined for the mailbox store, so this does not seem to be the problem.
    (We also tested with MAPI profiles that did not use the public folder store).

    I checked the output of the following commandlets:
    get-mailboxdatabase
    get-mailboxserver
    test-MAPIconnectivity
    get-CASmailbox

    The values look okay, concerning settings for MAPI.

    Where else can we look?
    Is there a way to force error logging on the server?


    Thanks in advance
    Annemarie
    Thursday, August 27, 2009 9:28 AM

Answers

  • Hi Annemarie,

    This forum is for discussion around the technical content and implementation using the the Open Protocol specifications for Exchange Server found here.  The question you asked does have some coverage in the documentation in the [MS-OXCRPC] section covering ExDoConnectEx that covers the returned error code you mentioned above here.  Do note that even though CDO uses ExDoConnect the method is depreciated as noted in a previous forum post.

    Because this is a question around client access using CDO you would be better served by posting your question to TechNet > Exchange Server > Development forum found here.


    Developer Consultant
    Thursday, August 27, 2009 5:59 PM
    Moderator

All replies

  • Hi Annemarie,

    This forum is for discussion around the technical content and implementation using the the Open Protocol specifications for Exchange Server found here.  The question you asked does have some coverage in the documentation in the [MS-OXCRPC] section covering ExDoConnectEx that covers the returned error code you mentioned above here.  Do note that even though CDO uses ExDoConnect the method is depreciated as noted in a previous forum post.

    Because this is a question around client access using CDO you would be better served by posting your question to TechNet > Exchange Server > Development forum found here.


    Developer Consultant
    Thursday, August 27, 2009 5:59 PM
    Moderator
  • Hi all,

    It seems  that  we found the reason of this problem.
    Registry value HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Disable Mapi Clients
     was set to
    -10.6515.6626


    Thanks.

    Annemarie
    Thursday, September 3, 2009 6:04 AM