Exchange Server Forums
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Windows Server 2008 RTM
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
 Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
|
|
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
|
Windows Server 2008 RTM - 13.Feb.2008 11:09:15 AM
|
|
|
Linke Loe
Posts: 17
Joined: 1.Oct.2003
From: Netherlands
Status: offline
|
Hi,
I'm trying to install Exchange Server 2007 on Windows Server 2008 RTM, but several services are unable to start. I get the following events every minute:
Event ID: 2101
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3400). The configuration domain controller specified in a call to SetConfigDCName (E2k7-test.e2k7.local) is unreachable. Exchange Active Directory Provider will select the configuration domain controller from the list of available domain controllers.
Event ID: 2080
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3400). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
(Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
E2k7-test.e2k7.local CDG 1 0 0 1 0 0 0 0 0
Out-of-site:
Event ID: 2114
Source: MSExchange ADAccess
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=3400). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event dedscription. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
I have searched the Internet for these events, but there's not much to be found when it comes to Exchange 2007 on Windows 2008. Does anyone have an idea?
Thnx.
|
|
|
|
|
RE: Windows Server 2008 RTM - 13.Feb.2008 1:11:33 PM
|
|
|
Linke Loe
Posts: 17
Joined: 1.Oct.2003
From: Netherlands
Status: offline
|
I followed this article, although there's nothing in it I didn't already know... Installing Exchange is a pretty straightforward procedure. On Windows Server 2003 I have no problem at all, but it seems on Windows Server 2008, there is a problem finding the right Active Directory objects...
|
|
|
|
|
RE: Windows Server 2008 RTM - 13.Feb.2008 3:05:54 PM
|
|
|
Linke Loe
Posts: 17
Joined: 1.Oct.2003
From: Netherlands
Status: offline
|
Another stupid Microsoft thing...
http://www.mcpblog.net/Lists/Posts/Post.aspx?ID=36
I've re-enabled IPv6, rebooted the machine and all service were started....
Thnx anyway.
|
|
|
|
|
RE: Windows Server 2008 RTM - 17.Feb.2008 6:07:46 PM
|
|
|
froos
Posts: 1
Joined: 17.Feb.2008
From: Netherlands
Status: offline
|
quote:
ORIGINAL: Linke Loe
Another stupid Microsoft thing...
http://www.mcpblog.net/Lists/Posts/Post.aspx?ID=36
I've re-enabled IPv6, rebooted the machine and all service were started....
Thnx anyway.
Bloody incredible.. I have been banging my head against the walls why the f**k it didn't work. I am actually moving from a windows 2003 server with ex2k7SP1 to a new server with win2k8 and ex2k7sp1 and on the new server had all kinds of strange reports.. Exchange didn't find the GC in the network, claimed there was no writable domain controller, all kinds of strange shit.
Now I enabled IPv6 again and all is working!! what kind of a ******** bug is that?? :S Sorry, I've been at this for about a week now and this is very relieving :)
BTW, policytest is still not responding properly, I get this response:
==============================
LookupAccountName returned error 1332
Abnormal exit from PolicyTest
==============================
If anyone has a clue what that is, give me a yell. :)
other than that, thanks for the brilliant idea
Cheers,
|
|
|
|
|
RE: Windows Server 2008 RTM - 30.Mar.2008 9:35:50 PM
|
|
|
kluken
Posts: 7
Joined: 30.Mar.2008
Status: offline
|
I just had same issue! Tgod for this post!! The Exchange 2007 Dev and QA team needs to be shot!! This product is full of BS oddities and quirks. I am so damn sick of this product, 15 months old and 6+ roll ups and a SP, come on this is by far the biggest crap they have released. If the SQL 2008 tema plans on doing this I'll stick with W2300 Ex2003 and SQL 2005 !!
|
|
|
|
|
RE: Windows Server 2008 RTM - 10.Apr.2008 11:30:02 AM
|
|
|
matiasnino
Posts: 1
Joined: 10.Apr.2008
Status: offline
|
Wow. God bless this thread for saving me days and days of potential Exchange installation agony.
I had the same issue. After installing Server 2008 I disabled IPV6 (cause I DON'T USE IT ON MY NETWORK). Of course when I tried to install Exchange 2007SP1(I'm doing a transition from server2k3+e2k7sp1 to s2k8+e2k7sp1), hub transport service failed when when installing. I damn near pulled out my hair out for a good 5 hours.
I had an inkling something was wrong with ipv6 because when I saw the event log claim that the configuration domain controller couldn't be found, I though, "That's bullcrap, I can ping it right now! See! ..." and when I make the server ping itself, the IP responds with an IPV6 address. Very odd considering I had IPv6 DISABLED!
Oh well. I guess these are the pains of early adoption. After all, Server 2008 has only been around for 2 months. You'd think this would've been taken care of after literlly YEARS of beta testing.
Ok. Wish me luck on the rest of my install!
|
|
|
|
|
RE: Windows Server 2008 RTM - 20.Sep.2008 4:31:27 PM
|
|
|
AndrewW
Posts: 1
Joined: 20.Sep.2008
Status: offline
|
OMG! I have never been more frustrated with a Microsoft Product than this one. I spent the last 4 days, lost reveunes and email trying to get the damn Exchange Server 2007 SP1 installation to work to simply find out that disabling the IPv6 protocol was the cause! Sure enough, I re-enable and it all works.
Why did I disable the IPv6 protocol in the first place, you ask? Because Exchange Server 2007 SP1 Setup warned me about using a dynamic IP address issue even when I had assigned a static IP address using the IPv4 protocol. So, I simply disabled the IPv6 protocol and no longer got the nagging warning message about and unassigned static IP address.
How retarded! Microsoft needs to the fix this issue ASAP!
Anyway, thank you so much for your insight!!! I almosted gave up. I was about ready to label it "bleeding-edge" and almost reverted back to Windows 2003 Server and Exchange 2003 Server. What a nightmare this has been.
So in an effort to help future installers of this issue, I will provide the keywords in hopes Google snags this post and hopefully helps other installers from this retarded situation.
Keywords: Exchange Server 2007 SP1, Windows 2008 Server, MSEXCHANGEADTOPOLOGYSERVICE.EXE
Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1880). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
RE: Windows Server 2008 RTM - 