Exchange Server 2013 // MFCMAPI could connect with errors

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   = <[email protected]>;
    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 tried
[email protected] 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
Are there any configuration changes need to be done on Exchange Server?
Is there any mistake in above parameters?
Kindly suggest.

You can refer Dave's blog post @
http://blogs.msdn.com/b/dvespa/archive/2013/05/21/how-to-mfcmapi-create-mapi-profile-exchange-2013.aspx
DeVa, M.S., {MSFT} Please remember to mark the replies as answers if they help

Similar Messages

  • Exchange Server 2013: Failed to connect. Winsock error code: 10060, Win32 error code: 10060.

    Dear All,
    I have exchange server 2013 running with windows server 2012.
    My email server have been send and receive email with internal and external as normal.
    Today, i got the problem the email cannot send out to external and get the error below:
    Please comment.
    BR,
    Khemarin
    [email protected]

    Hi Khemarin,
    If it is Smarthost, are you able to telnet your smarthost using 25 port number?
    Also please check your Send Connector setting.
    http://technet.microsoft.com/en-us/library/aa998662(v=exchg.150).aspx
    Thanks
    Mavis
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013 Client Mail are Return.Error is [0x80040305-0x0004de-0x00054a]

    Hi,
    We are using Exchange Server 2013.we have Outlook 2007 SP3 and 2010 SP2 client .Some clients inform mails are return.
    Return massage
    "This message could not be sent. Try sending the message again later, or contact your network administrator. Your server administrator has limited the number of items you can open simultaneously.
    Try closing messages you have opened or removing attachments and images from unsent messages you are composing. Error is [0x80040305-0x0004de-0x00054a]"
    Thanks,
    Gayan

    1) Disable TCPChimney and RSS on CAS and Mailbox Servers by running below commands
    netsh int tcp set global chimney=disabled
    netsh int tcp set global rss=disabled
    2) Disable unwanted Add-Ins in outlook that may open many sessions
    3) If above steps doesnt resolve, you can delete existing outlook profile and create new Outlook online profile

  • New Exchange Server 2013 in a Exchange 2007 Org, can't get cu's to install

    Hi,
    We have an Exchange Server 2007 in our organization. I installed an Exchange Server 2013 but could not get the CU3 to install, would throw exceptions. I tried CU2 and it got a lot further but failed to start a service near the end. Don't ask for specifics
    as I got frustrated and blew this machine away and installed a fresh VM. I read that you can install the CU's as if they are a fresh installation. I tried this but it fails saying "the Exchange server is in an inconsistant stet....recover". There
    IS no Exchange server yet!!
    What am I doing wrong? I used the command line for CU3, like: setup /mode:install /roles:ca,mb,mt /IAccept blah blah blah. I didn't set powershell execution policy, not sure if that was it. Are there switches I am missing? I want to see if I can install
    the Exchange CU3 right from the get-go.
    HeLp!

    Hi,
    According to the error message, this issue may occur if the previous Exchange installation or un-install failed to complete. This situation leaves the Exchange server
    object in Active Directory and prevents a new installation.
    We can try:
    1. Install ADSI Edit.
    2. Launch ADSI Edit. To do this, click Start, click Run, type adsiedit.msc in the text box, and then click OK.
    3. Locate the Exchange server object by going to the following location: CN=Configuration, DC= Domain Name, DC=com, CN=Services, CN=Microsoft Exchange, CN=<Organization
    Name>, CN=Administrative Groups, CN= <Exchange Administrative Group>, CN=Servers, CN=<Server Name>.
    4. Delete the server object.
    5. Remove the Exchange server's machine account from Security groups Exchange Servers and Exchange Install Domain Servers.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange Server 2013 failover design

    Hello:
    I'm designing a failover Exchange Server 2013 solution. I only need mail and calendar services.
    I'm planning to put two physical servers with Windows Server 2012 R2 with (or without) Hyper-V to run one virtual machine in
    each physical server.
    I don’t have external storage device, I like to use database replication
    Also, I have a physical third party anti-spam firewall
    The questions:
    I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server?
    I need a third server to avoid brain duplication, or isn’t needed?
    Exchange Server 2013 supports POP3 connections?
    Thanks for your time, and sorry for my bad English!
    Un saludo! Juan Segura

    The questions:
    I need one VM for Mailboxes and a separate one for CAS (4 VMs in total) or I can install 2 VMs with MBX+CAS in each VM server? - Definitely you can go for multi-role servers
    to combine MBX+CAS and in fact that's
    recommended except couple scenarios.
    I need a third server to avoid brain duplication, or isn’t needed? You need a witness server but that can be non-Exchange server too. You need to add Exchange trusted subsystem
    in Local Admin group of that server
    Exchange Server 2013 supports POP3 connections? - Yes, you can have POP3 connections
    Blog |
    Get Your Exchange Powershell Tip of the Day from here

  • Outlook 2013 not connect with Exchange server 2013 in internal network

    Hello All,
    I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
    but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
    I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network. 
    Can you please suggest as soon as possible.
    Thanks,
    Parvez

    Hi,
    Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
    Thus, let’s try the following resolutions:
    1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
    2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
    3. Check if the above host name is in your certificate.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Connecting to Exchange Server 2013 using IMAP command gives authenication error

    Hello All,
    My application (it is a C# code) connects to Microsoft exchange server 2013 using POP3 and IMAP, processes the emails, marks as read and move to particular folder if it is processed successfully else to an different folder.  In this sometimes,
    I am getting authentication failed error from IMAP however same mail is processed when it is executed next time. Few times it is processed with out error. I am not sure what is causing this issue.We are connecting to IMAP using tcpIMAP command.
    This is the same application which we used with exchange server 2010 now we are upgrading to exchange server 2013. I have verified that the setting of exchange 2010 and 2013 are the same.
    To verify the IMAP command I created a sample application using C# which will try to connect to IMAP service and log in to exchange server 2013; it fails to authenticate the user after connecting for few times and then it starts to authenticate
    successfully then again fails for few times and then authenticates. I am not sure why this is happening. 
    Please suggest how can I resolve this.
    Thank you, Santha

    Since I've upgraded to Snow Leopard I've also moved from Entourage 2008 to Mail, iCal & Addressbook with the new Exchange support.
    My company exchange server is Exchange 2007.
    Mail works fine except the occasional Mail crash.
    iCal worked fine the first two days and then it came with an error the it cannot connect to the Exchange server and asks me to type my email address again. Doesn't work so I need to put my exchange calendar in iCal in offline. But now there is no syncing with the Echange server.
    This only occurs when I add a meeting request in iCal.
    My Exchange administrator has reset my mailbox on the Exchange server.
    This helped for about 4 hours. Now it's the same problem.
    I have a feeling the when you setup your exchange account in Mail it uses different settings for Mail and iCal with the autoconfig.
    Anybody has a solution? My Exchange admin cannot find any problems on his side. Do I need to make changes on my iCal client or do we need to wait for OS 10.6.1 ?

  • Strange Exchange name when connecting with Outlook 2013 to Exchange server 2013 SP1

    I've setup a test environment with Windows Server standard 2012 R2 and Exchange Server 2013 SP1...
    In- and outbound SMTP works fine, as well as connecting with OWA and Mac Outlook client...
    Oddly though when setting up an Outlook 2013 connection....it recognizes the email address correctly, but later on can't connect and shows a dialog to enter the server and email account manually....though the profiled fields show something like:
    Exchange Server: [email protected]
    Mailbox: =SMTP:[email protected]
    When I fill in the right fields....it won't connect and falls back to the values above...
    Something wrong in the Exchange setup?

    Hmm...found aguide here:
    http://enterpriseit.co/microsoft-exchange/2013/ssl-certificate-request/
    Though it doesn't mention anything that with the self-signed certs it won't allow Outlook 2013 to connect...
    So from my point of view Outlook 2013 should be able to connect anyway...as during the connect process you can install the self-signed cert.....so must be something else then...

  • Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

    What am I trying to do?
    I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
    error logs at the bottom of the page but the basics are in order it will throw which loop around are:
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
    What am I running?
    2 X DC on domain and forest functional level 2008R2 both writable
    1 X fresh install of Windows 2012 R2 which is domain joined
    What have I tried?
    Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
    Rebooted every server
    Run setup as Administrator
    My account is part of the domain Enterprise Admin group
    Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
    Computer Configuration Windows Settings
    Security Settings + Local Policies
    User Rights Assignment Mange auditing and security log
    Turned off firewall on DC and Exchange Server even stopped the service
    Turned off all AV on the DC and Exchange Server
    Checked I could telnet to global catalog servers on port 3268 which I can
    Checked the global catalog records existed in DNS which they all do
    Done the obvious ping tests all round which confirms connectivity
    Schema has been prepared using appropriate commands before running the setup exe
    setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
    Making sure the following path has full permissions:
    EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    Restarted Microsoft Exchange Active Directory Topology service
    DcDiag all looks good
    What have I noticed that is suspicious?
    Microsoft Exchange Transport service will not start even though both of its dependences services have started:
    Microsoft Filtering Management Service
    Microsoft Exchange Active Directory Topology Service
    It will eventually error with
    “Windows could not start the Microsoft Exchange Transport Service on local computer
    Error 1053: This Service did not respond to the start of control request in a timely fashion”
    This error is from the GUI wizard itself:
    Error:
    The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
    " was run: "System.Exception: Unable to set shared config DC.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Exchange logs which have been written:
    **The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
    [01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
    '{ mydomain.com}'
    [01/20/2015 17:13:20.0084] [2] User specified parameters: 
    -DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
    No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
    [01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
    [01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
    Windows Event Viewer:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
    in either the local site 'Default-First-Site' or the following sites:

    Hi apl228,
    1. Please make sure the IPv6 is enabled.
    2. Please make sure the account that install Exchange server has Administrator permission.
    3. Please make sure DNS has been configured correctly.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013 Toolbox MMC Error ConsoleInitialize.ps1 not recognised

    Hello, after installing and configuring Exchange 2013 during a migration from 2010 (with both versions still running), I am now receiving a ConsoleInitialize.ps1 System.Management.Automation.RemoteException exception when trying to run the Management Toolbox
    (I am really after the Queue Viewer).
    This is the same when trying to connect locally on the server and remotely on a client computer with Management Tools installed - I can use EMC without any errors locally or remotely.
    I have tried various fixes found around the net, including:
    Changing the Identity of the Classic and DefaultAppPools in IIS and resetting - from LocalSystem to ApplicationPoolIdentity
    Adding the roles to Exchange Organisation Management in AD
    Disabling SSL on the Powershell virtual Directory and setting auth to anonymous
    I have not tried recreating the Powershell virtual directory as mentioned on a few sites, as I have not been able to test that in the lab, and I am not sure how it affects the powershell session that I am doing it from.
    The only thing that I can think that could be an issue is that Ex2010 is still up and running, could it be that Management Tools is looking at the old server, instead of the new?
    Can anyone point me in the right direction with this one?
    I can post more info if required.
    Thank you.
    Xpost here: http://serverfault.com/questions/666054/exchange-server-2013-toolbox-mmc-error-consoleinitialize-ps1-not-recognised

    Hi,
    If the EMS and EMC work properly, I think the powershell cannot be the problem. Is it possible to build up a new Exchange 2013 Server in test environment and make a replacement of
    the ConsoleInitialize.ps1 file?
    Thanks,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Error when try to install exchange Server 2013 in windows server 2008 R2 Sp1

    Hi
    I'm getting these errors while trying to install Microsoft Exchange Server 2013 on my Windows Server 2008 R2 SP1 the user i'm using is the Administrator and it is already a member of "Enterprise
    Admins" and "Schema Admins"
    in my organization there is 6 Exchange server 2013 in 3 site windows server 2012 in this case
    I have to install exchange 2013 in windows Server 2008 r2 sp1
    the functional level  2008 R2 I getting these errors please help.
    Errors:
    This computer doesn't belong to a valid Active Directory site. Check the site and subnet definitions.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.InvalidADSite.aspx
    Error:
    A reboot from a previous installation is pending. Please restart the system and then rerun Setup.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RebootPending.aspx
    Error:
    There is a pending reboot from a previous installation of a Windows Server role or feature. Please restart the computer and then run Setup again.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.PendingRebootWindowsComponents.aspx
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    Error:
    Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites or by replication latency.  See the Exchange setup log for more
    information on this error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

    I think it's from subnet in site and services
    have 3 site A,B,C and new site is  "D"I have problem in "D" site
    A subnet is 10.33.50.0/24  AD 2012 ,exchange 2013
    B subnet is 10.35.50.0/24 AD 2012 ,exchange 2013
    C subnet is 10.36.50.0/24 AD 2012 ,exchange 2013
    D subnet is 10.100.100.0/25 AD 2008 ,exchange 2013 error when install it
    find event error
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair
    the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    test-SetupPrerequisites
    {Roles={LanguagePacks, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport, Cafe}, LanguagesAvailableToInstall=True, DomainController=, CustomerFeedbackEnabled=True, ExchangeVersion=15.0.847.32, LanguagePackDir=D:\Exchange
    Server Software, SufficientLanguagePackDiskSpace=True, ADInitError=Setup encountered a problem while validating the state of Active Directory: Could not find information about the local site. This can be caused by incorrect configuration of subnets or sites
    or by rep, ScanType=PrecheckInstall, LanguagePackVersioning=True, HostingDeploymentEnabled=False, TargetDir=C:\Program Files\Microsoft\Exchange Server\V15, SetupRoles={LanguagePacks, AdminTools, Bridgehead, ClientAccess, UnifiedMessaging, Mailbox, FrontendTransport,
    Cafe}}

  • Exchange Server 2013 - Lab setup with internal emails only

    Hi,
    I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
    go over the internet. 
    I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
    Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
    Regards,
    Nithin

    Hi,
    You need not to configure send/receive connectors for internal email.
    The following article for your reference:
    http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
    Default Receive connectors created during setup
    Certain Receive connectors are created by default when you install the Mailbox server role.
    Default Receive connectors created on a Mailbox server running the Transport service
    When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
    These connectors are the following:
    Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
    Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
    Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
    mentioned, their TransportRole value is HubTransport.
    To view the default Receive connectors and their parameter values, you can use the
    Get-ReceiveConnector cmdlet.
    Default Receive connectors created on a Front End Transport server
    During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
    connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
    Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
    Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
    Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
    In a typical installation, no additional Receive connectors are required.
    Niko Cheng
    TechNet Community Support

  • Exchange Server 2013 installation error at Step 10/15

    I try to install Exchange Server 2013 on a fresh install of Windows Server 2012.
    Windows Server 2012, have already install on it:
    AD CD
    DNS
    IIS
    Exchange 2013 Prerequisites for Win.Server 2012 like described here
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    And the (winner) error message is:
    Exchange Server component Mailbox role: Client Access service failed.
    Error: Error:
    The following error was generated when "$error.Clear();
    Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Could not grant Network Service access to the certificate with thumbprint ABC7C6378BF63CED166794CFBF410C73B29EDD3A because a cryptographic exception was thrown.".
    I search online for a solution and I found many others with same problem but any solution yet. :(
    If anyone can help me I am able to dedicate him my next ode.
    Thank you,
    Adrian

    I am experiencing the same problem except that mine is definitely NOT a domain controller.  The error code indicates that the process is attempting to grant Network Access to the Certificate during Setup, but fails.
    "...Could not grant Network Service access to the certificate"
    Exchange 2013 is being installed on Windows Server 2012 R2 but it is a member server with no domain responsibilities.  Granting rights to the certificate during the Setup process is the root of the problem.
    Here is the complete error comment:
    The following error was generated when "$error.Clear();
              Install-ExchangeCertificate -WebSiteName "Exchange Back End" -services "IIS, POP, IMAP" -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "Could not grant Network Service access to the certificate with thumbprint 681FC4E2C66D726EFB91A8E0FF7FF6F98942C2F4 because a cryptographic exception was thrown.".

  • Exchange Server 2013 Missing file on ISO install Error Code 1603

    Hi all,   a mystery needs solving any suggestions much appreciated:
    We are trying to install Exchange Server 2013 on Windows 2012 server.
    The ISO File being used is: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118
    All preparation and requisites in place.
    During Stage 2 Copying files, we receive an error code 1603 and installation halts.
    The error states:
    Installing product F:\exchangeserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Source file not found: F:\Setup\ServerRoles\ClientAccess\Owa\prem\version\resources\themes\base\0\microsoft.o365.controls.timeline.mouse.css.
     Verify that the file exists and that you can access it.'.
    We have verified that the Path in the error is correct and exists BUT the file is not present within the 0 folder.
    We have downloaded the ISO from our Action Pack resources twice and attempted 4 separate installations.
    We have tried both Mailbox/Client Access  and Mailbox only installations.
    The missing file: microsoft.o365.controls.timeline.mouse.css. Hopefully the only file misisng???
    Any ideas anyone, could we source a different ISO or copy of the file or ?????
    Many thanks in advance

    Had the same issue with Exchange 2013 SP 1 Downloaded as an ISO from the Volume License Center, installing on a new Server 2012R2 STD box. I found the equivalent file in another ISO but discovered it was just an empty CSS file. So the easiest way is to not
    bother trying to find the file but: 1) open notepad, 2) set save to "All Files", and 3) save an empty CSS file with that filename then place it in the directory indicated in the path given in the error. (Make sure it saves as
    a CSS and not as a TXT.)
    I reran the install and it completed without issue.

  • Http 500 internal server error exchange server 2013

    Hello Everyone
    Here is my little scenario.
    i have a domain named contoso.com
    i then installed exchange server 2013 in my environment.  cas and mailbox server are on seperate box.
    switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
    i now have 2 cas server and 2 mailbox server
    problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
    although with exchange management shell i can connect to all the servers

    -->switched of my exchange servers for a week, during that period i changed the netbios name of my
    domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
    Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain. 
    Renaming of domain is not supported in Exchange2007/2010/2013.  (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
    Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)? 
    Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
    that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
    server.
    Please get back with the result.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Maybe you are looking for

  • Why is it that every time i go into the discription section on any video on the youtube app it crashes?

    I tried closing out of Youtube and then deleting it from the app history and back in but it did not do anything. I tried signing out an in of my youtube account and still didnt work. Its only other channels on my ipod touch 4g. My channels descriptio

  • Don't remember password and I can't change any settings - PLEASE HELP!!!

    Hi, My work is giving an old imac G5 and I can't change the IP address for my home internet because its asking for a password that no one remembers Even my boss is clueless. I tried going into Keychain Assistant, but it seemed not to help at all. We

  • Can't bind to /tmp/claws-mail-1000

    When i try to start claws-mail i got this output: [tirrenia@lappy ~]$ claws-mail can't bind to /tmp/claws-mail-1000: Åtkomst nekas Åtkomst nekas is Access/Permission Denied in Swedish. Anybody have an idea? Thanks

  • Can i change import settings in iphoto?

    I have noticed that when I import photos from my camera into iPhoto, it reduces the file size from 16M (on my camera settings) to 3-4M in iPhoto? I went into Preferences, but I don't see anyway to change it except for RAW settings. Any way around it?

  • Ipod video 5G

    Ok so initially i was having a problem with my ipod and lack of sound in one earphone. Checked different earphones and still same problem. Bought a new back plate with audio jack and battery in etc and installed. But in doing so broke the connector a