Quantcast
Channel: Exchange Server Development forum
Viewing all articles
Browse latest Browse all 7132

Exchange Server 2013 // MFCMAPI could connect with errors

$
0
0

While connecting with Exchange Server 2013 I have started facing problem with my application.

My application fails to connect to Exchange with below parameters, then i have tried using MFCMAPI to if everything is okay. MFCMAPI could connect with above errors.

And I have tried with program using below parameters, i still get network error from MAPI call. Can you kindly help, I can provide any additional details needed.

___ props[prop_count].ulPropTag = PR_PROFILE_UNRESOLVED_NAME;

    props[prop_count].Value.lpszA   = <ProfileUnresolvedName>;

    prop_count++;

    props[prop_count].ulPropTag     = PR_PROFILE_UNRESOLVED_SERVER;

    props[prop_count].Value.lpszA   = <mailboxGUID@domain.com>;

    prop_count++;

    // Setting this to TRUE causes OpenMsgStore() to fail with MAPI_E_UNCONFIGURED

    props[prop_count].ulPropTag      = PR_CONVERSION_PROHIBITED;

    props[prop_count].Value.b        = FALSE;

    prop_count++;

    props[prop_count].ulPropTag     = PR_PROFILE_CONFIG_FLAGS;

    props[prop_count].Value.l       = CONFIG_SERVICE /*| CONFIG_PROMPT_FOR_CREDENTIALS | CONFIG_SHOW_CONNECT_UI */;

    prop_count++;

    props[prop_count].ulPropTag     = PR_DISPLAY_NAME;

    props[prop_count].Value.lpszA   = <Mailbox Profile Name>;

    prop_count++;

    //Above setting used to be sufficient to connect using RPC

    //Below parameters added to connect via HTTPS

    LPSTR pwszUser = "domain\\username"; //also triedusername@domain.com AND username

    LPWSTR pwszPassword = L"paswword"; // Password has been encrypted using CryptProtectData

    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_W;

    props[prop_count].Value.lpszW = L"https://ProxyHostname.domain";

    prop_count++;

    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_AUTH_PACKAGE;

    props[prop_count].Value.l = RPC_C_AUTHN_NONE;      // RPC_C_HTTP_AUTHN_SCHEME_NTLM, RPC_C_HTTP_AUTHN_SCHEME_BASIC

    prop_count++;

    props[prop_count].ulPropTag =  PR_PROFILE_RPC_PROXY_SERVER_FLAGS;

    props[prop_count].Value.l = PRXF_ENABLED | PRXF_SSL;// | PRXF_IGNORE_SEC_WARNING; // | PRXF_IGNORE_SEC_WARNING;

    prop_count++;

    props[prop_count].ulPropTag = PR_PROFILE_RPC_PROXY_SERVER_PRINCIPAL_W;

    props[prop_count].Value.lpszW = L"msstd:certificateserverhostname.domain";

    prop_count++;

    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PACKAGE;

    props[prop_count].Value.l = RPC_C_AUTHN_GSS_NEGOTIATE;                // RPC_C_AUTHN_WINNT, RPC_C_AUTHN_GSS_NEGOTIATE, RPC_C_AUTHN_NONE

    prop_count++;

    props[prop_count].ulPropTag = PR_PROFILE_AUTH_USER_W;

    props[prop_count].Value.lpszA = pwszUser;

    prop_count++;

    props[prop_count].ulPropTag = PR_PROFILE_AUTH_PASSWORD;

    props[prop_count].Value.bin.lpb = dataBlobOut.pbData;

    props[prop_count].Value.bin.cb = dataBlobOut.cbData;

    prop_count++;

    DB( (DB_PR _T("ConfigureExchangeService() About to configureMsgService\r\n"), this ) );

    hres = lpServiceAdmin->ConfigureMsgService( exchUID, 0, config_flags, prop_count, props );___

    I still get MAPI_E_NETWORK not found

  1. Are there any configuration changes need to be done on Exchange Server?
  2. Is there any mistake in above parameters?

Kindly suggest.


Viewing all articles
Browse latest Browse all 7132

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>