exchange 2013 cu2

I am trying to install Exchange 2013 CU2 (second node) so that I can setup DAG. I have follow and meet all prerequisites. On step 7 of 14 I get the following error.

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. Property Name: Database".

I did find some articles on how to resolve this issue, one was to make sure that certain services are running during the installation. The only one that I saw that would stop was the Remote Registry so I would continue to make sure that service was running.

Please advise,
Niles
Niles67Asked:
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.

dsnegi_25decCommented:
As per your error looks below article will help you.But these types of issues come due to arbitration mailboxes . So I will suggest removing arbitration mailboxes & then try to install again & arbitration mailboxes will automatically will recreate once you  will upgrade CU2



http://kickthatcomputer.wordpress.com/2013/02/28/exchange-server-2013-setup-fails-creating-mailbox-role/
Stelian StanIT Services ManagerCommented:
Make sure that the account you are using to install exchange has these permission: “Schema Admins”, “Domain Admins” and “Enterprise Admins”.

Second, why you are still using Exchange 2013 CU2 instead of using Exchange 2013 CU3? CU3 is available.
Niles67Author Commented:
I would use CU3 but my first Exchange node is still on CU2. I did however tried to upgrade from CU2 to CU3 on that node but it failed miserably around step 14 of 17. I did not cop y the error but will if it returns in my second attempt.

Will keep you posted.
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Niles67Author Commented:
Ok so here is the error when I try to update from CU2 to CU3 at step 13 of 17 (Mailbox role: Mailbox service).  Again, this is Exchange 2013.


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{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 -MessageTracking:$true -PstProvider:$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.".

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{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 -MessageTracking:$true -PstProvider:$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.".
Niles67Author Commented:
I have now reverted back to the previous Checkpoint in Hyper-V for my primary Exchange node. Everything appears to be fine but for some weird reason my Mailbox Database is not showing up in the Exchange Admin Center.

I do have a backup of the server but only from Dec 22, 2013. If I restore will users lose data or will the Outlook clients update the Mailbox Database?

Please advise,
Niles
Niles67Author Commented:
Whew! I think I figured my last post out. My Second exchange node attempt still had a Mailbox Database listed in ADSI. Removing that fix the primary Exchange node issue with the Mailbox Database not being listed in the Exchange Admin Center.

I still need help with the CU2 to CU3 upgrade.
Niles67Author Commented:
I have run into another issue and at this time I will be not be upgrading to CU3 until this one is resolved. I can no long send nor receive email inside or out. The Event Logs look pretty empty except for, "Unable to update the IP address on Isatap interface isatap.domain.local. Update Type: 1. Error Code: 0x490."

Thank you,
Niles
Niles67Author Commented:
My end goal has been solved by way of Office 365. So my solution is solved but the issue in this post is not. I have since decommissioned my on-premise exchange server.

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
Niles67Author Commented:
My end goal has been solved by way of Office 365. So my solution is solved but the issue in this post is not. I have since decommissioned my on-premise exchange server.
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.