Error During Exchange 2013 Mailbox Transport Role Install On Server 2012

I was installing Exchange 2013 on Server 2012.  The server is not a DC, but is a member of a domain with a 2008 R2 functional level, and I was logged in as a domain admin.  There has never been an Exchange instance on this domain.  I got past
the prerequisite checks, and the installer showed 15 steps, so I walked away.  When I came back, I saw this:
Step 8 of 15: Mailbox role: Transport service
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: "Unable to set shared config DC.".
The only option on the screen was exit, so I did.  I checked the start menu, and there were two new Exchange icons, but I did not click them.  I ran the installer again, and it detected an incomplete install, the only option was to click next to
finish the install, so I clicked next.  This time, I eventually got the same error, except the screen showed "Step 8 of 15: Mailbox role: Transport service."  I did install some Exchange 2010 prerquisites on the server before Exchange Server 2013
came out, and I can rebuild the server and try the install again if that would be best, but I thought I should post here first and try to work through this since the product is so fresh.  Any suggestions?

I've tried three times since my last post, following
http://msexchange2010.info/archives/2330 as closely as possible the most recent time.  I am consistently getting the same error that appears to imply I don't have write access to the domain.  I don't understand this, because I am using the
same domain admin account I have been using all along.  Nonetheless, here is the powershell output starting with the first Exchange setup.exe step (all other steps were already performed, all available updates were installed, and the server was rebooted
prior to this):
Windows PowerShell
Copyright (C) 2012 Microsoft Corporation. All rights reserved.
PS (domain admin home)> D:
PS D:\> .\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
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 D:\> .\Setup.exe /PrepareAD /OrganizationName:PRD-INC /IAcceptExchangeServerLicenseTerms
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 D:\> .\Setup.exe /Mode:Install /Roles:ClientAccess, Mailbox, ManagementTools /t E:\Exchange /IAcceptExchangeServe
rLicenseTerms
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
Client Access role: Front End Transport service
Client Access role: Client Access Front End 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 COMPLETED
Mailbox role: Client Access service COMPLETED
Mailbox role: Unified Messaging service COMPLETED
Mailbox role: Mailbox service FAILED
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$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)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox.".
The following error was generated when "$error.Clear();
if ($RoleIsDatacenter -ne $true)
if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
$sysMbx = $null;
$name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
$dispName = "Microsoft Exchange";
Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
$mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
if ($mbxs.Length -eq 0)
Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
$dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
if ($dbs.Length -ne 0)
Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
$arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
if ($arbUsers.Length -ne 0)
Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
$sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0
].Identity;
else
if ($mbxs[0].DisplayName -ne $dispName )
Write-ExchangeSetupLog -Info ("Setting DisplayName=$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)
# We need 1 GB for uploading large OAB files to the organization mailbox
Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions
:$true -MailRouting:$true -MaxSendSize 1GB -Force;
else
Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
else
Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
" was run: "Database is mandatory on UserMailbox. Property Name: Database".
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
PS D:\>
I am cleaning out in ADSI and rebuilding the server for now, because the server is behaving oddly (not as oddly as it was with 6GiB, but oddly, nonetheless).  I probably won't try to install Exchange again before tomorrow.  What should I do to prevent
encountering the above again and/or if I encounter it again?

Similar Messages

  • Error during Exchange 2007 mailbox provisioning with IDM 8.1.1.1

    Hi
    We want to create Exchange 2007 mailboxes from IDM.
    When we let Exchange set the SMTP address (EmailAddressPolicyEnabled=true), it works fine
    But when we set the SMTP address in IDM with the attribute PrimarySmtpAddress (and EmailAddressPolicyEnabled=false) there are an error and an information in the provisioning task
    Error : PowerShell:6c13f14c-3825-4064-a585-48b4756de3a3 is not a mailbox user
    Information : Added exchange mailbox to the user based on the RecipientType change from: 'User' to: 'UserMailbox'
    We see that the mailbox has the SMTP address set by Exchange.
    After 5mn, the task ends successfully and we see that the SMTP address is the one set by the IDM attribute PrimarySmtpAddress.
    We guess that this error is caused by the active directory replication delay between controllers.
    Does anybody know how to solve this problem ?
    Thank you

    Hi Patrick
    Thank you for your answer.
    The cmdlet enable-mailbox can be used with the PrimarySmtpAddress option and, in this case, the EmailAddressPolicyEnabled option is automatically set to false.
    Cf. the MS technet help : "The PrimarySmtpAddress parameter specifies the primary SMTP address for the mailbox. By default, the primary SMTP address is generated based on the default e-mail address policy. If you specify a primary SMTP address by using this parameter, the command sets the EmailAddressPolicyEnabled attribute of the mailbox to $false, and the e-mail addresses of this mailbox aren't automatically updated based on e-mail address policies."
    I have tested this option on our Exchange 2007 environment and it works fine.
    In IDM if PrimarySmtpAddress is used but not EmailAddressPolicyEnabled, there is an error : "PowerShell:The e-mail addresses for this recipient are automatically generated based on e-mail address policies. To modify the primary SMTP address for this recipient, you must disable automatic updating of e-mail addresses based on e-mail address policy”
    If PrimarySmtpAddress is used and EmailAddressPolicyEnabled is set to false, then the log shows that 2 powershell commands are run by the gateway, the second immediately after the first.
    Enable-Mailbox with the parameters -Identity and -Database, run with no error
    Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with the error “…is not a mailbox user.”
    After 5 mn (the retry delay) another powershell command is run :
    Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with no error.
    The solution would be that IDM, when PrimarySmtpAddress is set, runs only the command Enable-Mailbox with the parameters PrimarySmtpAddress, which set automatically EmailAddressPolicyEnabled to FALSE
    Gilles

  • Setup Error 1603 with Exchange 2013 incl. SP1 on Windows Server 2012 R2

    Hello all,
    i've started the installation of a new Exchange 2013 with SP1 in a Windows 2012 R2 environment. New AD, no Exchange previously installed. Exchange ISO from
    Volume Licensing Service Center (Filename: SW_DVD9_Exchange_Svr_2013w_SP1_MultiLang_Std_Ent_MLF_X19-35118.iso)
    All the prerequisites are ok, installed also the “Unified Communications Managed API (UCMA) 4.0″ as requested.
    Setup.exe i've started with "run as administrator" and all went well, until Step 11 of 15 (Mailbox role:Mailbox service).
    Setup stopped and gives an error:
    The following error was generated when "$error.Clear(); 
    Install-MsiPackage `
    -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi")) `
    -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
    -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-nb-NO.msilog"))
    " was run: "Installing product F:\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.nb-NO.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'The cabinet file 'EngineInstanceData.cab'
    required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.'.".
    Exchange ECP is not working (HTTP Error 404.0 - Not Found), EMS (Shell) is working - if i try a get-mailboxserver it gives me the correct servername.
    Exchange Services are running:
    Running MSExchangeADTop... Microsoft Exchange Active Directory...
    Running MSExchangeAntis... Microsoft Exchange Anti-spam Update
    Running MSExchangeDelivery Microsoft Exchange Mailbox Transpor...
    Running MSExchangeDiagn... Microsoft Exchange Diagnostics
    Running MSExchangeEdgeSync Microsoft Exchange EdgeSync
    Running MSExchangeHM Microsoft Exchange Health Manager
    Stopped MSExchangeIMAP4BE Microsoft Exchange IMAP4 Backend
    Running MSExchangeIS Microsoft Exchange Information Store
    Running MSExchangeMailb... Microsoft Exchange Mailbox Replication
    Running MSExchangeMigra... Microsoft Exchange Migration Workflow
    Stopped MSExchangePOP3BE Microsoft Exchange POP3 Backend
    Running MSExchangeRPC Microsoft Exchange RPC Client Access
    Running MSExchangeServi... Microsoft Exchange Service Host
    Running MSExchangeSubmi... Microsoft Exchange Mailbox Transpor...
    Running MSExchangeTrans... Microsoft Exchange Transport
    Running MSExchangeTrans... Microsoft Exchange Transport Log Se...
    Running MSExchangeUM Microsoft Exchange Unified Messaging
    So, how to proceed ? Try to download a new ISO for Exchange 2013 incl. SP1 and run the setup again ? 
    What happens to the existing  (corrupt) installation of the exchange which is not working ?
    Thanks for your help
    Bruno

    Hi,
    From the error message, the cabinet file 'EngineInstanceData.cab' required for this installation is corrupt and cannot be used. I'm afraid you have to download a new ISO for Exchange 2013 incl. SP1 and run the setup again.
    If it still doesn't work, I recommend you remove the failed Exchange server installation, then re-install Exchange server.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Error Calculating InstanceID when installing SQL Server 2012 SP1 on Windows 7 Home Premium SP1

    Hello...
    I know this issue has been on several tickets but I have not been able to find a satisfactory solution.  I am receiving error 0x85640001 "...error calculating instanceid" when I attempt to install SQL Server 2012 Developer Edition DVD. 
    I have downloaded the ISO for the enterprise evaluation product and tried burning it to a DVD-RW and decompressing the ISO to my desktop for installation without success.
    The log files do state the setup process runs into a badimageformat exception.
    I had SQL Server 2008 Developer edition installed on this laptop, but I have completely removed all prior SQL Server instances (using the uninstall wizard in Control Panel).
    Please let me know what you suggest to correct this problem.
    Thank you for your help!

    Hello,
    1. Uninstall any SQL Server 2012 component using Control Panel.
      2. Download the Evalaution Edition from the following link:
    http://www.microsoft.com/en-us/download/details.aspx?id=29066
      3.Perform an edition upgrade from evaluation edition to developer edition using the current media.
    http://technet.microsoft.com/en-us/library/cc707783(v=sql.110).aspx
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Exchange 2013 Mailbox Role Installation Error

    Hi All,
    I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
    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: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
    . HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
       at System.DirectoryServices.DirectoryEntry
       at System.DirectoryServices.DirectoryEntry.Bind()
       at System.DirectoryServices.DirectoryEntry.RefreshCache()
       at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
       at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
       at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
       at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
       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)".
    Any views on this is appreciated.
    Regards
    Boniface
    Senior Systems Administrator

    Hi,
    After uninstalling the IIS, please run the following command to install prerequisites.
    Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
    Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
    Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
    Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
    In addition, please disable any third-part software for troublwshooting.
    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

  • OWA Error after Exchange 2010 Mailbox move to 2013

    Hello,
    We have been experiencing an issue when we move a users mailbox from Exchange 2010 on-prem to Exchange 2013 on-prem.  As a domain admin I was able to access the users mailbox via OWA 2010 with out issues.  However, now that they have been
    moved over to 2013 I am getting the following error message:
    X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
    X-OWA-Version: 15.0.995.28
    X-FEServer: CASServer
    X-BEServer: Mailboxserver.domain.com
    Date: 1/29/2015 5:27:38 PM
    Full Access permissions appear on the mailbox still via the 2013 ECP console for my account.  I have tried running the
    Set-Mailbox UserName -ApplyMandatoryProperties command but receive a message that no settings have been modified.
    I have also tried to remove/re-add inheritable permissions on the users AD account to no avail.
    I have a large group of mailboxes to move over to 2013 and hoping their is a decent solution out there to prevent this from happening.
    Greatly appreciate any feedback on this request.
    Cheers

    Hi,
    Please re-add the full access permission for the administrator:
    Get-Exchange Server "servername" | Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights FullAccess
    If Administrator is still located in Exchange 2010 and has the full access permission to an Exchange 2013 mailbox ([email protected]) which is moved from Exchange 2010, please use the following URL to open the mailbox:
    https://Exch13.domain.com/owa/[email protected]/
    Then check whether the issue persists.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Cumulative Update 5 Install Issue

    I have tried installing Exchange 2013 Cumulative Update 5 on our server but it is failing at the Mailbox role: Transport Service section with the following error. I am running the command prompt as Administrator. Any help would be great. 
    Error: The following error was generated when "$error.Clear(); Set-LocalPermissions 
    " was run: "System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. 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.SetLocalPermissions.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String
    funcName, Action func, Boolean terminatePipelineIfFailed)".

    Hi Tim,
    From the Exchange setup log description, there is only one error, "Attempted to perform an unauthorized operation.". The error indicates that it is a permission problem. I would like to verify if you add the account to the local admin group. If no, please
    add the account to the admin group and continue to install the CU5.
    If the issue persists, I recommend you download a new CU5 for Exchange 2013 and reinstall it to check the result.
    For you convenience:
    Cumulative Update 5 for Exchange Server 2013
    http://www.microsoft.com/en-us/download/details.aspx?id=43103
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact 
    [email protected]
    Amy Wang
    TechNet Community Support

  • Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

    Hi Team,
    I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
    Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
    open and throws an error of some "cannot open set of folders".
    Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
    Kindly share some KB or tip. Any help is appreciated. Thank You.
    Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

    I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 mailbox added to the CAS array

    We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
    installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
    in the array. When installing the mailbox role, we did not choose the client access role but after
    the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
    we did not choose the client access role. How does this happen, and to proceed ?

    I see the same thing in my lab:
    Get-ClientAccessArray | FL
    RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
    ExchangeLegacyDN  : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                        tlook.wingtiptoys.ca
    Fqdn              : Outlook.wingtiptoys.ca
    Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
    SiteName          : Default-First-Site-Name
    Members           : {EXCH-2010, EXCH-2013}
    AdminDisplayName  :
    ExchangeVersion   : 0.1 (8.0.535.0)
    Name              : Outlook.wingtiptoys.ca
    DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                        ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
    Identity          : Outlook.wingtiptoys.ca
    Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
    ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
    ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
    WhenChanged       : 4/12/2014 12:51:18 PM
    WhenCreated       : 4/12/2014 12:51:18 PM
    WhenChangedUTC    : 4/12/2014 7:51:18 PM
    WhenCreatedUTC    : 4/12/2014 7:51:18 PM
    OrganizationId    :
    OriginatingServer : DC-1.wingtiptoys.ca
    IsValid           : True
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2013 "451 4.7.0 Temporary server error. Please try again later. PRX5" Error

    I know this error message is discussed on other topics on several different forums including TechNet but I ended up opening this as the suggestions that solved the problems with the previous threads dos not work on mine. 
    We have a ticketing software that runs on client computers which sends mails to local Exchange server for notifications using port 25. 
    Approximately 1 out of 5 mails end up getting the "451 4.7.0 Temporary server error. Please try again later. PRX5" error. I have confirmed this by running Wireshark on the clients, saw the exact error message. This has been replicated with
    several client machines running Win7 & 8.
    I have tried several solutions to this, one of them being this:
    http://www.techieshelp.com/exchange-2013-451-4-7-0-temporary-server-error-please-try-again-later-prx5/
    I still get the same error from time to time after doing this, so it is not the issue. All the records in local hosts file, receive connector is listening to port 25 on all IPv4 addresses. 
    The server has a single NIC and the DNS lookups are done through that single NIC, not through "All available adapters" as set by default on ECP.  
    Almost everyone seems to be convinced that this is related to DNS but looking at how fast I get the error message, it doesn't look like it's waiting for a timeout (maybe unrelated, just an observation). Do you think it is possible that the DNS servers themselves
    are causing this issue? 
    Also, I see Event 5504 on the primary dns server almost all of them coming from the mail server, saying that the DNS query was invalid. It may be related. 
    Additional Notes:
    - CU6 is applied but did not fix the issue. 
    - None of these have solved it for me: http://www.servolutions.com/support/articles/Temporaryservererror2013.htm 
    - Receive Connectors do listen to separate ports 25 & 2525 -> There is a single instance of both Transport Service and Edge Transport service respectively. Anonymous users are accepted in both Receive connectors. 

    Thank you for your post.
    This is a quick note to let you know that we are performing research on this issue.
    Niko Cheng
    TechNet Community Support
    Thank you Niko. I'm looking forward to your answer as I've gone through every post regarding this and none of them worked. I will let everyone know if I can find a solution to this. 

  • How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

    Hi All,
    we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013  and i have to add the 2013
    servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
    Thanks, Venkatesh. &quot;Hardwork Never Fails&quot;

    For a step by step follow the deployment assistant
    http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Error during copy of partner: Partner role VN

    I am creating an Inbound Delivery from an Outbound using SPED output type on the Outbound Delivery.
    When I process the output using vl71 I get the following error.
    Can anyone tell me what im missing.
    The same scenario works for other plants except this one, its between 2 new plants in a new company code.
    What do i do?
    Type Message text
         Object 0080011663
         Output type: Stk.Transf.CrteDeliv
         Processing log for program /SPE/STO_ID_PROCESSING routine STO_ID_CREATION
         Error during copy of partner: Partner role VN
         Error during copy of partner: Partner role VN
         Error during copy of partner: Partner role VN
         No inbound delivery created for the replenishment delivery 0080011663

    This issue has been resolved.
    I recreated the Vendor from scratch and switched plant config settings to the new Vendor and entered the new vendor number in the Customer and retried the process. It works.
    So i think there was something wrong with the initial Vendor setup.(Though i checked view by view and didnt find any difference)

  • Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

    I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
    for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
    the following command:
    Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
    The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
    how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
    Many thanks.

    Hi Dennis,
    Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
    Please check your connection authentication. We can  run the following command to set your Outlook Anywhere for Exchange 2013:
    Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
    In Outlook side, please ensure the following settings in Account Settings:
    In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

    Hello guys,
    I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
    When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
    When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
    We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
    What should I check and configure to make it work?

    Hi,
    I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact  EMC supplier to improve it.
    By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
    A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    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]
    Jim Xu
    TechNet Community Support

  • Error during copy of partner: Partner role SP Message no. VL864

    while we are doing delivery in consignment issue process i am getting "Error during copy of partner: Partner role SP"
    message no.VL864
    i was tried previous posts in scn with this message no but i didn't get suitable answer.so scn experts do the needfull
    best regards,
    venkateswar dama

    Hi,
    Have you read the thread below?
    http://scn.sap.com/thread/1831385
    Also if not resolved then I suggest you to better to post this issue in SD forum.
    Regards
    Shishir

Maybe you are looking for