Exchange server 2013 showing some error on event Log ( "DCOM" and "MSExchangeMapiMailboxAppPool" )

Error : DCOM was unable to communicate with the computer ADCB.ABCD.net using any of the configured protocols; requested by PID     2bec (c:\windows\system32\inetsrv\w3wp.exe).
Error: A process serving application pool 'MSExchangeMapiMailboxAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '2412'. The data field contains the error number.
Please suggest

Hi Parvez,
According to the error message, I understand that the Event error 10009 is received on DC. Please correct me if there is any misunderstand.
To solve this issue, please follow the steps below:
a. Please ensure that the remote computer is online.
b. This problem maybe the result of a firewall blocking the connection.
c. Other reasons for the problem might be found in the Extended RPC error information that is available in Event Viewer.
More details in the following article:
Event ID 10009 — COM Remote Service Availability
http://technet.microsoft.com/en-us/library/cc774368(WS.10).aspx
If the Remote server contains some 32 bit Applications, please make sure that each Application Pool in IIS, under "Advanced Settings" has "Enable 32 bit Application" set to "True".
Thanks
Mavis
Mavis Huang
TechNet Community Support

Similar Messages

  • 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

  • Upgrade Exchange server 2013 to CU7 error

    Dear Microsoft Team
    I have Exchange server 2013 SP1 and upgrade it to CU5 it is working normal
    But wen I try to Upgrade it to CU7 I got this error massage
    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.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, 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)".
    Best Regards
    Rawa Zangana

    Hi Rawa Zangana,
    According to the error message, it seems that the Global Catalog not reachable from DC.
    Please perform following steps.
    1. Port 3268 listened on DC.
    2. Enable Global Catalog role on all DCs.
    3. Restart Exchange Server 2013 CU5.
    4. Check whether Event 2080 found on all DCs, Event 2080 means that AD connectivity works fine.
    5. Repeat CU7 installation.
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013: no send/receive after failed CU1- CU2 and machine restore

    Hi!
    For several reasons, I decided to fully restore my Exchange Server 2013 machine today.
    The machine is virtualized on Hyper-V.
    I rebooted the server and recovered from backup and Exchange seems to be working fine. However, I cannot receive or send mail. If I try to send a message it goes to the "drafts" folder. OWA and EMC is working. I can not send mail between interna mailboxes
    either. Outlook says disconnected.
    When running the Exhchange Connectivity Analyzer, I get the following:
    - Receive: Connection was successful but no banner was received.
    - Send: Successfull. However when trying to send mail to external mailbox it does not reach that mailbox.
    Mailflow was working perfectly at the time of the backup.
    Help is much appreciated!
    UPDATE 1: When telnet on local server i get SMTP banner. But not on other computers in same subnet.

    OK. After fiddeling around in ADSIedit and trying to rebuild my Exchange environment I ended ut breaking it completely.
    I then restored both my DC (Exchange schema CU2) and my EX (Exchange schema CU1). Scema Versions where the inconsistent as stated.
    Then I uninstalled the KB2874216 successfully. After that i tried to Upgrade Exchange to CU2. The Upgrade failed at Mailbox Role: Mailbox Service With error Message:
    The following error was generated when "$error.Clear();
              if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
                if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
                  $sysMbx = $null;
                  $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";
                  $dispname = "Microsoft Exchange";
                  $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
                  if ( $mbxs.length -eq 0)
                    $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                    if ($dbs.Length -ne 0)
                      $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                      if ($arbUsers.Length -ne 0)
                        $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;
                  else
                    if ($mbxs[0].DisplayName -ne $dispname )
                       set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;
                    $sysMbx = $mbxs[0];
                  # Set the Organization Capabilities needed for this mailbox
                  if ($sysMbx -ne $null)
                      Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
                      set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;
                      # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.
                      # This can be remove after BUG(O15#2555914) is fixed.
                      if ($sysMbx.RetentionPolicy -eq $null )
                         $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});
                         set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;
                  else
                    Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");
                else
                  write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox. Property Name: Database".
    Seems the problem was corrupted arbitrary system mailboxes from previous Exchange 2010 to Exchange 2013 migration.
    The solution for me was to restore the corrupted arbitrary mailboxes using this
    LINK. It is for 2010 but Works on 2013.
    I am now currently on Exchange CU2 on both my EX server and on my DC. Now I have to check mail flow and will report back.

  • Exchange Server 2013 CU3 Installation Error - Fresh Installation

    Hi All,
    I am trying to install Exchange 2013 CU3 on Windows Server 2012 Datacenter Edition. This is New Server Forest build.
    Forest Function Level and Domain functional Level is Windows Server 2008 R2
    As part of this Fresh installation, I have tried to install CAS Server Role first on the server.
    I have full admin (Schema,Entp, Domain) Previliges and installed MS recomended pre-requesities successfully.
    Set the Powershell Execution policy as unrestricted.
    But, When i run setup file using GUI option. I am getting the below error. I would like to know whether this is ignorable for installation or how to fix the issue.
    Error:
    Warning:
    Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type
    initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    Warning:
    Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type
    initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    Warning:
    Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for
    'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    Note: Server OS hardening policy has been applied in this server as per company security policy and Symantec A/V also installed in this server.
    Regards
    Manoj

    Hi,
    Same Error for Mailbox Server also.
    Stopped the Symantec AV Service and Tried. But result is same.
    02/18/2014 06:39:06.0018] [0] Active Directory session settings for 'Get-OrganizationRelationship' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred
    Domain Controllers: '{ TESTPRADC01.Domain.LOCAL }'
    [02/18/2014 06:39:06.0050] [0] User specified parameters:
    [02/18/2014 06:39:06.0050] [0] Beginning processing Get-OrganizationRelationship
    [02/18/2014 06:39:07.0157] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    [02/18/2014 06:39:07.0391] [0] [ERROR] Couldn't find the Enterprise Organization container.
    [02/18/2014 06:39:07.0469] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0610] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0688] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:07.0688] [0] Ending processing Get-OrganizationRelationship
    [02/18/2014 06:39:07.0766] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
    execution result should not be affected.
    [02/18/2014 06:39:08.0015] [0] Active Directory session settings for 'Get-AcceptedDomain' are: View Entire Forest: 'True', Configuration Domain Controller: 'TESTPRADC01.Domain.LOCAL', Preferred Global Catalog: 'TESTPRADC01.Domain.LOCAL', Preferred Domain Controllers:
    '{ TESTPRADC01.Domain.LOCAL }'
    [02/18/2014 06:39:08.0015] [0] User specified parameters:
    [02/18/2014 06:39:08.0015] [0] Beginning processing Get-AcceptedDomain
    [02/18/2014 06:39:08.0078] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Error" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution
    result should not be affected.
    [02/18/2014 06:39:08.0078] [0] [ERROR] Couldn't find the Enterprise Organization container.
    [02/18/2014 06:39:08.0140] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0202] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0265] [0] [WARNING] Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped.
    Task execution result should not be affected.
    [02/18/2014 06:39:08.0265] [0] Ending processing Get-AcceptedDomain
    [02/18/2014 06:39:08.0327] [0] [WARNING] Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task
    execution result should not be affected.
    [02/18/2014 06:39:08.0327] [0] While running the On-Promises test, either Get-AcceptedDomains or Get-OrganizationRelationship return a null value.
    [02/18/2014 06:39:08.0717] [0] Finished loading screen WelcomePage.
    [02/18/2014 06:45:23.0242] [0] Finished loading screen EULAPage.
    [02/18/2014 06:45:26.0908] [0] Finished loading screen RecommendedSettingsPage.
    [02/18/2014 06:45:30.0012] [0] Setup is determining what organization-level operations to perform.

  • Exchange server 2013 setup encounter error

    anyone pls help me, i'm ready setup few time still facing same error.
    Error:
    The following error was generated when "$error.Clear();
    if ($RoleCustomerFeedbackEnabled -ne $null)
         $organizationConfig = get-OrganizationConfig;
    if ($organizationConfig.CustomerFeedbackEnabled -ne $False)
    Set-ExchangeServer -Identity $RoleFqdnOrName -CustomerFeedbackEnabled $RoleCustomerFeedbackEnabled;
    " was run: "Property CustomerFeedbackEnabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

    Hi,
    First, please make sure you have installed all the required prerequisites. For Exchange 2013 prerequisites, please refer to this
    article.
    Then please verify if there is a legacy server via ADSIEDIT. If there is a legacy object, please delete this legacy object. In registry editor, remove the watermark key and action key from the following path and then reinitiate the setup to check the result.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\HubTranportRole
    If the issue persists, to narrow down the issue, I recommend you check the setup log for related error message.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Get list of User Mailboxes in Exchange server 2013 by using EWS managed API

    Hi all,
    I need list of Users exists in my Exchange server 2013 , i.e Mail Box Users log in name.
    i know the command in Powershell  to get list, but i need this using code[ ews managed API].
    How can i achieve this ?
    Please share your ideas

    Hi Glen,
    i follow your suggested links i wrote below code ,
    here i am getting error  
    The term 'Get-Users' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
    SecureString password = new SecureString();
    string str_password = "EIS2014!@#";
    string username = "[email protected]";
    foreach (char x in str_password) { password.AppendChar(x); }
    PSCredential credential = new PSCredential(username, password);
    WSManConnectionInfo connectionInfo = new WSManConnectionInfo(new Uri("http://ExchangeServer.admin.com/powershell"), "http://schemas.microsoft.com/powershell/Microsoft.Exchange", credential);
    //connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Basic;
    Runspace runspace = RunspaceFactory.CreateRunspace(connectionInfo);
    PowerShell powershell = PowerShell.Create();
    PSCommand command = new PSCommand();
    command.AddCommand("Get-Users");
    command.AddParameter("ResultSize", 50);
    powershell.Commands = command;
    runspace.Open();
    powershell.Runspace = runspace;
    var aa = powershell.Invoke();
    Please help me.

  • Installation error for Exchange Server-2013

    I am trying to install exchange server-2013 on my Windows server-2012
    machine. I have configured per-requisite applications and develop the server environment with active directory roles.
    At my readiness check option, it shows the following error:-
    "An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later  and windows server-2012".
    I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
    Regard
    Azad 
    Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

    Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through  the
    exchange 2013  management shell  
    "Get-Exchangeserver" 
    However still not able to connect to https://localhost/eac and when i re-run setup 
    01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
    [01-28-2014 21:10:16.0804] [0] **********************************************
    [01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
    [01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
    [01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
    [01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
    [01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
    [01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
    [01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
    [01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
    [01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
    [01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
    [01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
    [01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
    [01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole 
    [01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked: 
    [01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole 
    [01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
    [01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
    [01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
    [01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
    [01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
    [01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
    [01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
    [01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
    [01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
    [01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
    [01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
    [01-28-2014 21:10:39.0664] [0] Applying default role selection state
    [01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
    [01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
    [01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
    [01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
    [01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
    [01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
    [01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
    [01-28-2014 21:15:30.0513] [0] End of Setup
    [01-28-2014 21:15:30.0513] [0] **********************************************

  • 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

  • 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}}

  • 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

  • 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.

  • CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

    HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012.  I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role,  first i installed the MBX and after the CAS role, i passed
    prerequisite check without any issue.  However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
    I got HTTP 500 Internal Server Error saying  "This website cannot display the page.  Most likely causes: 1. The website is under maintenance. 2. The website has a programming error."   I tried access ECP at https://localhost/ecp and
    I got the same problem.  Under either cases I was able to see the logon page of  ECP and I was able to enter my credential (e.g. domain\user name, password).  However I got HTTP 500 Internal Server Error at the next page.
    I appreciate your help, on my case.

    Hi,
    The link that Jatin points to should be this.
    https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
    Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
    %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
    If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
    Thanks.

  • Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

    I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
    I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
    Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
    If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
    My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did  before I removed the 2010 Exchange server?
    Thank you,

    Hi,
    From your description, I recommend you verify the following things for troubleshooting:
    1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
    2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
    For more information, here is a kb for your reference.
    Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
    http://support.microsoft.com/kb/2931385
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Error in Installing Exchange Server 2013 (w SP1) Mailbox Role on Windows Server 2012 R2

    Hi Team,
    Need urgent help in resolution of following error:
    Environment Details: VMware ESXi 5.5 (vMotion)
    Migration from Exchange Server 2007 (SP3 + RU13) to Exchange Server 2013
    Exchange Server: Exchange Server 2013 with SP1 (Latest Installation Media)
    OS: Windows Server 2012 R2 - Standard (Latest Installation Media)
    Exchange 2013 Roles: Seprated (Mailbox and CAS on Different VMs)
    Prerequisites: Installed
    Error: Installation gives Error at Step 10 during installation of Mailbox Service
    Error Details Below:
    Error:
    The following error was generated when "$error.Clear();
    if ([Environment]::OSVersion.Version.Major -ge 6)
    $WsbBinPath=$RoleInstallPath+"bin\wsbexchange.exe";
    $reg= join-path (join-path $env:SystemRoot system32) reg.exe;
    $servicecmd = join-path (join-path $env:SystemRoot system32) sc.exe;
    if ((get-service wsbexchange* | where {$_.name -eq "wsbexchange"}))
    if ((get-service wsbexchange).Status -eq "Running")
    Start-SetupProcess -Name:"$servicecmd" -Args:"stop wsbexchange";
    Start-SetupProcess -Name:"$servicecmd" -Args:"delete wsbexchange";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\CLSID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}\LocalServer32`" /t REG_SZ /d `"$WsbBinPath`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /t REG_SZ /d `"CExchangeHelper Class`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LocalService /t REG_SZ /d `"wsbexchange`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /v LaunchPermission /t REG_BINARY /d `"010004806000000070000000000000001400000002004c0003000000000014001f000000010100000000000512000000000018001f000000010200000000000520000000200200000000180003000000010200000000000520000000270200000102000000000005200000002002000001020000000000052000000020020000`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKCR\APPID\wsbexchange.exe`" /v AppId /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`" /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v `"Application Identifier`" /t REG_SZ /d
    Exchange /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WindowsServerBackup\Application Support\{76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}`" /v CLSID /t REG_SZ /d `"{D8A2E312-3B17-4293-B71E-CD72A7C04BF3}`"
    /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMarkDbRecoverable /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$reg" -Args:"add `"HKLM\Software\Microsoft\windows nt\currentversion\WSBAppExchangeHelper`" /v AutoMountOnPITRecovery /t REG_DWORD /d 1 /f";
    Start-SetupProcess -Name:"$servicecmd" -Args:"create wsbexchange binpath= `"$WsbBinPath`" type= own start= demand error= ignore obj= LocalSystem DisplayName= `"Microsoft Exchange Server Extension for Windows Server Backup`"";
    Start-SetupProcess -Name:"$servicecmd" -Args:"description wsbexchange `"Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server.`"";
    " was run: "Process execution failed with exit code 1.".

    Resolved ! :)
    Root Cause: The user account I was using had all the required privileges for Exchange Installation but was not having access to edit the registry of the server. Enable access to registry edit tools and you are good to go.
    As an alternate you can also try installing using Domain Administrator account if in case there is an IT Policy constraint in the former method.
    Thanks to all.

Maybe you are looking for