Exchange 2013 SP1 Installation Error in "Mailbox Role: Transport service"

I tried an installation last week on a Windows Server 2008 R2 but was unable to get it to work. With the value of hindsight, I am inclined to think the error was more with the Web Site making EAC unavailable. I subsequently got it installed in my personal
lab environment by creating a VM with a fresh install of Windows Server 2008 R2 SP1. 
With this information I then went back to the customer's site and installed a clean version of Windows Server 2008 R2 SP1 in a virtual machine under Hyper-V. After installing all the prerequisites the install appeared to be going just fine but then in failed
in Step 7 with the following error:
The following error was generated when "$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
" was run: "Database is mandatory on UserMailbox.".
I know MS Exchange hides most of its information in AD so my suspicion is that the failed install on the real server has left some residual information in AD. Note that the original install on the real machine won't uninstall because the prior install attempt
hasn't finished.
The relevant part of the Exchange Setup Log is:
[07/22/2014 14:22:57.0593] [2] Active Directory session settings for 'Update-RmsSharedIdentity' are: View Entire Forest: 'True', Configuration Domain Controller: 'AWSDC.aws.local', Preferred Global Catalog: 'AWSDC.aws.local', Preferred Domain Controllers: '{
AWSDC.aws.local }'
[07/22/2014 14:22:57.0593] [2] User specified parameters:  -ServerName:'EXCHANGE'
[07/22/2014 14:22:57.0593] [2] Beginning processing Update-RmsSharedIdentity
[07/22/2014 14:22:58.0031] [2] RMS Shared Identity user 'CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042,CN=Users,DC=aws,DC=local' (originating server = 'AWSDC.aws.local') is being linked to computer 'CN=EXCHANGE,CN=Computers,DC=aws,DC=local' (originating
server = 'AWSDC.aws.local').
[07/22/2014 14:22:58.0156] [2] [ERROR] Database is mandatory on UserMailbox.
[07/22/2014 14:22:58.0156] [2] Ending processing Update-RmsSharedIdentity
[07/22/2014 14:22:58.0156] [1] The following 1 error(s) occurred during task execution:
[07/22/2014 14:22:58.0156] [1] 0.  ErrorRecord: Database is mandatory on UserMailbox.
[07/22/2014 14:22:58.0156] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/22/2014 14:22:58.0156] [1] [ERROR] The following error was generated when "$error.Clear(); 
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "Database is mandatory on UserMailbox.".
[07/22/2014 14:22:58.0156] [1] [ERROR] Database is mandatory on UserMailbox.
Does anyone have suggestions about what to do with ADSI Edit to fix the problems?
I think I am getting close to having a working Exchange!!

Hi,
Agree with Amit's suggestion. Please use the following cmdlet to re-home the arbitration mailbox which does not have database attribute stamped and check the result.
Set-Mailbox "FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042" -Arbitration -Database "xxx"
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 CU7 Installation crash on Mailbox role: Transport Service!!

    Hi
    I need some help, very urgent.
    I started cu7 Installation, and in the middle the Installation failed:
    Error:
    The following error was generated when "$error.Clear();
                # Apply XML Transforms to FIPS configuration file if schema changed
                Write-ExchangeSetupLog -Info "Applying XML Transforms to FIPS configuration";
                $FipsBinPath = [System.IO.Path]::Combine($RoleInstallPath, "FIP-FS\bin");
                [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigurationServerInterfaces.dll"));
                [Reflection.Assembly]::LoadFile([System.IO.Path]::Combine($FipsBinPath, "FSCConfigSupport.dll"));
                $configServer = New-Object Microsoft.FSC.Configuration.ConfigManagerClass;
                if(! $configServer)
                  Write-ExchangeSetupLog -Error "Configuration Server object could not be created.";
                else
                  try
                    $configServer.Upgrade();
                    Write-ExchangeSetupLog -Info "Configuration.xml was upgraded successfully";
                  catch
                    Write-ExchangeSetupLog -Error "Upgrade of Configuration.xml was unsuccessfull, $_";
                  # Stop the process if it is still running
                  # We silently continue because if process has already exited, Stop-Process will throw error
                  # Error is non-terminating and so can be suppressed
                  Stop-Process -processname FSCConfigurationServer -Force -ErrorAction SilentlyContinue;
              " was run: "System.Exception: Upgrade of Configuration.xml was unsuccessfull, Exception calling "Upgrade" with "0" argument(s): "Root element is missing."
       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)".
    I couldn't find any information about that
    Any sugggestion what I can do?
    Regards
    Peter

    Hi,
    If it is unable to start Transport service, please try the following method to solve this issue.
    Go to “C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Data”
    Deleted the file "Configuration.xml" and renamed "Configuration.xml.back" to Configuration.xml.
    Then try to re-install Exchange Mailbox Server.
    Note: remember to back up the file "Configuration.xml" and "Configuration.xml.back"
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange Installation Error on Mailbox role: Transport Service Step

    The error I receive occurs at 47% of the Mailbox Role: Transport Service installation.  The details of the error are as follows:
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainController
            " was run: "Active Directory operation failed on DC1.xxxxxx.xxxxxx.com. This error is not retriable. Additional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCH-MBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=xxxxxx,DC=xxxxxx,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    Also, when opening the setup log I have this:
    [12/26/2012 17:51:25.0809] [1] [ERROR] A naming violation occurred.
    [12/26/2012 17:51:25.0809] [1] [ERROR-REFERENCE] Id=ProvisionServerComponent___a16cb82f909348d3a32b9046f3bfb9ba Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [12/26/2012 17:51:25.0809] [1] Setup is stopping now because of one or more critical errors.
    [12/26/2012 17:51:25.0809] [1] Finished executing component tasks.
    [12/26/2012 17:51:25.0809] [1] Ending processing Install-BridgeheadRole
    [12/26/2012 17:51:25.0825] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [12/26/2012 17:51:25.0825] [0] End of Setup
    [12/26/2012 17:51:25.0825] [0] **********************************************
    I have done a ton of searches trying to find a resolution to this error and there are two pages with a similar issue for Exchange 2007 but after trying the solutions suggested, the installation still fails with the same error.
    http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploylegacy/thread/dfa9961a-9b20-4c17-ae4d-ebf44c66c18f/
    http://exchangetroubleshooting.blogspot.com/2011/05/unable-to-run-preparead-command.html/
    Some additional information:
    This is a clean installation of Exchange 2013 in a forest that has never had exchange.
    The domain and forest preparations run without errors and are at functional level of 2003.
    The Exchange server has all prerequisites installed for a Mailbox server role and is running on a VM with Server 2012 as the OS.
    This error occurs on other VMs as well that we are trying to implement as mailbox servers in the same forest.
    I am running the installation as an enterprise, schema, domain admin.
    Thanks for your help in advance.

    Yes.  I cleaned out Exchange with ADSIEdit so I could re-run the Prepare Schema, domain and all domains and then re-ran setup to show the output here.  But the install still failed.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareSchema
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:AZGT
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have b
    een detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
     For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.
    aspx
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\> .\setup /IacceptExchangeServerLicenseTerms /PrepareAllDomains
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Prepare Domain Progress                                                                          
    COMPLETED
    The Exchange Server setup operation completed successfully.
    PS F:\>
    PS F:\> .\setup /IAcceptExchangeServerLicenseTerms /mode:install /roles:Mailbox /TargetDir:"C:\Program Files\Microsoft\Exchange Server\V15"
    Welcome to Microsoft Exchange Server 2013 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Languages
    Management tools
    Mailbox role: Transport service
    Mailbox role: Client Access service
    Mailbox role: Unified Messaging service
    Mailbox role: Mailbox service
    Performing Microsoft Exchange Server Prerequisite Check
        Configuring Prerequisites                                                                        
    COMPLETED
        Prerequisite Analysis                                                                            
    COMPLETED
    Configuring Microsoft Exchange Server
        Preparing Setup                                                                                  
    COMPLETED
        Stopping Services                                                                                
    COMPLETED
        Copying Exchange Files                                                                           
    COMPLETED
        Language Files                                                                                   
    COMPLETED
        Restoring Services                                                                               
    COMPLETED
        Language Configuration                                                                           
    COMPLETED
        Exchange Management Tools                                                                        
    COMPLETED
        Mailbox role: Transport service                                                                  
    FAILED
         The following error was generated when "$error.Clear();
              if ($server -eq $null)
                set-ExchangeServerRole -Identity $RoleNetBIOSName -IsProvisionedServer:$true -DomainController $RoleDomainCo
    ntroller
            " was run: "Active Directory operation failed on DC1.XXXX.XXXX.com. This error is not retriable. Addi
    tional information: The object cannot be added because the parent is not on the list of possible superiors.
    Active directory response: 00002099: NameErr: DSID-0305109C, problem 2005 (NAMING_VIOLATION), data 0, best match of:
            'CN=EXCHMBOX1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=AZGT,CN=
    Microsoft Exchange,CN=Services,CN=Configuration,DC=XXXX,DC=XXXX,DC=com'
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS F:\>

  • Echange 2013 Installation Failing at Mailbox Role: Transport Service - 97%

    Hi all, let me just preface by saying thank you very much all your time, help, and patience!  
    So I've gone through the Exchange 2013 deployment guide, have installed all the pre-requisites, and am now trying to install Exchange 2013 CU7 on (2) 2008 R2 Enterprise SP1 servers.  Unfortunately it is failing on both of them at the Mailbox
    Role: Transport Service - 97% with the following error:
    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)".
    I've seen and heard the suggestions about enabling IPv6 on the servers as well as the Domain Controllers which I've done to no avail.  We do not have IPv6 addresses available on our network as we use IPv4 space, but I've heard just having the
    IPv6 adapter disabled is a lot of times the issue.  So the adapters are set to DHCP even though there's no IPv6 address for it to grab.  The 2008 R2 servers that I'm trying to install Exchange 2013 on are VMs on ESX.  Will the
    install fail even if it offers to pick up the installation where I left off?  Do I need to completely start from scratch?  Any help would be wonderful!

    Hi,
    Please verify whether the port 3268 listen on DC.
    Please try to enable GC role on all DCs.
    Then restart Exchange server, try to find whether Event 2080 exists with all DCs.
    Then try to re-install Exchange Server 2013 CU7.
    Thanks
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 SP1 Installation Errors I Cannot Resolve

    Good Afternoon All -
    Note:  I updated this post an hour after posting.  Still no solution, but please see updated info at end of this post)
    I'm trying to introduce Exchange into an existing, small environment.  The server I'm trying to install it onto is an SBS 2011 server (single server.)  Even though SBS comes with Exchange, I found out that it's installation was corrupted and someone
    had attempted to uninstall it before.  Yes, it's being installed onto a server with a DC.  I considered creating a Hyper-V VM on the server for Exchange, but thought it may be better to try to install directly onto server instead.
    Before I started, I made sure all Exchange data had been removed.  I checked for and deleted (if present) all Exchange-related objects in ADSI, ADU&C, files, and registry entries.
    When I try to install Exchange 2013 SP1, I get the below errors.  I know that some are easily resolved by installing pre-requisites - however - others aren't - especially the pending reboot one.  I've restarted the server many times when making
    changes or applying various updates and still get flagged to restart during installation.  I've tried the SBS 2011 repair disc as well, but had many issues with it.  In all honesty, the whole server needs to be wiped and re-installed, but
    cannot do at this point.
    Besides the errors below, I've zipped up the ExchangeSetupLogs folder and placed them in the link below.  Also below are system specs.  The only edit I made in them is a find/replace for server and domain name.
    ExchangeSetupLogs Folder
    System Specs
    Xeon E31270 3.4Ghz
    16gb RAM
    Windows Server 2011 SBS x64 (Domain Controller Role Installed & Used)
    C:\ - RAID 1 = 500gb
    D:\ - SATA HDD = 320gb
    E:\ - SATA HDD = 320GB
    Should I perhaps try to install to a VM on the server or think that would use too many unnecessary resources?
    Any help would be appreciated - Thanks!
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB2619234 (http://go.microsoft.com/fwlink/?LinkId=262359).
    Without this update, the Outlook Anywhere feature may not work reliably.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7RpcHttpAssocCookieGuidUpdateNotInstalled.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:
    The Windows component RSAT-Clustering isn't installed on this computer and needs to be installed before Exchange Setup can begin.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringInstalled.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from
    http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ben K.
    UPDATE
    I just tried fixing a few things and tried again.  Still no luck.  Below is what I changed as well as the errors received.  Only option was Retry.  Can I just not install it onto this environment?
    What I Changed
    Installed Unified Comm Managed API 4.0 (Required Uninstalling Speech Analysis app before it would install)
    Installed KB2619234 for Outlook Anywhere
    Installed 12 updates - Server fully patched
    Exchange Setup Errors
    Error:
    An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support
    Windows Server 2008 R2 SP1 or later and Windows Server 2012.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersion.aspx
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected
    in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Thanks Guys -

    Hi,
    Agree. Windows Server 2011 SBS x64 can be the problem.
    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

  • Installation of Exchange 2013 Failed on Mailbox Role Transport Service

    Hi All,
    Getting this error when trying to install a new exchange 2013 server. Thanks in advance
    Error:
    The following error was generated when "$error.Clear();
              if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
                Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
            " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
       at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi,
    This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
     directory service is corrupted.
    Please try to follow these steps to solve this problem.
        1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
    Click Start, click Run, type adsiedit.msc, and then click
    OK.
    Locate the Default Naming Context node, and then locate to the
    CN=Users container.
    Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
    Delete.
        2. Rerun the Exchange Server 2013 Mailbox role setup application.
        3. Create a new federated e-mail account by using the following command:
    New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
    If this issue persistes, please let me know.
    Best Regards.

  • Exchange 2013 SP1 prerequ errors

    Current installation. 4 Exchange 2013 machines on Server 2008 R2 platform (VM with Hyper-V), all have CAS and mailbox role installed. DAG across all for servers. 2 servers
    reside in main datacenter and 2 on a DR site.
    The Exchange installation is at CU 2 and working.<o:p></o:p>
    We have 2 domain controllers in the main datacenter (win 2008 R2) and 2 domain controllers in the DR site (Win 2012 R2).<o:p></o:p>
    DCDIAG checks out fine on all. Network is fine for all.
    Running SP1 installation on the Exchange servers in the DR site results in prerequisites in a bunch of errors which all stem from one root issue: <o:p></o:p>
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.<o:p></o:p>
    Running the same on the main site (DC= Win 2008 R2) completes prereq for SP1 with no errors.
    So the difference is that the 2 Exchange servers on the DR site have Win 2012 R2 for their domain controllers and fail.<o:p></o:p>
    Any advise?<o:p></o:p>
    Gerhard Waterkamp ACSLA Inc.

    No, I am not done.
    The situation is that on the DR site SP1 on 2 Exchange 2013 servers (on 2008 R2) using Windows 2012 R2 Domain controllers does not install.
    Error messages: ( a whole bunch more, but all related to this)
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    It is not resolved but still open.
    Gerhard Waterkamp ACSLA Inc.

  • Server Exchange 2013 SP1 installation on Hyper-V server

    Dear colleges, I seek your help with ExchangeServer 2013 installation on a Hyper-V server issue I've been having.
    Getting below errors during prerequisites check of XCHG SVR installation. Installation is done on a Hyper-V server. This server is member of a domain. I have also promoted this server to a Active Directory Domain Controller. In other words there's 2 AD DC
    - one is on the main server and the other on this one. The user the installation is run under has ALL required access rights. Please advise as this issue is getting on my nerves. I believe something is wrong setup on a AD DC part. Please suggest what to check
    and post on the forum, so somebody can just point out what I am doing wrong.  
    Error:
    The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
    Error:
    Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.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 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: Couldn't find the Enterprise Organization container.  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:
    The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.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
    Warning:
    Installing Exchange Server on a domain controller will elevate the permissions for Exchange Trusted Subsystem to domain administrators.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.WarningInstallExchangeRolesOnDomainController.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit:

    Got the same errors when ran on the main AD DC server:
    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.
    C:\Windows\system32>setup /ps /iacceptexchangeserverlicenseterms
    'setup' is not recognized as an internal or external command,
    operable program or batch file.
    C:\Windows\system32>h:
    H:\>setup /ps /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for
    installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                     FAILED
         The Active Directory schema isn't up-to-date, and this user account isn't a
     member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
         For more information, visit: http://technet.microsoft.com/library(EXCHG.150
    )/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
         Setup encountered a problem while validating the state of Active Directory:
     Couldn't find the Enterprise Organization container.  See the Exchange setup lo
    g for more information on this error.
         For more information, visit: http://technet.microsoft.com/library(EXCHG.150
    )/ms.exch.setupreadiness.AdInitErrorRule.aspx
         The forest functional level of the current Active Directory forest is not W
    indows Server 2003 native or later. To install Exchange Server 2013, the forest
    functional level must be at least Windows Server 2003 native.
         For more information, visit: http://technet.microsoft.com/library(EXCHG.150
    )/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
         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
    The Exchange Server setup operation didn't complete. More details can be found
    in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    H:\>

  • Exchange 2013 Sp1 OWA Error

    Hi,
    I installed a new exch2013 sp1 server and created few users.
    In that Administrator can able to access OWA & Admin Center without any error.
    Where Other users not able to access OWA- its prompting error Something Went wrong.
    I didn't check with Outlook client.
    I gone thru forums and reset the Virtual Directory, Cleared the Exchcanary data 0,1,2 using ADSI edit.
    Nothing works. Please help me to resolve this issue.
    Regards
    Dinesh

    Hi Dinesh,
    From your description, I recommend you use the Test-ServiceHealth cmdlet to check if all services Exchange server needed are started. If no, please start the services Exchange server needed and check the result.
    What's more, please make sure that OWA is enabled for other users.
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2013 SP1 Installation

    Hello
    After installation on windows domain server/controller 2012 R2.
    I got this message:
    VERBOSE: Connecting to GolfServer.GOLFKLUB.local.
    New-PSSession : [golfserver.golfklub.local] Connecting to remote server golfserver.golfklub.local failed with the follo
    wing error message : The WinRM client cannot process the request. The WinRM client tried to use Kerberos authentication
     mechanism, but the destination computer (GolfServer.GOLFKLUB.local:80) returned an 'access denied' error. Change the c
    onfiguration to allow Kerberos authentication mechanism to be used or specify one of the authentication mechanisms supp
    orted by the server. To use Kerberos, specify the local computer name as the remote destination. Also verify that the c
    lient computer and the destination computer are joined to a domain. To use Basic, specify the local computer name as th
    e remote destination, specify Basic authentication and provide user name and password. Possible authentication mechanis
    ms reported by server:   Digest Negotiate For more information, see the about_Remote_Troubleshooting Help topic.
    I tried to find solution on many forums and I also check other erros in Event Log and Kerberos...
    I also cannot connect to Administration center.
    Can anyone help me, please.
    Thank you very much

    Hi VachtiCZ,
    Thank you for your question.
    By the error, we could do the following steps to troubleshoot:
    If there are another application which is installed on GolfServer.GOLFKLUB, we could open IIS and navigate Default Web Site to check if
     the port 80 has been used by another application. if that we could change the port of application.
    Check if we have disable the Kerberos authentication
    a.  Run gpedit.msc in Run
    b. Navigate Computer Configuration>Administrative Templates>Window Components>Window Remote Management(WinRM)>WinRM Service
    c. Check if  we have selected “Enable” on Disallow Kerberos authentication
           d. Then we could use “gpupdate /force” to update group policy.
    I also cannot connect to Administration center
    A: It was caused by the above error. So if we solve this error, we will access EAC. if there are coexistence in organization, for example Exchange 2010, we could refer to the following link to access EAC:
    https://technet.microsoft.com/en-us/library/jj150562(v=exchg.150).aspx
    In addition, I strongly suggest we didn’t install Exchange server on Domain controller on production.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim

  • Exchange 2013 SP1: Fix for failing MSExchangeTransport service

    We had a newly updated Exchange 2013 SP1 that would not start the Transport service
    "Netstat -b" showed that a service was listening to port 25 on all IP's (0.0.0.0:25) and when the service could not get the port, it would die, and Exchange would attempt to restart it over and over.
    After many tears, I found this solution: 
    Through the console or the ECP, check the Frontend receive connectors and find the one that is listening on 0.0.0.0:25, which is probably the Default Frontend Receive.  Disable it.
    Restart the MSExchangeTransport and MSExchangeTransportFrontEnd services.
    If both services restart normally, troubleshooting is complete.
    We use several custom connectors carried forward from the previous installation, which was SBS 2008.  If this applies to you, take notice.

    Normally, the Default Frontend Receive Connector (0.0.0.0:25) is the messaging entry point for your organization (I am assuming that you have a single MBX/CAS server).
    1. If you disable the Default Frontend Receive Connector (0.0.0.0:25), you block inbound email.
    2. Most probably, the cause for your problem are the Custom Receive Connectors. Check their type, and if it is Hub Transport, delete and re-create them as Front End Receive connectors.
    Step by Step Screencasts and Video Tutorials

  • Error in step 8 - transport service

    hi there,
    i need some help here... in the instalation of exchange server 2012 apear this error on mailbox roles: transport service.
    how i renew the certificate? that the program ask...
    thanks.
    Error:
    The following error was generated when "$error.Clear(); 
              Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
              if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
                Install-AuthCertificate -DomainController $RoleDomainController
            " was run: "System.Security.Cryptography.CryptographicException: The certificate is expired.
       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.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi John,
    Based on my experience, this error usually is caused by incorrect system time.
    And as we know first place to check is ExchangeSetup.log, open the log file and press Ctrl+End, you will reach the end of the file the place where our error will be available. Then check the
    validity of certificate(Start time and End time), if the certificate is valid, please make sure your system time is correct.
    And if the certificate is expired, you need to renew the certificate.
    Click the link below for more information:
    Renewing Certification Authorities
    http://technet.microsoft.com/en-us/library/cc962077.aspx
    Hope it can be helpful.
    Best regards,
    Eric

  • Exchange 2013 SP1 - Edge Tranport Role

    Hi.
    When Exchange 2013 was released only CAS & Mailbox roles where available. Hub & Edge Transport server roles were discontinued.
    Now with Exchange 2013 SP1, the edge transport role has came back.
    Question:
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    2. will there any be problems without an Edge Transport ?
    Thanks,
    Paul

    Hi ,
    Please find the below mentioned points .
    1. Can I deploy a new Exchange 2013 Infrastructure without the Edge Transport Role. This will be a fresh deployment.
    I plan to have a UTM with spam blocking at the perimeter instead of the Edge Server?
    Answer :
    Just ensure that the product is having all the features as you need on your side .There is not necessary to have a an edge server in all the exchange environment's. Moreover Gateway and anti spam products will differ as per the company requirements.
    2. will there any be problems without an Edge Transport ?
    Answer :
    If you are having any one the anti spamming solution to have all the emails scanned before it reaches the exchange server then it will be good .
    Just ensure that the anti spamming product what you are going to use is mainly doing the reverse dns lookup
     and spf look up .With the help of that we can able to avoid large no of forged emails.
    Regards
    S.Nithyanandham

  • Exchange 2013 SP1: messages still stuck in Drafts folder

    Hello!
    The second question on Exchange 2013SP1 that I asked when I was working with Exchange 2013:
    New lab setup: a Windows 2012R2 DC (server1) + Exchange 2013SP1 (server2). Exchange 2013SP1 installation completed successfully. I created three mailboxes: [email protected], [email protected], [email protected]
    Now when I'm trying to send a message (from user1 to user, for example) it gets stuck in the Drafts folder.
    I manually set up my DNS server in ECP:
    as described here: http://thoughtsofanidlemind.com/2013/03/25/exchange-2013-dns-stuck-messages - but the problem persists.
    And this problem
    "On every single installation / that I’ve done of Exch 2013 in multiple labs, when set as a single mailbox server, messages have never been able to leave the “drafts” folder. Not a single instance where it worked correctly. Messages
    leaving a mailbox, destined to the exact same server do not route, let alone use any send-connector to leave the organization.
    Now, take it to the next step, and install a second mailbox server. The very second that services finish installing, and AD replication (if using multiple sites) settles down, mail-flow on the first server starts working absolutely flawlessly. Whatever
    changes are done to AD from the second mailbox server being installed in regards to mailflow, it completely resolves the issues of the first server holding onto the messages."
    ...is exactly the same as mine...but in Exchange 2013 SP1 ( Messages leaving a mailbox, destined to the exact same server do not route).
    Can anybody from MS tell me if it's a bug or by design??? I've NEVER had an Exchange installation without this issue...
    Thank you in advance,
    Michael

    Hi,
    I have never come across such a situation in my labs(all roles install in a single server), and there is no Microsoft documentation mentioned this issue.
    In addition, Microsoft does not oppose the Exchange installed on a single server(although not recommend).
    I recommend you check if all the exchange services are running, and try to restart Exchange Mailbox Transport Submission & Exchange Mailbox Assistants services.
    Hope this helps!
    Thanks.
    Niko Cheng
    TechNet Community Support

  • Error in moving exchange 2010 mailboxes to Exchange 2013 SP1 during migration

    Dear All,
    We were running Exchange 2010 SP3 with MBX/HT/CAS role in single server. Now we are migrating our exchange 2010 to Exchange 2013 SP1. After configuring co-existence and during the mailbox move from Exchange 2010 to Exchange 2013 SP1, we are facing below
    error. Please help to troubleshot. As per our search on net, people were suggesting that it can be due to not able to resolve NetBIOS name. We checked same and we are able to ping both servers by NetBIOS and FQDN names.
    [PS] C:\Windows\system32>New-MoveRequest -Identity
    '[email protected]' -TargetDatabase "CI-DB01"
    MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
    Diagnostic context:
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1722
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 323
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1237
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 313
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 311
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 3
        Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 22964
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[1]: Pointer val: 0x0
        Lid: 15000   dwParam: 0x0 Msg: EEInfo: prm[2]: Pointer val: 0xFE01A8C000000000
        Lid: 62184
        Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 6004
        Lid: 12696   dwParam: 0x0 Msg: EEInfo: Generation Time: 0414-08-21T09:10:43.8970000Z
        Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 18
        Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 10060
        Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 318
        Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 0
        Lid: 53361   StoreEc: 0x977
        Lid: 51859
        Lid: 33649   StoreEc: 0x977
        Lid: 43315
        Lid: 58225   StoreEc: 0x977
        Lid: 39912   StoreEc: 0x977
        Lid: 54129   StoreEc: 0x977
        Lid: 50519
        Lid: 59735   StoreEc: 0x977
        Lid: 59199
        Lid: 27356   StoreEc: 0x977
        Lid: 65279
        Lid: 52465   StoreEc: 0x977
        Lid: 60065
        Lid: 33777   StoreEc: 0x977
        Lid: 59805
        Lid: 52487   StoreEc: 0x977
        Lid: 19778
        Lid: 27970   StoreEc: 0x977
        Lid: 17730
        Lid: 25922   StoreEc: 0x977
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : [Server=Exch01,RequestId=f6886977-92f1-4148-991b-aa76b449aff5,TimeStamp=8/21/2014 9:1
       0:43 AM] [FailureCategory=Cmdlet-RemoteTransientException] 7FCC37,Microsoft.Exchange.Management.RecipientTasks.New
    MoveRequest
      + PSComputerName        : Exch01.domain.local
    Please help as we are stuck here!!
    Thanks in advance!!

    Can yo ping server by name not by FQDN? e.g. ping server1.
    Make sure firewall/antivirus not blocking communication. Disable antivirus and try
    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