none
Exchange 2010 SP1 update issues RRS feed

  • Question

  • Hey guys,

    like the title says, yesterday i tried to upgrade our exchange 2010 with sp1, but kept getting an error at the mailbox section. I beleive it has something to do with a "system mailbox" or the DB.

     

    Here is the end of the error log, i can post the entire log if needed:

     

     

    [08/26/2010 09:33:10.0993] [2] [WARNING] The object Example.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} has been corrupted, and it's in an inconsistent state. The following validation errors happened:

    [08/26/2010 09:33:10.0993] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:10.0993] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:10.0993] [2] Ending processing get-mailbox

    [08/26/2010 09:33:11.0040] [1] Executing: 

              if ($RoleIsDatacenter -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."

                }  

              }

     

    [08/26/2010 09:33:11.0040] [2] Active Directory session settings for 'test-ExchangeServersWriteAccess' are: View Entire Forest: 'True', Configuration Domain Controller: 'sca-bes.Example.com', Preferred Global Catalog: 'home.Example.com', Preferred Domain Controllers: '{ sca-bes.Example.com }'

    [08/26/2010 09:33:11.0040] [2] Beginning processing test-ExchangeServersWriteAccess -DomainController:'sca-bes.Example.com' -ErrorAction:'SilentlyContinue'

    [08/26/2010 09:33:11.0133] [2] Used domain controller sca-bes.Example.com to read object DC=Example,DC=com.

    [08/26/2010 09:33:11.0274] [2] Used domain controller sca-bes.Example.com to read object CN=Exchange Servers1,OU=Microsoft Exchange Security Groups,DC=Example,DC=com.

    [08/26/2010 09:33:11.0445] [2] The current user has write access to Exchange Servers group.

    [08/26/2010 09:33:11.0445] [2] Ending processing test-ExchangeServersWriteAccess

    [08/26/2010 09:33:11.0508] [2] Active Directory session settings for 'Get-Mailbox' are: View Entire Forest: 'True', Configuration Domain Controller: 'sca-bes.Example.com', Preferred Global Catalog: 'home.Example.com', Preferred Domain Controllers: '{ sca-bes.Example.com }'

    [08/26/2010 09:33:11.0508] [2] Beginning processing get-mailbox -RecipientTypeDetails:'DiscoveryMailbox' -DomainController:'sca-bes.Example.com'

    [08/26/2010 09:33:13.0379] [2] Active Directory session settings for 'Set-Mailbox' are: View Entire Forest: 'True', Configuration Domain Controller: 'sca-bes.Example.com', Preferred Global Catalog: 'home.Example.com', Preferred Domain Controllers: '{ sca-bes.Example.com }'

    [08/26/2010 09:33:13.0379] [2] Beginning processing set-mailbox -DomainController:'sca-bes.Example.com'

    [08/26/2010 09:33:15.0001] [2] Searching objects of type "ADUser" with filter "(RecipientTypeDetails Equal DiscoveryMailbox)", scope "SubTree" under the root "$null".

    [08/26/2010 09:33:15.0235] [2] Previous operation run on domain controller 'sca-bes.Example.com'.

    [08/26/2010 09:33:15.0235] [2] Preparing to output objects. The maximum size of the result set is "1000".

    [08/26/2010 09:33:15.0610] [2] Searching objects "Example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}" of type "ADUser" under the root "Example.com/Users".

    [08/26/2010 09:33:15.0875] [2] Previous operation run on domain controller 'sca-bes.Example.com'.

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Update Recipient object "Example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}" with ConfigurationDomainController "sca-bes.Example.com", DomainController "sca-bes.Example.com", GlobalCatalog "<null>".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Contacts".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Groups".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Rooms".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Users".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\Public Folders".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\Default Global Address List".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Recipients(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Mailboxes(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Groups(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Mail Users(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\All Contacts(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\Groups(VLV)".

    [08/26/2010 09:33:15.0890] [2] [Microsoft Cmdlet Extension Agent] Found Address List "\Mailboxes(VLV)".

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Remove Address List "Example.com/Configuration/Deleted Objects/All Users

    DEL:75c25b9d-553e-4c71-81e3-a5e2aaa90092" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Remove Address List "Example.com/Configuration/Deleted Objects/Default Global Address List

    DEL:af307a25-6736-44fb-97ed-fe80c951b52b" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Remove Address List "Example.com/Configuration/Deleted Objects/All Recipients(VLV)

    DEL:8f0644ca-e9eb-448d-885e-6ff011c159f6" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Remove Address List "Example.com/Configuration/Deleted Objects/All Mailboxes(VLV)

    DEL:64b80b6a-3cef-4438-86d0-7d44e2ee5494" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Remove Address List "Example.com/Configuration/Deleted Objects/Mailboxes(VLV)

    DEL:414ba7a7-2a31-4328-a144-614af290a972" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Add Address List "\All Users" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Add Address List "\Default Global Address List" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Add Address List "\All Recipients(VLV)" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Add Address List "\All Mailboxes(VLV)" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Add Address List "\Mailboxes(VLV)" to AddressListMemberShip of the recipient.

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Found Email Address Policy "Default Policy".

    [08/26/2010 09:33:15.0906] [2] [Microsoft Cmdlet Extension Agent] Found Email Address Policy "Normal Policy".

    [08/26/2010 09:33:16.0202] [2] [Microsoft Cmdlet Extension Agent] Add Primary Email Address SMTP:MsExchDiscoveryMailboxD919BA05-46A6-415f-80AD-7E09334BB852@Example.com.

    [08/26/2010 09:33:16.0202] [2] [Microsoft Cmdlet Extension Agent] Set the recipient's WindowsEmailAddress to "MsExchDiscoveryMailboxD919BA05-46A6-415f-80AD-7E09334BB852@Example.com".

    [08/26/2010 09:33:16.0202] [2] Processing object "Example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852}".

    [08/26/2010 09:33:16.0218] [2] [ERROR] Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0249] [2] [ERROR] Unexpected Error

    [08/26/2010 09:33:16.0249] [2] [ERROR] Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0249] [2] [WARNING] The object Example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted, and it's in an inconsistent state. The following validation errors happened:

    [08/26/2010 09:33:16.0249] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:16.0249] [2] [WARNING] The property value you specified, "16", isn't defined in the Enum type "Nullable`1".

    [08/26/2010 09:33:16.0249] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:16.0249] [2] Ending processing get-mailbox

    [08/26/2010 09:33:16.0249] [2] Ending processing set-mailbox

    [08/26/2010 09:33:16.0265] [2] Active Directory session settings for 'Get-Mailbox' are: View Entire Forest: 'True', Configuration Domain Controller: 'sca-bes.Example.com', Preferred Global Catalog: 'home.Example.com', Preferred Domain Controllers: '{ sca-bes.Example.com }'

    [08/26/2010 09:33:16.0265] [2] Beginning processing get-mailbox -Filter:'name -eq $name' -IgnoreDefaultScope:'True' -ResultSize:'1'

    [08/26/2010 09:33:16.0265] [2] Searching objects of type "ADUser" with filter "(&((|((RecipientTypeDetails Equal RoomMailbox)(RecipientTypeDetails Equal EquipmentMailbox)(RecipientTypeDetails Equal LegacyMailbox)(RecipientTypeDetails Equal LinkedMailbox)(RecipientTypeDetails Equal UserMailbox)(RecipientTypeDetails Equal DiscoveryMailbox)(RecipientTypeDetails Equal SharedMailbox)))(Name Equal DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852})))", scope "SubTree" under the root "$null".

    [08/26/2010 09:33:16.0327] [2] Previous operation run on global catalog server 'home.Example.com'.

    [08/26/2010 09:33:16.0327] [2] Preparing to output objects. The maximum size of the result set is "1".

    [08/26/2010 09:33:16.0795] [2] [WARNING] The object Example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted, and it's in an inconsistent state. The following validation errors happened:

    [08/26/2010 09:33:16.0795] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:16.0795] [2] [WARNING] The property value you specified, "16", isn't defined in the Enum type "Nullable`1".

    [08/26/2010 09:33:16.0795] [2] [WARNING] Database is mandatory on UserMailbox.

    [08/26/2010 09:33:16.0795] [2] Ending processing get-mailbox

    [08/26/2010 09:33:16.0795] [1] The following 2 error(s) occurred during task execution:

    [08/26/2010 09:33:16.0795] [1] 0.  ErrorRecord: Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0795] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0811] [1] [ERROR] The following error was generated when "$error.Clear(); 

              if ($RoleIsDatacenter -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".

    [08/26/2010 09:33:16.0811] [1] [ERROR] Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0811] [1] 1.  ErrorRecord: Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0811] [1] 1.  ErrorRecord: Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0811] [1] [ERROR] The following error was generated when "$error.Clear(); 

              if ($RoleIsDatacenter -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".

    [08/26/2010 09:33:16.0811] [1] [ERROR] Database is mandatory on UserMailbox. Property Name: Database

    [08/26/2010 09:33:16.0811] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___590e51a8a98846d3a7fa8ddcc5472c74 Component=EXCHANGE14:\Current\Release\PIM Storage\Discovery

    [08/26/2010 09:33:16.0811] [1] Setup is stopping now because of one or more critical errors.

    [08/26/2010 09:33:16.0811] [1] Finished executing component tasks.

    [08/26/2010 09:33:16.0998] [1] Ending processing Install-MailboxRole

     

     

    Help is much appreciated!!!

     

    Thanks

     

    • Edited by SCANetworks.com Thursday, August 26, 2010 11:48 PM blackout the domain
    Thursday, August 26, 2010 11:45 PM

Answers

  • Did you already run setup.com /prepareschema, setup.com /preparead, and setup.com /pad?

    Your system mailbox and default discovery mailbox look like they're missing a couple values. Did you at any time delete the original DB which would have been created when this box was first installed and not moved these mailboxes to another DB? It should have prevented you from doing it, but there are ways to get around the warning.

    Open up LDP and take a look at the user accounts for these two objects which should be in your default Users container in AD. What values (if any) is in homeMdb attribute? If it is empty/null then you may want to copy the value from a user that has a mailbox on 2010 and populate this field with what they have then stop/start MSExchangeIS and System Attendent for good measure.

    Or you could delete these accounts and re-run setup.com /preparead which should recreate them for you.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Friday, August 27, 2010 1:13 AM

All replies

  • Did you already run setup.com /prepareschema, setup.com /preparead, and setup.com /pad?

    Your system mailbox and default discovery mailbox look like they're missing a couple values. Did you at any time delete the original DB which would have been created when this box was first installed and not moved these mailboxes to another DB? It should have prevented you from doing it, but there are ways to get around the warning.

    Open up LDP and take a look at the user accounts for these two objects which should be in your default Users container in AD. What values (if any) is in homeMdb attribute? If it is empty/null then you may want to copy the value from a user that has a mailbox on 2010 and populate this field with what they have then stop/start MSExchangeIS and System Attendent for good measure.

    Or you could delete these accounts and re-run setup.com /preparead which should recreate them for you.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Friday, August 27, 2010 1:13 AM
  • This sounds similar to :

    http://support.microsoft.com/kb/978776

     

    Except in your case, the discovery mailbox may be the culprit.

     

    Friday, August 27, 2010 1:13 AM
    Moderator
  • Thanks for the reply Brian,

     

    and yes i did mess around with the dbs to restore the db from my old domain, so i did delete the orignal db and tried to restore db from another forest but that didn't workout so i created a db from scratch.

     

    So I will do as you said and get back to you in a few minutes. BTW is it crucial to run setup.com/preparead, and by doing this won't it mess up my current setup?

     

    Thanks a lot

    Friday, August 27, 2010 1:18 AM
  • So the value of HomeMdb for both accounts was null, and so I just copied the value from another account and pasted onto those two accounts and rebooted exchange. let's see how that goes. 

     

    If it doesn't work out then i will just do what Andy and Brian suggested, to delete the accounts and run setup.com/preparead

     

    Thanks Again

    Friday, August 27, 2010 1:24 AM
  • Cool, those Null values are definitely making Exchange setup unhappy. :) Hopefully the reboot will do the trick.

    Re-running /preparead won't harm anything as long as you always are doing it from the newest version of Exchange in the org. So for example if you have Exchange 2003 and/or Exchange 2007 in the org still, don't run the similar commands for either of those versions now that 2010 is in there.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.

    Friday, August 27, 2010 1:29 AM
  • Thanks for the prompt reply! BTW i have another error in my eventvwr which keeps popping up, and i can't seem to find this account:

     

    Process w3wp.exe () (PID=1544). Object [CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Examples,DC=com]. Property [GlobalAddressList] is set to value [example.com/Configuration/Deleted Objects/Default Global Address List DEL:af307a25-6736-44fb-97ed-fe80c951b52b], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

     

     

    how can i fix this as well?

     

    Also, i just rebooted, can i run setup.com/prearead from the sp1 upgrade file? Thanks

    Friday, August 27, 2010 1:33 AM
  • Also, i just rebooted, can i run setup.com/prearead from the sp1 upgrade file? Thanks


    Yes. Before installing *any* SP1 servers you need to...

    1. Extend the Schema to 2010 SP1 via setup.com /ps

    2. Prepare the AD Forest to Exchange 2010 SP1 via setup.com /preparead

    3. Prepare the AD Domain(s) to Exchange 2010 SP1 via setup.com /pad (prepare all domains, it'll do them all at once if you have multiple)

    ... as long as you have done that already, then you should be good to go with SP1 installs.

     

    As for the other error it looks like the Default GAL may need to be recreated. Let me see if I can find something on that happening elsewhere.


    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Friday, August 27, 2010 1:51 AM
  • Thanks again Brian for the prompt response.

     

    BTW have you ever encountered this weird error, where an account won't connect to active sync, and in the event viewer it says active sync is disabled for the account but even though active sync is enabled for the account?

     

     

    Friday, August 27, 2010 2:00 AM
  • Check if security inheritence is turned off for their AD account. Use ADUC, turn on Advanced Features in the view menu, properties of the user, security tab, advanced button, look for a checkbox in the lower left of the window that pops up. If the user is a member of domain admins, enterprise admins, backup admins, or ever *was* a member of such groups this will be turned off and Exchange cannot create a sync partnership under the user object.
    Microsoft Premier Field Engineer, Exchange
    MCSA 2000/2003, CCNA
    MCITP: Enterprise Messaging Administrator 2010
    Former Microsoft MVP, Exchange Server
    My posts are provided “AS IS” with no guarantees, no warranties, and they confer no rights.
    Friday, August 27, 2010 2:02 AM
  • Thanks for the prompt reply! BTW i have another error in my eventvwr which keeps popping up, and i can't seem to find this account:

     

    Process w3wp.exe () (PID=1544). Object [CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Examples,DC=com]. Property [GlobalAddressList] is set to value [example.com/Configuration/Deleted Objects/Default Global Address List DEL:af307a25-6736-44fb-97ed-fe80c951b52b], it is pointing to the Deleted Objects container in Active Directory. This property should be fixed as soon as possible.

     

     

    how can i fix this as well?

     

    Also, i just rebooted, can i run setup.com/prearead from the sp1 upgrade file? Thanks


    Open the first referenced object with something like ADSI Edit and paste in the distinguishedName of a valid Global Address List object. You can grab the DN off the properties of the Global Address List with ADSI Edit or the like.
    Active Directory, 4th Edition - www.briandesmond.com/ad4/
    Friday, August 27, 2010 2:11 AM
  • So I just ran the upgrade again, and am getting the same error so i will delete those two accounts from adsiedit.msc, and run setup.com/ps, followed by setup.com/preparead. Should I run the orignal cd or should I use the sp1 update? Thanks
    Friday, August 27, 2010 2:31 AM
  • So I just ran the upgrade again, and am getting the same error so i will delete those two accounts from adsiedit.msc, and run setup.com/ps, followed by setup.com/preparead. Should I run the orignal cd or should I use the sp1 update? Thanks

    Definetely from the SP1 media. You can think of the SP1 media as a complete replacement for your RTM media (it is - you can install new servers with it).
    Active Directory, 4th Edition - www.briandesmond.com/ad4/
    Friday, August 27, 2010 2:32 AM
  •  but it is just the update file i downloaded from MS website, is the file just an update or the whole thing?

     

    Also, can you elaborate on finding the DN, in your earlier post?

     

    Thanks

    Friday, August 27, 2010 2:35 AM
  •  but it is just the update file i downloaded from MS website, is the file just an update or the whole thing?

     

    Also, can you elaborate on finding the DN, in your earlier post?

     

    Thanks

    It's the whole thing - there's no delta for SPs.

    As far as the DN, I'm looking at a 2010 environment and here's what I see (using adsiedit):

    Under Config/Services, properties of Microsoft Exchange there is a globalAddressList attribute. You can find your GAL under YourOrg/Address Lists Container/All Global Address Lists. Pull the properties of the GAL and copy the distinguishedName attribute to the clipboard. Paste it in to the globalAddressList property of the Microsoft Exchange object.


    Active Directory, 4th Edition - www.briandesmond.com/ad4/
    Friday, August 27, 2010 2:38 AM
  • Found it! Replaced the value as you said.

     

    I will try the SP1 upgrade now via setup.com/ps and then setup.com/preparead and then setup.com/pad

    BTW should I delete those two systemmailbox and discoverysearchmailbox, FederatedEmail before running the setup?

    I will get back to you as soon as it is done or an error comes up :)

     

    Thanks a lot for the prompt response and the help.

    Friday, August 27, 2010 2:47 AM
  • Just checked for Security inheritance on the object and it was already turned on(BTW it is the admin account, the master account that I am talking about)
    Friday, August 27, 2010 3:02 AM
  • Hey Brian,

     

    just tried the setup.com/ps, but I got the following error:

     

    Welcome to Microsoft Exchange Server 2010 Unattended Setup

     

    Preparing Exchange Setup

     

        Copying Setup Files                           COMPLETED

     

    No server roles will be installed

    Mailbox Role

    Setup previously failed while performing the action "BuildToBuildUpgrade". You

     can't resume setup by performing the action "Install".

     

    Exchange Server setup encountered an error.

     

    Do you know why this could be?

    Friday, August 27, 2010 3:17 AM
  • I have this same issue with the upgrade to 2010 sp1:

    WARNING: The object example.com/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted,
    and it's in an inconsistent state. The following validation errors happened:
    WARNING: Database is mandatory on UserMailbox.
    WARNING: The property value you specified, "16", isn't defined in the Enum type "Nullable`1".
    WARNING: Database is mandatory on UserMailbox.

     

    Running setup.com  /preparead also results in:

    No server roles will be installed
    Mailbox Role
    Setup previously failed while performing the action "BuildToBuildUpgrade". You
     can't resume setup by performing the action "Install".

    Exchange Server setup encountered an error.

     

    Please let me know if you find any resolution to this issue.  I'm searching on it as well today.

    Friday, August 27, 2010 1:58 PM
  • Hello,

    "Setup previously failed while performing the action "BuildToBuildUpgrade". You
     can't resume setup by performing the action "Install"."

     

    Go to your registry Editor under localmachine\software\microsoft\exchangeserver\V14


    In one of the Folders like MailboxRole, HubtransportRole or ClientaccessRole must exist an Value like Watermark and/or Action. Safe the current Folder (export)

    and then delete "Watermark" and "ACTION"

     

    Rerun the Setup Installation.

     

    Ralf

     

    • Proposed as answer by [MT] Tuesday, August 31, 2010 3:05 PM
    Tuesday, August 31, 2010 8:49 AM
  • YES, after deleting Discovery Mailbox and the two System Mailboxes i've started again the setup.com /preparead. This has recreated the Mailboxes. Then deleting the two registry Keys and rerun Setup. And it works like a charm :)

     

    Thank You for the Help,

     

    Ralf

    • Proposed as answer by 5150cd Friday, November 19, 2010 3:48 AM
    Tuesday, August 31, 2010 12:27 PM
  • CONFIRMED! In my case it solved the mailbox installation failure as well ;)
    Tuesday, August 31, 2010 1:30 PM
  • Hi, a question, when you say rerun setup, refer to setup.com /ps, setup.com /preparead or execute the wizard of Exchange 2010 SP1?

    Tuesday, September 7, 2010 10:21 PM
  • Thanks, specially Bryan, for your support with this topic.

    We had to implement a brand new Exchange 2010SP1 installation in Windows 2008R2, on a network with no-internet access. After several attempts, and reading information in microsoft-support, and several blogs, I must say that this was the most accurate information I found to troubleshoot the incident.

    However I consider important to clarify that the Exchange 2010-SP1 is not 100% accurate, when it comes to prereqs.

    After 3 days attempting to install EX2010SP1, the installation ended, but when opened the Exchange Management Console always failed, with the following error:

     

    Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

     

    and of course, the aforementioned:

     

     

    [WARNING] The object Example.com/Users/SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9} has been corrupted, and it's in an inconsistent state. The following validation errors happened:

    [WARNING] Database is mandatory on UserMailbox.

    [WARNING] Database is mandatory on UserMailbox.

     

    I remove the Exchange Server, and reinstalled it, but everytime the Readiness and prereqs passed OK.

     

     

    Conclusion: I found that there are several Windows Updates, that are not specified as prereqs (or at least not in the documentation I found) by the Exchange Installation.

    My point is, all of this strange errors also occurred if the server is not patched.

    After patched the server I runout the installation perfectly. I'm not talking about the Updates/Roles/Features(Including IIS6 Management Compatibility), nor the 979744, 983440, 979099, 982867 and 977020; that the Readiness checks previous to the installation. All of those were installed perfectly, and yet the installation always failed. In fact, Windows Server 2008R2, downloaded 84 patches, so I don't know exactly which one solved my problem.

    I know is kind of silly, but the customer didn't want internet connection in the infrastructure at that point, but at the end we found out a way to update the server from Windows Update without compromising the perimetral security, and the problem was solved.

    I also considered as Windows 2008R2, is the most recent incarnation of the Server OS, maybe EX2010SP1, didn't need Windows Update that much. I can't tell you how wrong I was. 

    Always patch your server, the 'Exchange Readiness Check' don't go that deep to show you dependencies related to Updates.

    Tuesday, September 6, 2011 3:49 PM
  • It worked for me, thanks

    Wednesday, September 7, 2011 10:27 PM
  • YES, after deleting Discovery Mailbox and the two System Mailboxes i've started again the setup.com /preparead. This has recreated the Mailboxes. Then deleting the two registry Keys and rerun Setup. And it works like a charm :)

     

    Thank You for the Help,

     

    Ralf

    Absolutely correct in my case as well.  I've been banging my head against this off and on for a month.  Once I got the courage to delete these objects from AD (existing exchange2003 environment I didn't want to destroy), I was able to setup.com /ps, and then the mailbox role installed happily.  Great posts to all who contributed to that finding!

    Paul


    P. Wasilewski
    Tuesday, October 25, 2011 2:21 PM
  • Dear Brian,

    I am having this problem during the installation of Exchange 2010 - I had installed Exchange 2010 for testing in our organization two months ago - now time for production and getting error:

    Mailbox Role
    Failed

    Error:
    The following error was generated when "$error.Clear(); $arbUsers = @(get-user -Filter {lastname -eq "MSExchApproval 1f05a927-3be2-4fb9-aa03-b59fe3b56f4c"} -IgnoreDefaultScope -ResultSize 1); if ($arbUsers.Length -ne 0) { $mbxname = $arbUsers[0].name; $mbxs = @( get-mailbox -arbitration -Filter {name -eq $mbxname} -IgnoreDefaultScope -resultSize 1 ); if ( $mbxs.length -eq 0) { $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController); if ($dbs.Length -ne 0) { enable-mailbox -Arbitration -identity $arbUsers[0] -database $dbs[0].Identity; } } }" was run: "The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox.".

    The user's Active Directory account must be logon-disabled for linked, shared, or resource mailbox.

    Can you please help me out in this - all other things went fine in the end of installation I received this error. You are really the champ.

    Regards

    Friday, December 9, 2011 11:38 AM
  • I would just like to chime in that this discussion thread totally saved me a call to Microsoft.  I battled with this for 1.5 days and finally got the mailbox role to install.  It had to do with a bad Discovery Mailbox also.
    Friday, April 12, 2013 2:54 PM
  • I have deleted system mailboxes of my exchange server 2010 and now want to run setup with prepareSC and AD to recreate the system user objects which I can later enable as mailboxes. Problem is when I run setup I get the error:

    Setup encountered problems while validating the sate of Active directory. The active directory organization configuration version (14322) is higher than Setup's version (14214). Therefore PrepareSchema cannot be executed.

    So what should i Do?

    Thanks
    Friday, May 24, 2013 1:40 PM
  • Brian Day you are a legend.

    This thread saved my Exchange 2010 box. The deleting of the system mailboxes via LDP and the the AD Prep steps work a treat even if though they took forever, like overnight.

    Then SP3 just installed as it should.

    SP3 seems to have cured some auth issues my users were having too !

    Thanks heaps

    Andrew

    Gold Coast


    Andrew Gold Coast, Aust

    Wednesday, February 26, 2014 1:16 AM