Solved

Exchange 2003 Server Status 'Unreachable'

Posted on 2004-08-30
16
3,219 Views
Last Modified: 2008-01-09
I have two DC's. One of them has Exchange 2003 running on it. I was told when I installed Exchange that installing it on a DC wouldn't be a problem, but I'm finding out now that it can be. Anyways, the problem I am trying to resolve now is why it is telling me that my server is 'Unreachable' when I try to view it's status (under 'Tools' in the System Manager). The admin group that it's displaying is 'First Administrative Group'. Could the error I'm getting in the event logs have something to do with it? The error in the event log is MSExchangeSA, Event ID 9098, the MAD Thread was unable to read its configuration from the DS, error '0x80041010'.
0
Comment
Question by:Grime121
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
  • 4
16 Comments
 
LVL 12

Expert Comment

by:ColinRoyds
ID: 11935114
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 11935247
How do you have your DNS configured? Do you have them hard coded in the network settings?
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 11935346
here is some information regarding the error - http://www.eventid.net/display.asp?eventid=9098&eventno=785&source=MSExchangeSA&phase=1

From the Event ID site ...

This error showed up after an install of Exchange 2000. The install had failed midstream with a COM+ error code 0xc103798a. The event log then produced these 9098 errors (if you choose to continue the install and not to abort). It indicates that there may have been a failure when registering "cdowfevt.dll", according to Q296095. I double-checked that it was the most up to date version from the latest Exchange 2000 Service Pack. I then manually registered this DLL from the command prompt with no problem. I then checked out the Exchange 2000 setup log and found this: “The command C:\WINNT\System32\WBEM\mofcomp.exe -n:root\cimv2\applications\exchange "C:\WINNT\System32\WBEM\wbemcons.mof" failed, returning error code 1 (Incorrect function.)”.
I found that there were two files missing from the Exchange install, these two files, “wbemcons.mof” and “wbemcons.dll” belong in the “c:\winnt\system32\wbem” directory. I copied these two files over and ran the following command: “C:\WINNT\system32\wbem>mofcomp -N:root\cimv2\applications\exchange c:\winnt\syst em32\wbem\wbemcons.mof”. The outcome was the following: “Parsing MOF file: c:\winnt\system32\wbem\wbemcons.mof
MOF file has been successfully parsed
Storing data in the repository...”.
Then I rebooted the box, reran the Exchange 2000 setup and everything installed without error.

I'm pretty sure the article Colin listed refers to a similar issue ... probably going to need to review the setup logs to identify where the install blew up - reregister the "cdowfevt.dll" file (which seems to be a common denominator of this issue) and rerun the install ... definitely review your setup logs to identify where things went wrong
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 1

Author Comment

by:Grime121
ID: 11935526
Yes, DNS is hardcoded. I don't think it's a DNS error. I think it is a WMI error. Can someone tell me a plain and dry way of wiping out all of the WMI data and then re-registering it all? I tried stopping the WinMgmt service, deleting the repository, and then registering by running 'regsvr32 wbemupgd.dll', but it just spit out about 50 COM+ errors saying that such-and-such file failed to load into the repository. Now I'm missing a BUNCH of repositories, and instead of getting MSExchangeSA event error 9098, I'm getting event error 9097 with error code 0x8004100e. So I followed these instructions trying to get rid of that:  http://support.microsoft.com/default.aspx?kbid=288590 and when I execute the command perscribed in that KB article it tells me...

C:\Documents and Settings\Administrator>%systemroot%\system32\wbem\mofcomp.exe e:\setup\i386\exchange\exwmi.mof
Microsoft (R) 32-bit MOF Compiler Version 5.2.3790.0
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: e:\setup\i386\exchange\exwmi.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while opening the namespace for object 1 defined on lines 10 - 13:
Error Number: 0x8004100e, Facility: WMI
Description: Invalid namespace
Compiler returned error 0x8004100e

I think it's doing that because since the root\cimv2 directory doesn't exist, it can't add the root\cimv2\applications\exchange directory that it loads the classes into. I really need to completely reinstall all of the WMI info it that is even possible. If not, I might just back up the mailboxes and reformat.... What do you think I should try next?
0
 
LVL 1

Author Comment

by:Grime121
ID: 11935877
Bah, back to square one. I waited a little bit and then I tried deleting the repository and then running 'regsvr32 wbemupgd.dll' again, and it worked. Then I tried '%systemroot%\system32\wbem\mofcomp.exe e:\setup\i386\exchange\exwmi.mof' again, and it worked. Then I checked the event logs and I was getting the 9098 error again instead of the 9097. So I figured what the hell and tried the same thing for the other two .mof files in the same directory as exwmi.mof (exmgmt.mof and msgtrk.mof). I got about a 30 of the errors bellow for all different providers, and it didn't fix the 9098 error.

Event Type:      Warning
Event Source:      WinMgmt
Event ID:      63
Description:
A provider, ExchangePublicFolderProvider, has been registered in the WMI namespace, root\MicrosoftExchangeV2, to use the LocalSystem account.  This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

I've been messing with this 9098 error for over 2 weeks now. What do you think about simply backing up the mailboxes and reformating?
0
 
LVL 12

Expert Comment

by:ColinRoyds
ID: 11935991
not a bad idea if this has been going on for that long or phone MS
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 11936010
Given the issues you have with some of the primary DLL's and COM+ ... I'd definitely blow it out and reinstall ...even if you get it resolved it doesn't seem worth the risk nor the extra time ...  I'd reinstall the whole server ...

The real question is can you afford the downtime ... not sure how many users you have on AD etc ...

If you want to reregister WMI and resolve some of the repository errors you can do the following:

Start a command-line session.
Unregister any WMI service (also known as WinMgmt) performance libraries by typing
winmgmt /clearadap
Stop all running copies of the WMI service by typing
winmgmt /kill
Unregister the WMI service by typing
winmgmt /unregserver
Register the WMI service by typing
winmgmt /regserver
Register any WMI service performance libraries by typing
winmgmt /resyncperf


I'd make sure you have a backup of the data on that server before continuing ... you know how it goes, start tinkering and blow something up ... you don't want to lost anything ...
0
 
LVL 1

Author Comment

by:Grime121
ID: 11936049
Ok, I'll give that a shot before I reformat. Downtime shouldn't be an issue. One more question... if I do reformat, should I run dcpromo before or after installing Exchange 2003? I think after, but I want to double-check so I will get a clean installation this time.
0
 
LVL 12

Expert Comment

by:ColinRoyds
ID: 11936110
If you can I would not make it a DC, Exchange is better on it's own as a memeber server. Less to worry about.
0
 
LVL 1

Author Comment

by:Grime121
ID: 11936142
Only have two servers running right now. It's either I make this one the Exchange server as well, or I pull a Dell Demension 2400 out of production and put Exchange on it... I'll add a GB of RAM and do that if you think it that would work better... I think there would be a lot more downtime that way though. Not to mention it would be more likely to fail. The server I have it on now is a brand new PowerEdge 2600.
0
 
LVL 12

Expert Comment

by:ColinRoyds
ID: 11936259
Keep it on the PowerEdge.It's not recommended where possible, but not everyone has the budgets available, so I would rather go with the original idea you had.  
0
 
LVL 1

Author Comment

by:Grime121
ID: 11936305
so dcpromo before or after Exchange installation?
0
 
LVL 12

Accepted Solution

by:
ColinRoyds earned 500 total points
ID: 11936338
I would dcpromo first.  
0
 
LVL 12

Expert Comment

by:BNettles73
ID: 11936899
dcpromo was the answer? hehe I feel slighted!!! =P
0
 
LVL 1

Author Comment

by:Grime121
ID: 11937839
Yeah, I thought about splitting the points, but he had answered a lot of my questions.... Plus, I tried that command line procedure, and it didn't help :(


0
 
LVL 1

Author Comment

by:Grime121
ID: 11937842
Oh yeah, feel free to answer this question though: http://www.experts-exchange.com/Security/Win_Security/Q_21105320.html :)
0

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question