none
Hub Transport Role Install Fail error # 2147504141

    Question

  • Hello,

    I am trying to install Exchange 2010 on a fresh Server 2008 install that is running domain services, dns and IIS.  All the prereqs were installed and it passed all the tests.  While installing the hub transfer role it threw an error:

    Hub Transport Role
    Failed

    Error:
    The execution of: "$error.Clear(); install-ExsetdataAtom -AtomName SMTP -DomainController $RoleDomainController", generated the following error: "An error occurred with error code '2147504141' and message 'The property cannot be found in the cache.'.".

    An error occurred with error code '2147504141' and message 'The property cannot be found in the cache.'.

    Elapsed Time: 00:09:31

    Any ideas?

    Thanks, Steve
    Thursday, April 16, 2009 6:28 PM

Answers

  • @Peter  -  Exchange 2007 is x64 and Exchange 2003 is 32-bit only.  Your question isn't making much sense to me in that regard.  You most likely need to remove Exchange, make certain the server objects in AD are clean, and reinstall the entire server.  I have never heard of that error.

    @Brian  -  Can you start a new forum thread for your issue please?  Next steps, I would check the event logs as you should have some reasons why the Transport service will not start in there.  Perhaps there is an issue with the ADTopology service or something.

    For future readers of this thread, let me attempt to clarify:

    1. Microsoft does NOT recommend unchecking IPv6 on the NIC properties.  At this time, there are issues with doing so.  Fully disabling it should not be required either, although it can workaround issues with AAAA records and other environmental issues that may be going on.  We are working on some troubleshooting content and blog post for IPv6 to better assist you with learning this technology.
    2. Hub role failing to install is a complex issue -- we hear the feedback that many of you are having issues.  But there are different problems and different resolutions.  In order to improve the experience and better help you, we need specific errors from the setup log and from the event logs.  If your issue doesn't match the 2147504141 error above, it may make sense to start a new thread on this forum so that we can better track it and avoid confusion.  Part of the problem here is that folks are having many different errors, which explains why certain things work for some but not others.
    3. Regarding the original error from the title of the post, 2147504141, we have published a new KB article http://support.microsoft.com/kb/980050.  This KB specifically addresses the 2147504141.  We have seen the issue be caused by other time sync issues, so it isn't necessarily specific to Hyper-V installs -- but if the clock on either the Exchange server or DCs are not correct, then the ADSI cache will not work properly and setup will fail.

    I hope that this guidance is useful and I wish you luck in troubleshooting your issue.  Please do not hesitate to ask us for help and thank you for all of your feedback so that we can continue to improve the install experience.

    Regards,
    Scott Landry, Program Manager
    Microsoft Exchange Customer Driven Quality

    Thursday, July 01, 2010 3:10 PM
    Moderator

All replies

  • hello,

    What is the status of IPv6? if it is disabled hub transport server role will not installed successfully.

    enable it or install it and then run setup.exe again.

    regards.


    System & Network Support Specialist - Bursa / TURKEY
    Thursday, April 16, 2009 6:33 PM
  • Steve,

    What happens when you try installing the HT role again?
    Microsoft Exchange MVP | http://exchangeexchange.com
    Thursday, April 16, 2009 6:35 PM
  • hello,

    What is the status of IPv6? if it is disabled hub transport server role will not installed successfully.

    enable it or install it and then run setup.exe again.

    regards.


    System & Network Support Specialist - Bursa / TURKEY

    This is incorrect, all roles can be installed even if IPv6 are disabled.
    Microsoft Certified Master: Exchange 2007; MCSE:M 2003; MCITP: 2008; Windows Server MVP; CCNA
    • Proposed as answer by Anatoly Ivanov Thursday, April 23, 2009 5:17 PM
    Thursday, April 16, 2009 6:40 PM
  • So I tried it again after a reboot with IPv6 turned back on and off and both resulted in the same error:

    Hub Transport Role
    Failed

    Error:
    The execution of: "$error.Clear(); set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController", generated the following error: "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).

    Elapsed Time: 00:00:00
    Thursday, April 16, 2009 6:53 PM
  • hi erik,

    during my test phases I tried to install without IPv6 and Exchange HUB Transport Role did not installed and occured problem.

    when i installed IPv6 and then run setup again Exchange Server 2010 installed succesfully...

    thanks...
    Exchange - MVP / TURKEY
    Thursday, April 16, 2009 6:56 PM
  • 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).

    Did that server, or computer object in AD, have a prior version of Exchange on it?
    Microsoft Certified Master: Exchange 2007; MCSE:M 2003; MCITP: 2008; Windows Server MVP; CCNA
    Thursday, April 16, 2009 6:56 PM
  • Nope. New 2k8 dvd install. Although I did not get that error the first time setup failed when I got the error in the first message.
    Thursday, April 16, 2009 7:01 PM
  • what is the service pack status on 2k8?

    Exchange 2010 requires Windows Server 2008 with SP1...

    regards,
    Exchange - MVP / TURKEY
    Thursday, April 16, 2009 7:03 PM
  • Yep, sp1 installed and all updates from WU.
    Thursday, April 16, 2009 7:04 PM
  • I wonder if I am missing some server roles or something?

    These are the exact steps I took:

    1. Installed Server 2008 std. x64
    2. Installed Hyper-v integration components
    3. Set static IP address and disabled IPV6 on the nic.
    4. Ran Windows Update to get latest SP and patches
    5. Added Domain Services role.
    6. Ran dcpromo to create domain and set it to server 2008 level, this also installed the DNS role
    7. Added web server role
    8. Started setup and worked through the rest of the prereqs that came up in the prereq checker.
    9. Ran typical install with all defaults and got the error in the first message.
    Thursday, April 16, 2009 7:10 PM
  • And on a clean w2k8-sp1 server without any domain services?

    I'm running a w2k8-sp1 into a hyper-v 2 environment.
    Also latest updates and web components (requirements) installed...
    I've not disabled any ipv6 settings - all roles are installed correctly.

    regards,

    MCSE+S; MCITP:SA,EA; MCITP: EMA
    Thursday, April 16, 2009 7:50 PM
  • ya, the same problem i met with IPv6

    this is  funny from ex2007..
    Friday, April 17, 2009 3:34 AM
  • http://support.microsoft.com/default.aspx/kb/952842

    check this article, disable ipv6 by adding a registry key

    i have the same issue, i disable ipv6 competely and even i leave ipv6 available.  both get the same result.

    i install a new win2k8 sp1 in hyper v and leave ipv6 open, the same result!
    Friday, April 17, 2009 7:12 AM
  • Hi Steve,

    do not disable ipv6 in Step 3. I´ve done a few tries and disabling ip v6 in E2010 - Beta always lets you run into errors.
    Viele Grüße Walter Steinsdorfer MVP Exchange Server http://msmvps.org/blogs/wstein
    Friday, April 17, 2009 9:10 AM
  • The install destroyed itself.  I can't even uninstall the components that did install to start fresh so I'm reloading the server again.  I'll report back when I install again. Thanks!
    Friday, April 17, 2009 12:19 PM
  • Hi all ,

    as you said above i am trying to install with or without ipv6 but the installation gives error
    ""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).""
    has anyone succesfully installed it ?
    Friday, April 17, 2009 12:57 PM
  • Hi Steve,

    I tried the same way you did. I aggreed your number 9 result
    Friday, April 17, 2009 1:06 PM
  • Looks like IPv6 was it.

    After the rebuild I tried it again with IPv6 unchecked on the local area connection and attempted the registry change to disable IPv6 but still had the error.  So I re-enabled IPv6 on the local area connection and gave it a static address and then setup worked flawlessly. 

    Thanks everyone!
    Friday, April 17, 2009 6:36 PM
  • you are right Steve. static IPv6 address works fine
    Saturday, April 18, 2009 9:58 PM
  • just experienced the same scenario

    I did this steps,

    1. Got a fresh virtual-server2008.
    2. Disabled the ipv.6 using the http://support.microsoft.com/default.aspx/kb/952842 .
    3. Disabled the ipv6 on the nic.
    4. Installed the prerequisites and hotfixes.
    5. Installed exchange typical installation.

    Everything gone right.
    Saturday, April 18, 2009 10:29 PM
  • Same issue for me as well (win2k8 Datacenter x64 DC/GC and top of it Exchange), initially i disabled the IPv6 using NIC property that messed up the entire networking component, so letter followed the KB 952842 and made the following changes in the registry

    1. Open Registry Editor.
    2. Locate the following registry subkey:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
    3. In the details pane, click New, and then click DWORD (32-bit) Value.
    4. Type DisabledComponents, and then press ENTER.
    5. Double-click DisabledComponents, and then type 0xffffffff in Hexadecimal or 4294967295 in Decimal.

    Rebooted the box and it did the trick! - just wondering still we are hitting up on IPv6 :(

    Regards,
    -A

    Sunday, April 19, 2009 5:04 PM
  • We've heard reports that opening up the HOSTS file (\windows\system32\drivers\etc\hosts) and removing the ipv6 addresses there helps unblock this setup issue.

    If this is the case, please let us know.


    -Greg
    Tuesday, April 21, 2009 8:41 PM
  • hi all there,
    i have tested it on Server 2008 R2 SP2 (64bit) and Server 2008 SP2.
    furthermore, i also completed all prereqs before starting exchange2010 setup. but every time i got same error "2147504141". i also tried installation after disabling IPv6.

    i am really tired of this error, could any one please help me out to solve this issue..

    very thankful to all of you.

    regards,

    AK

    Thursday, April 23, 2009 12:12 PM
  • Here is what I have experienced.

    Tried to install the Ex 2010 on a Windows 2008 X64 server ENTERPRISE edition promoted as DC and it failed miserably like you stated.
    It could have failed because :
    1. Installation on the Enterprise version ?
    2. I have renamed the DC after promotion ?

    I am running on a virtual environment.

    Anyway , I have installed a windows 2008 X64 SP1 Server STANDARD edition , patched with all the patches.
    Installed IIS and .Net 3.0
    Disabled IPV6 on the network adapter and in the registry.
    Promoted the machine as DC on a new forest.
    Reboot
    Started installation and everything went ok.

    I am suggesting a virtual environment so you guys can take snapshots if anything goes bad , you can always revert.
    Saturday, May 09, 2009 10:18 PM
  • hi,

    exchange server 2010 can be installed on Windows Server 2008 Enterprise edition. there is no problem about this. I am running 3 exchange server 2010 on Enterprise edition on my Hyper-v.

    it is not problem to rename your dc after promotion it can be done. I tried it during my testing phases...

    I installed on my windows server 2008 enterprise edition ;

                    -       Microsoft. Net Framework 3.5 (.Net Framework 1.1 is also required for ExBPA installation)

    -          Windows PowerShell v2

    -          Windows Remote Management (WinRM) (KB950099)

    -          ExBPA

    -          KB950888

    -          KB951725

    -          FilterPack x64

    regards,


    Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    Sunday, May 10, 2009 4:46 AM
  • Now let me ask you :

    Have you installed IIS after DC promotion ?
    Have you renamed the DC before or after the DC promotion or IIS install ?
    Have you disabled IPV6 before or after starting the exchange installation ?

    On my second attempt of install , I disabled the IPV6 before starting exchange install and I installed IIS after I renamed the machine. And I renamed the machine BEFORE promoting to DC.

    Sunday, May 10, 2009 4:06 PM
  • hi GeoSs,

    on my first installation of exchange server 2010;

    you know while you are installing windows server 2008 you can not assign a name to server. Win 2008 assigns it automatically and assigned to my server "win-4hcpyzsrjob" as name. when installation finished I installed Active Directory directly I didnt change the name. and then I renamed DC with "exc2010"  name. 

    I installed IIS after DC promotion.

    First I disabled it but during the installation of Exchange Server setup it gave an error. and then I enabled IPv6 then re run setup and it went ok... no problem...

    and my installation screenshots are here ;

    http://www.mumincicek.com/index.php/exchange-server/35-exchange-server/114-exchange-server-2010-kurulumu-.html

    it is not in English in Turkish but from the pictures you can follow the installation...

    regards,


    Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    Sunday, May 10, 2009 5:05 PM
  • I am not sure what and how you did your install but I have tried again.
    New install , left the IPV6 as default , took a snapshoot on Vmware , started Exchange install ... failed miserably.

    Revert to snapshoot , DISABLED IPV6 and patched registry , reboot , started installation ... everything went painless.
    So MY conclusion (in my environment and situation) is that you have to disable the damn IPV6 before starting exchange installation.

    I will try again one of this days in a different environment , as I have to make a documentation for a customer , and I will try also your way.

    Have you tried to promote to DC , install IIS and THEN rename the whole thing ? IIS / Exchange might not like the fact that I renamed the machine after installing IIS ? (had many IIS problems in the past with MS Application Center when renaming machine after IIS install on a domain member).
    Saturday, May 23, 2009 11:49 AM
  • hi,

    why do you disable IPv6?

    I didnt disable IPv6 on my installations. when I disabled it Exchange installation did not continue...

    regards,


    Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    Saturday, May 23, 2009 12:07 PM
  • If it is on DC then you don't need to disable, otherwise on member server.. Yes disabling the same resolved the installation errors
    Arun Kumar | MCSE - 2K3 + Messaging | ITIL-F V3
    Saturday, May 23, 2009 12:27 PM
  • hi,

    I just finished one test installation for you and take screenshots of installation.

    What I did;

    - installed windows server 2008 enterprise
    - ip konfiguration (static ip given), IPv6 not disabled
    - installed active directory (not renamed pc yet,standart named by windows server 2008 setup wizard)
    - installed application server, web server (IIS) on it
    - renamed windows server 2008 (new name is "excdc" for it)
    - installed exchange server 2010 requirements
    - installed exchange server 2010 successfully
    - checked for mail traffic (it is working both owa and outlook)

    and screenshots for this installation is here ;

    http://www.4shared.com/file/107251681/80fe05ef/exc.html

    and also, I have 4 exchange server on my Hyper-V. 3 of them are Mailbox Server and 1 of them is CAS,HT server role installed. they are member server all. and IPv6 is not disabled. they are working correctly.

    regards,


    Mumin CICEK | Exchange - MVP | www.cozumpark.com | www.mumincicek.com
    • Proposed as answer by Mumin CICEK Monday, May 25, 2009 7:04 AM
    Saturday, May 23, 2009 1:59 PM
  • Hi all,

    I experience the same issue with installing exchange 2007. I tried disabled IPv6 and enabling IPv6 but i still have the same error.

    Anyone managed to resolve this?
    yongsan
    Friday, October 09, 2009 5:04 PM
  • I had the same problem on Exchange Server 2007 with SP1 on Windows Server 2008 Enterprise and I resolved it with this:

    http://support.microsoft.com/default.aspx/kb/952842

    How ever, I tried doing the same on Datacenter Edition of the same product and it fails painfully.

    Anyone with a solution is highly welcome.

    Ifeatu - MCTS, MCP
    http://www.ifeatuosegbo.com - http://blogs.ifeatuosegbo.com
    Friday, October 23, 2009 1:12 PM
  • Dear Friends,

    I really need your help to soughted out the issue, which I'm facing to install Exchange 2010 in the test lab, I have read the thousands of post reated to this issue but havent fixed it out this yet...

    Solutions tried:
    1) unticked the IPV6 from the LAN Card configuration and Disabled IPv6 from the Registery.
    2) left ticked IPv6 in the LAN Card configuration and diabled iPv6 fromt he registery.
    3) Disabled IPv6 from the registery and give static link local IP address to IPV6
    4) left ticked IPv6 in the LAN card configuration and not-disabled IPv6 from the registery

    Actual errors, which I'm receiving:
    1) Error: An error occurred. error code was 2147504141 message was The property
    cannot be found in the cache.."

    2) Error: The execution of: "$error.Clear(); set-ExchangeServerRole -Identity $RoleFqdnOrName -IsHubTransportServer:$true -DomainController $RoleDomainController", generated the following error: "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).

    And now by trying all the aboved described solutions, i havent fixed this problem...

    Kindly leeme knw the most appropriate solution to fix this.

    Zahir Hussain Shah
    zhshah@live.com
    UAE
    Monday, November 09, 2009 11:20 AM
  • I would suggest a format and start clean install windows ... this will spare you much time in debugging.
    IT System Engineer / MCSA / MCSE
    Monday, November 09, 2009 11:31 AM
  • Yup, I just started it, but I just wana knw here that, what combination of settings should I keep here, e.g.

    i) Should I disable the IPV6 from the registery with ticked IPv6 in LAN Card before installing Exchange 2010 on Windows Server 2008 R2?
    ii) Should I disable the IPV6 from the registery with unticked IPv6 in LAN Card before installing Exchange 2010 on Windows Server 2008 R2?
    iii) Should I disable the IPV6 from the registery with ticked IPv6 & give static IP Address in LAN Card before installing Exchange 2010 on Windows Server 2008 R2?, if yes then which IP (link-local)?


    Kindly tell me i really got stucked in all that.

    Regards,

    Zahir
    zhshah@live.com

    Monday, November 09, 2009 12:03 PM
  • Dsiable IPV6 from all the places before you start any exchange installation. This did it for me.
    IT System Engineer / MCSA / MCSE
    Monday, November 09, 2009 12:54 PM
  • First of all thankx for your reply, and after that you mean the following:

    - Before starting Exchange 2010 installation,
    - i should first Untick IPv6 from the LANCARD of the box and
    - after that disabled IPv6 from the registery.

    one thing more tell me, is there any hard and fast requirement for Exchange Server 2010 that it can not be installed on Domain Controller?

    Regards,

    Zahir Hussain Shah
    Monday, November 09, 2009 5:26 PM
  • Having the same error. Server 2008 R2 with Exchange 2010. It's also a domain controller. disabled ipv6 on lan card as well as disabled in registry. Rebooted server. restarted installation and still getting same error. :-(

    Tuesday, November 10, 2009 10:03 PM
  • Dear Forum members, please put some light on this issue ???

    Zahir
    Wednesday, November 11, 2009 6:19 AM
  • FIXED IT! :)

    Summary of problem:

    Initially, i was testing to install Exchange 2010 on the Domain Controller itself (Windows Server 2008 R2), and when I seperated my DC (AD DS) on the seperate server, then make another seperate VM of Windows Server 2008 R2 with the follwoing settings for IPv6"

    - Untick IPv6 from the LAN CARD
    - Disabled from the registery

    so finally it went all fine...

    So guys, it was IPv6 + AD DS presence on the machine on which you wanted to install Exch 2010.

    Thank you all of you to contribute here...

    Zahir
    zhshah@live.com
    Wednesday, November 11, 2009 6:51 AM
  • I had the same problems with my test install, this is what I did to fix my problem

    Clean install of windows 2008 SP2 Standard x64

    Existing Win 2008 Domain but used ADSI edit to delete all the MS Exchange Containers to fix the issue with the HT complaining that it needs version 8.5 and that it detected 6.5.  I also deleted the Microsoft Exchange Security Groups using Active Directory Users and Computers console.

    I did not touch anything about IPV6 (I had tried with IPv6 on and off and never successful for some reason but at the end I didn't have to do anything with IPv6)

    I did every step except for step 1 from the following http://technet.microsoft.com/en-us/library/bb125224.aspx 

    Downloaded all the prerequisites (.NET Framework 3.5, power shell, and added the services roles)

    and the install was successful

    Monday, January 11, 2010 4:08 PM
  • It has been determined that there are many possible causes for this issue.  Most of them are solved simply by restarting the machine or waiting for the AD cache to expire.  However, there may be other causes. 

    We are investigating these causes.  If you're have a situation where this can be reproduced reliably, please consider reaching out to us so that we can improve the product.  You may feel free to email me personally (Scott Landry in the format of first dot last) if you're stuck and want to share the relavent data with us.

    We apologize for any inconvenience this may have caused.

    Thanks for your help!
    Tuesday, January 19, 2010 4:30 PM
    Moderator
  • I also got this error, and have tried the disable ipv6, it doesn't work for me.
    Any good ideas? thanks very much, I've been stuck for a week.
    Tuesday, January 26, 2010 12:19 PM
  • Have reinstalled Win2k8 x64 R2, it looks good so far. I suspect there're problems when patching so many hotfix, and it's an issue that's worth MS to track i think.
    Wednesday, January 27, 2010 3:39 AM
  • I can get the install of Exchange to fail every time with out fail. I have installed 2 x server 2008 R2 Domain controllers from scratch. 

    Add a member server 2008 R2. Install all Exchange prerequisites and readiness passes no problems. Go to install Hub transport and it fails with error

    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).

    I have installed all 3 servers from scratch without any luck. Got sick of that so took snapshots with esxi.

    Have tried the ipv6 "fix" without any luck.

    Does anybody have any other ideas. Spent 2 days on this now.

    Thanks
    Sunday, February 14, 2010 12:54 PM
  • Look here:
    http://support.microsoft.com/kb/980050
    Friday, March 05, 2010 3:31 PM
  • Dear All,

    I would like to recommend a solution here, as a tested resolution for Exchange 2010 HUB TRANSPORT ROLE:

    Steps to prepare a Machine for HUB Transport Server role before running setup installation:

    1) Uncheck IPv6 option in the LAN CARD TCP/IP Configuration
    2) Go to the registery and disabled the IPV6, using this MS KB ARTICEL:

    http://social.technet.microsoft.com/Forums/en/exchange2010/thread/8f6ff508-2c09-4140-ba14-eca32bc5bf1d
    3) Install Exchange 2010 HUB Trasnport Server Role
    4) After the installation, when you will first open the EMC, so it will get failed on the initializaiton of EMC, so the workaround for this problem is to close the EMC, and go the SERVER MANAGER, and do the following:
    - Go the the installed features, remove WINRM feature
    - Restrat Server
    - After rebooting go the SERVER MANAGER again and install the WINRM again
    - after installing WINRM feature again, open CMD, run the below commands:
                      - %WINDIR%System32>winrm quickconfig
                                                          > confirm YES for creating FIREWALL expectioin for WINRM


    After doing the above series of steps, when you will open Exchange 2010 Management Console, so it will open without giving you any error related to WINRM initialization.



    Please reffer back to me if you face any issue with this

    Zahir Hussain Shah

    Thursday, March 11, 2010 9:53 AM
  • For a NEW installation of Exchange 2010 which I did a few weeks ago the error came again and it helped just uninstalling WINRMand installing the feature again.

    IT System Engineer / MCSA / MCSE
    Thursday, March 11, 2010 1:58 PM
  • Hi all,

    just FYI: I ran into the very same problem yesterday. It seemed to have a very special cause but I'll just describe it here in case anyone gets into the same situation.

    We were trying to install Exchange 2010 in a test lab based on Win 2008 R2 Datacenter upon VMware ESX 4. We used two servers, one as a DC for our test domain and one as Exchange server. Both machines were based on the same OS template (which had been sysprep'd, of course).

    The strange thing was that both servers initially had a completely wrong system time which was more than five hours ahead of the real time (not exactly, there were some additional minutes). I have no idea where this time came from as the ESX host had correct time. Host time sync was not enabled, however. We corrected the time, but obviously we had to set it back for more than five hours. We only noticed this after AD had already been installed.

    First we ran into the "the attribute was not found in the cache problem". The IPv6 trick did not help. Some time later we had setup complain about the object with the wrong version number. Strangely enough, we did not manage to delete the objects via ADSI Edit.

    We then decided to flatten the Exchange box and uninstall/reinstall AD on the DC. The DC server had been online for more than five hours now, so even the initial incorrect system time had passed, and it was having the correct real time now.

    This time we were lucky. We did not have to disable IPv6 or do any other magic. Exchange installed flawlessly.

    My lesson learned: There may be severe issues when the AD domain has system time problems. I really think this was the base problem. So make sure time is synced correctly before you install Exchange 2010.

    Bye, Nils

     


    Nils Kaczenski
    MVP Directory Services
    Hannover, Germany
    Tuesday, May 18, 2010 6:03 PM
  • I messed with IP v6 on my fresh Windows 2008 R2 Domain Controller that I was installing on and figured out that I was missing some components. 

    Make sure that you have all of the componets listed in this page installed or you will get the error:

    http://technet.microsoft.com/en-us/library/bb691354.aspx#WS08R2 


    Eric
    Monday, May 31, 2010 7:58 PM
  • I am also having the same issues installing Exchange 2010. I have a clean 2008R2 Enterprise server running in a 2008R2 domain. This is a clean environment that has never had Exchange installed before.

    I have tried with the default IP6 settings and unchecking from the network settings then doing the registry hack as instructed above.

     

    To clarify I get the following error:

    Error:
    The following error was generated when "$error.Clear(); if ($RoleStartTransportService) { start-SetupService -ServiceName MSExchangeTransport }" was run: "Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.".

    Service 'MSExchangeTransport' failed to reach  status 'Running' on this server.

     

    Any help is appreciated.

    Brian

    Tuesday, June 29, 2010 7:59 PM
  • I am suffering with "LsaStorePrivateDataFailed()". In my case there WAS an prior version of Exchange (2003) running on this system, but it was deinstalled. Is there something I should do to get the Hub Transport installed?
    Peter
    Thursday, July 01, 2010 11:30 AM
  • @Peter  -  Exchange 2007 is x64 and Exchange 2003 is 32-bit only.  Your question isn't making much sense to me in that regard.  You most likely need to remove Exchange, make certain the server objects in AD are clean, and reinstall the entire server.  I have never heard of that error.

    @Brian  -  Can you start a new forum thread for your issue please?  Next steps, I would check the event logs as you should have some reasons why the Transport service will not start in there.  Perhaps there is an issue with the ADTopology service or something.

    For future readers of this thread, let me attempt to clarify:

    1. Microsoft does NOT recommend unchecking IPv6 on the NIC properties.  At this time, there are issues with doing so.  Fully disabling it should not be required either, although it can workaround issues with AAAA records and other environmental issues that may be going on.  We are working on some troubleshooting content and blog post for IPv6 to better assist you with learning this technology.
    2. Hub role failing to install is a complex issue -- we hear the feedback that many of you are having issues.  But there are different problems and different resolutions.  In order to improve the experience and better help you, we need specific errors from the setup log and from the event logs.  If your issue doesn't match the 2147504141 error above, it may make sense to start a new thread on this forum so that we can better track it and avoid confusion.  Part of the problem here is that folks are having many different errors, which explains why certain things work for some but not others.
    3. Regarding the original error from the title of the post, 2147504141, we have published a new KB article http://support.microsoft.com/kb/980050.  This KB specifically addresses the 2147504141.  We have seen the issue be caused by other time sync issues, so it isn't necessarily specific to Hyper-V installs -- but if the clock on either the Exchange server or DCs are not correct, then the ADSI cache will not work properly and setup will fail.

    I hope that this guidance is useful and I wish you luck in troubleshooting your issue.  Please do not hesitate to ask us for help and thank you for all of your feedback so that we can continue to improve the install experience.

    Regards,
    Scott Landry, Program Manager
    Microsoft Exchange Customer Driven Quality

    Thursday, July 01, 2010 3:10 PM
    Moderator
  • Thanks Scott ! worked like a charm.
    Tuesday, July 20, 2010 6:07 PM
  • Hy,

    I have the same problem, same error code.

    I have tryed everything (I think...). I even reinstalled the OS. I have tryed disabled IPv6, enabled and with static IP, Schemamaster on same site, changed schemamaster to another DC. Same error. have Microsoft Exchanged figured out what the problem is?

    I have error logfile, and can post it if can help to solve the problem.

    My system is a forrest with 2 child domains, 2 domaincontrollers in the forrest, and 4 domaincontrollers in each childdomain. In 6 sites.

    Sunday, October 31, 2010 11:41 PM
  • Hi all ,

    as you said above i am trying to install with or without ipv6 but the installation gives error
    ""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).""
    has anyone succesfully installed it ?


    Same exact issue (and question). Any idea as to what this may be?

    Regards

    Monday, January 17, 2011 12:32 AM
  • Hi Scott,

    I am also having the "2147504141" issue installing hub transport for exchange 2010 on a fresh 2008R2 server.

    I am not runnning any virtualisation software.  So what do you mean exactly with :

    >>> but if the clock on either the Exchange server or DCs are not correct <<<

    In my network DC and Exchange server are the same...

    I have tried with IPv6 active and non-active.  (in dns only IPv4 adresses)

    Thanks for any help.

    Best regards,


    Tony Maertens - Belgium


    Monday, February 21, 2011 10:11 AM
  • Hello Steven, I don't know if its too late to reply on this issue but i recently came across this issue when I was given the task to prepare a Virtual PC machine with the following requirements:

    1. Windows Server 2008 SP2 (32-bit)

    2. Exchange 2007 SP2 (32-bit)

    It is obvious, from the 32-bit Exchange, that it was going to be used as a testing machine. I did not have to play with IPv6 to resolve the issue. Here is how I was able to resolve it:

    1. Installed Windows 2008 SP1 (32-bit)

    2. Applied SP2 for Windows 2008

    3. Promoted it to a Domain Contorller

    4. Installed the Web Server Role with the required features

    5. Added the Windows Powershell feature

    6. Added .Net Framework 3.0 feature from Server Manager (This was the step that I was missing and it actually resolved the issue)

    7. Then ran Exchange Server setup and it Finished without any issues.

     

    I hope this helps someone.

    Regards

    Asif Bashir

    Sunday, May 22, 2011 7:37 PM
  • Hi There,

     I am running Windows 2008 R2 which is DC and trying to install exchange 2010 Ht role on it. Noe other DC's and exchnage roles in environment. This is first role in Organixation and faced exact same error mentioned above. After lots of troubleshooting manage to get past this error and able to install HT role.

    I cannot right all troubleshooting steps here as incorrectly following steps will screw up your environment. I will suggest you to open tikcet with MS.

     

    Monday, November 28, 2011 8:46 PM
  • Hi,

    during installation of exchage server, it  generated the following error:

    An error occurred with error code '2147504141' and
    message 'The property cannot be found in the cache.'.

    i hve tried IPv6 solution but found the same error..

    can u please help me to resolve it..


    Harmeet Singh Virk

    Thursday, May 03, 2012 12:44 PM
  • I got this issue when doing an Exchange 2010 install on a HyperV host.

    Tried it multiple ways - rebuilding Win2008R2 each time, with IPV6 on, off, DisabledComponents reg key etc - nothing seemed to work.

    My last ditch attempt was to turn off IP6 on the HyperV Host (left IP6 enabled on the virtual I was installing Exchange on).
    That worked a treat for me.

    So - disable ip6 on the host. set the reg key DWOD 'DisabledComponents' to 0xffffffff and it'll work.

    .. Ken


    • Edited by kjhughes097 Thursday, July 25, 2013 11:50 AM syntax
    Thursday, July 25, 2013 11:50 AM
  • Hello Steve. Could you resolve this problem or not?
    Wednesday, February 19, 2014 1:26 PM