none
Exchange server 2010 SP3 failed

    Question

  • Hello 

    We have exchange 2010 SP2 running correctly. We wanted to install a second exchange server and transfer the mail to the second ( new server).  As we tried to install exchange 2010 SP3, the following error returned.

    Kindly help on this issue

    Action taken: We have checked our DNS is working correctly and also disjointed the server and rejoined it to the domain.

    Summary: 5 item(s). 1 succeeded, 1 failed.
    Elapsed time: 00:00:02


    Preparing Setup
    Completed

    Elapsed Time: 00:00:01


    Hub Transport Role
    Failed

    Error:
    The following error was generated when "$error.Clear(); 
    set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController

    " was run: "Property IsHubTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

    Property IsHubTransportServer can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp

    Elapsed Time: 00:00:01


    Client Access Role
    Cancelled




    Mailbox Role
    Cancelled




    Finalizing Setup
    Cancelled


    Saturday, October 12, 2013 3:34 PM

Answers

All replies

  • Install SP3 where? On a new server or the existing one? It sounds like you an old server object under the Exchange config container that setup sees.


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Saturday, October 12, 2013 4:15 PM
    Moderator
  • SP3 is on the new server
    Saturday, October 12, 2013 4:30 PM
  • Ok, things I would check:

    Was this an upgrade from 2003 at some point? If so, was the 2003 servers removed correctly?

    You havent disabled IPV6 have you?

    Did you follow all the pre-reqs for Sp3? http://technet.microsoft.com/en-us/library/bb629560(v=exchg.141).aspx

    Is the time sync correct on the server? Any other event errors in the logs? Does ExBpa look clean?


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    • Proposed as answer by Zaza Abramov Saturday, October 12, 2013 5:39 PM
    • Unproposed as answer by drorisa Sunday, October 13, 2013 8:55 AM
    Saturday, October 12, 2013 4:40 PM
    Moderator
  • Here is the story. We had exchange 2003 and we installed exchange 2010 on a new server and tranferred all the mail boxes. For some reason which we do not know, the old exchange 2003 could not be totally removed from the 2010. The exchange 2003 is already gone now. We operated for a year without problem. Now we want to change our mail server by a new one. We need to install exchange 2010 sp3 on a new server and transfer the mail boxes to this new server but the above problem happened. We think it is referencing the old exchange 2003. 

    Actions taken:

    IPv6 disabled

    DNS record updated.

    Sunday, October 13, 2013 9:48 AM
  • Here is the story. We had exchange 2003 and we installed exchange 2010 on a new server and tranferred all the mail boxes. For some reason which we do not know, the old exchange 2003 could not be totally removed from the 2010. The exchange 2003 is already gone now. We operated for a year without problem. Now we want to change our mail server by a new one. We need to install exchange 2010 sp3 on a new server and transfer the mail boxes to this new server but the above problem happened. We think it is referencing the old exchange 2003. 

    Actions taken:

    IPv6 disabled

    DNS record updated.

    Look under the config container via adsiedit and see if the old Exchange 2003  server is still there

    CN=configuration,DC=.example,DC=.COM > CN=Services > CN=Microsoft Exchange > CN=Organization > CN= Administrative Groups > CN=(Legacy Admin Groupname) > CN=Servers >


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Sunday, October 13, 2013 1:23 PM
    Moderator
  • We see the following hierarchy

    CN=Administrative Groups

    • CN=Exchange Administrative Group(FYDIB….)
      • Advanced security
      • Arrays
      • Database availability groups
      • Databases
      • Routing groups
      • Servers
        • Mail server
          • Information store
          • Microsoft MTA
          • Microsoft system attendant
          • Protocols
    • CN=First Administrative Group
      • Advanced security
      • Folder Hierarches
      • Routing groups
        • First Routing group
          • Connection
      • Servers
        • Mail
          • Microsoft MTA
          • Protocols

    The old exchange was mail and the mailboxes were transferred to mail-server(the current running exchange server). These two servers were in coexistence mode for sometimes. Now we want our mail server to be changed and the name of our new mail server is mail

    thanks

     
    Monday, October 14, 2013 5:20 AM
  • Well, there is your problem. The "MAIL" server still exists in AD right? 

    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

    Monday, October 14, 2013 12:34 PM
    Moderator
  • The new server is named MAIL but the old mail is removed from AD properly
    Monday, October 14, 2013 12:46 PM
  • The new server is named MAIL but the old mail is removed from AD properly

    And yet its still there under the config container yes?

    You can follow this KB to remove the 2003 object manually.

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

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

    Ensure you have correctly moved everything to 2010. DO NOT REMOVE any 2010 objects. DO NOT REMOVE the legacy Admin Groups.

    You can however remove the servers object under the 2003 Admin group once its empty. In fact, removing that may prevent other issues with routing and mail-enabled PFs.

    http://blogs.technet.com/b/sbs/archive/2012/05/17/empty-cn-servers-container-causing-issues-with-public-folders-on-small-business-server-2011.aspx

    I assume you have moved all the PF hierarchy and followed this:

    http://technet.microsoft.com/en-us/library/gg576862(v=exchg.141).aspx

    Remove the Last Legacy Exchange Server from an Exchange 2010 Organization

    Alternatively, you could call the new server something else  :)


    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.



    Monday, October 14, 2013 1:32 PM
    Moderator