TechNet - Только для профессионалов. Специально для Вас. >
Форумы
>
Exchange Server 2010
>
Hub Transport Role Install Fail error # 2147504141
Hub Transport Role Install Fail error # 2147504141
- 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
Ответы
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- Помечено в качестве ответаSteve SinchakMVP17 апреля 2009 г. 18:37
Все ответы
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- Помечено в качестве ответаSteve SinchakMVP17 апреля 2009 г. 18:37
- Steve,
What happens when you try installing the HT role again?
Microsoft Exchange MVP | http://exchangeexchange.com 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- Предложено в качестве ответаAnatoly Ivanov 23 апреля 2009 г. 17:17
- 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 - 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 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- 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.
- what is the service pack status on 2k8?
Exchange 2010 requires Windows Server 2008 with SP1...
regards,
Exchange - MVP / TURKEY - Yep, sp1 installed and all updates from WU.
- 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. - 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 - ya, the same problem i met with IPv6
this is funny from ex2007.. - 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! - 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 - 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!
- Предложено в качестве ответаbarisca 17 апреля 2009 г. 12:56
- 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 ? - Hi Steve,
I tried the same way you did. I aggreed your number 9 result - 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! - you are right Steve. static IPv6 address works fine
- 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. - 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
- Open Registry Editor.
- Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
- In the details pane, click New, and then click DWORD (32-bit) Value.
- Type DisabledComponents, and then press ENTER.
- 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 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.
-Greghi 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
- 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. - 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 - 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.
- 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 - 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). - 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 - 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 - 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- Предложено в качестве ответаMumin CICEKMVP25 мая 2009 г. 7:04
- 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 - 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 - 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 - I would suggest a format and start clean install windows ... this will spare you much time in debugging.
IT System Engineer / MCSA / MCSE 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- Dsiable IPV6 from all the places before you start any exchange installation. This did it for me.
IT System Engineer / MCSA / MCSE - 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 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. :-(
- Dear Forum members, please put some light on this issue ???
Zahir - 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
