Exchange 2013 CU2 errors

Hi,

i have an issue trying to install exchange 2013 CU2, it has failed on step 7 and now the exchange environment is down, and im guessing I pretty much need to finish the CU2 update

It fails on step 7/11 with this error

Error:
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.".

Error:
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".
gerard_thusaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Questions for you:

1. Did you run the CU2 under Administrator privileges
2. Does the logged on account has org admin privileges in Exchange
0
gerard_thusaAuthor Commented:
1. Yes
2. Yes it is an enterprise admin (the builtin administrator account)
0
DipakCommented:
Referenced from below article.
http://blog.jasonsherry.net/2013/07/09/exchange-2013-rtm-cu2-released/

Error at step 7/11: A note has been added to the EHLO blog post on CU2 about this issue:

    To prevent issues during the installation or upgrade of Exchange 2013 RTM CU2, you should ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted”. Failure to do so could cause the Exchange 2013 server to be in an unusable state and some downtime could occur. To verify the policy settings, run the Get-ExecutionPolicy cmdlet from PowerShell on the Exchange 2013 Server(s). If the policies are NOT set to Unrestricted you should use the resolution steps in the following article to adjust the settings KB 981474.

Please refer the note in below mentioned technet's article for same.

http://blogs.technet.com/b/exchange/archive/2013/07/09/released-exchange-server-2013-rtm-cumulative-update-2.aspx


Maybe this could help.
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

gerard_thusaAuthor Commented:
no luck with the above!
0
gerard_thusaAuthor Commented:
Fixed via Microsoft support.

•      Environment – One combined role server
•      Symptom – Incomplete installation of Exchange 2013 CU2
•      Cause – multiple errors
•      Resolution –
-Run the setup throw the following error for system mailbox
     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.".

Error:
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".
-----------------------------
-Remove the system mailboxes and reboot
-Run setup /preparead
-Remove watermark buildtobuildupgrade
-Run setup again
-Failed with error script couldn't be found ManageScheduledTask.ps1

The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "The term 'E:\Exchange\Bin\ManageScheduledTask.ps1' 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.".
-------------
-Run the setup again fails to launch the wizard
[09-17-2013 12:30:31.0544] [0] Exception has been thrown by the target of an invocation.
[09-17-2013 12:30:31.0544] [0] The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception.
[09-17-2013 12:30:31.0544] [0] The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
-Check all exchange services disabled, and remote registry, windows management instrumentation,   windows modules installer
-Start remote registry, windows management instrumentation, windows modules installer
-Run the setup again fails
The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "The term 'E:\Exchange\Bin\ManageScheduledTask.ps1' 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.".
-copy the scripts from the scripts folder to the bin directory ManageScheduledTask.ps1
-run the setup again fails for discovery mailbox
The following error was generated when "$error.Clear();
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
              # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
              get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if($dbs.Length -ne 0)
                {
                  $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($mbxUser.Length -ne 0)
                  {
                    enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                  }
                }
              }
            }
            else
            {
              write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            }  
          }
        " was run: "Database is mandatory on UserMailbox.".

Error:
The following error was generated when "$error.Clear();
          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))
          {
            if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
            {
              # upgrade the discovery mailboxes to R5 version, this will fix the RecipientDisplayType property of the discovery mailbox which was wrong in R4.
              get-mailbox -RecipientTypeDetails DiscoveryMailbox -DomainController $RoleDomainController | where {$_.IsValid -eq $false} | set-mailbox -DomainController $RoleDomainController
              $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
              $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
              $mbxs = @( get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );
              if ( $mbxs.length -eq 0)
              {
                $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
                if($dbs.Length -ne 0)
                {
                 $mbxUser = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
                  if ($mbxUser.Length -ne 0)
                  {
                    enable-mailbox -Discovery -identity $mbxUser[0] -DisplayName $dispname -database $dbs[0].Identity;
                  }
                }
              }
            }
            else
            {
              write-exchangesetuplog -info "Skipping creating Discovery Search Mailbox because of insufficient permission."
            }  
          }
        " was run: "Database is mandatory on UserMailbox. Property Name: Database".
------------------
-Remove discovery mailbox
-Run setup /preparead fails because of watermark
-Remove watermark from registry
-Run setup again fails "pending reboot"
-Reboot
-Run setup /preparead
-Reboot
-Start the setup again
-Fail at step 7 to install the mailbox role
Error:
The following error was generated when "$error.Clear();
      start-SetupService -ServiceName MSExchangeDagMgmt

" was run: "Service 'MSExchangeDagMgmt' is disabled on this server.".
-Change the service type to automatic and start the setup again
-Setup completed successfully
-Cx confirmed that outlook and OWA works fine
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gerard_thusaAuthor Commented:
Fixed the issue myself, via Microsoft Support desk
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.