Unable to start Microsoft Exchange System Attendant

[Brysk]

I am using MS Exchange 2003 on a Windows 2003 server.

Since 15 minutes I am not able to restart service "Microsoft Exchange System Attend"

----
Microsoft Exchange System Attendant was unable to find the Exchange server object named 'HERMES' in the Active Directory. All known Domain Controllers were checked for this object.

For more information, click

http://www.microsoft.com/contentredirect.asp.

----
Microsoft Exchange System Attendant failed to start Exchange server 'HERMES'. Error code '0x8007200a'.

For more information, click

http://www.microsoft.com/contentredirect.asp.

----
Unexpected error The specified directory service attribute or value does not exist. Facility: Win32 ID no: 8007200a Microsoft Exchange System Attendant occurred.

For more information, click

http://www.microsoft.com/contentredirect.asp.

----

Please I need help

 

[markdmac]

Sounds liek a DNS problem or your Exchange server can not find a Global Catalog.

For starters run NETDIAG and DCDIAG and see what results you get.

I hope you find this post helpful.

Regards,

Mark

 

[Brysk]

C:\Documents and Settings\smithe>netdiag

................................

Computer Name: HERMES
DNS Host Name: HERMES.NILP.ENTERPRISE.NORFAL.NET
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
List of installed hotfixes :
KB817789
KB819696
KB823182
KB823353
KB823559
KB824105
KB824141
KB824146
KB824151
KB825119
KB828028
KB828035
KB828741
KB828750
KB831464
KB832894
KB833987
KB834707
KB835732
KB837001
KB837009
KB839643
KB839645
KB840315
KB840374
KB840987
KB841356
KB841533
KB842773
KB867282
KB867460
KB867801
KB871250
KB873333
KB873376
KB883935
KB883939
KB885250
KB885834
KB885835
KB885836
KB885881
KB886903
KB888113
KB890046
KB890047
KB890175
KB890859
KB890923
KB891711
KB891781
KB893066
KB893086
KB893756
KB893803
KB893803v2
KB896358
KB896422
KB896423
KB896424
KB896426
KB896428
KB896688
KB896727
KB897715
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB903235
KB904706
KB905414
KB905495
KB905915
KB910437
Q147222
Q819639
Q828026


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : HERMES.nilp.enterprise.norfal.net
IP Address . . . . . . . . : 142.70.190.183
Subnet Mask. . . . . . . . : 255.255.252.0
Default Gateway. . . . . . : 142.70.191.15
Primary WINS Server. . . . : 142.70.190.176
NetBIOS over Tcpip . . . . : Disabled
Dns Servers. . . . . . . . : 142.70.190.175
142.70.190.176


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed


WINS service test. . . . . : Skipped
NetBT is disable on this interface. [Test skipped].


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Skipped
There are no interfaces that have NetBT enabled. [Test skipped]


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Skipped
There are no interfaces that have NetBT enabled. [Test skipped]


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed


Redir and Browser test . . . . . . : Skipped
There are no interfaces that have NetBT enabled. [Test skipped]


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Passed
Secure channel for domain 'NILP' is to '\\DEIMOS.NILP.ENTERPRISE.NORFAL.NET'
.


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

 

[Brysk]

C:\Documents and Settings\smithe>dcdiag /shobos

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: NILP-CEZ\PHOBOS
Starting test: Connectivity
......................... PHOBOS passed test Connectivity

Doing primary tests

Testing server: NILP-CEZ\PHOBOS
Starting test: Replications
......................... PHOBOS passed test Replications
Starting test: NCSecDesc
......................... PHOBOS passed test NCSecDesc
Starting test: NetLogons
......................... PHOBOS passed test NetLogons
Starting test: Advertising
......................... PHOBOS passed test Advertising
Starting test: KnowsOfRoleHolders
......................... PHOBOS passed test KnowsOfRoleHolders
Starting test: RidManager
......................... PHOBOS passed test RidManager
Starting test: MachineAccount
......................... PHOBOS passed test MachineAccount
Starting test: Services
......................... PHOBOS passed test Services
Starting test: ObjectsReplicated
......................... PHOBOS passed test ObjectsReplicated
Starting test: frssysvol
......................... PHOBOS passed test frssysvol
Starting test: frsevent
......................... PHOBOS passed test frsevent
Starting test: kccevent
......................... PHOBOS passed test kccevent
Starting test: systemlog
......................... PHOBOS passed test systemlog
Starting test: VerifyReferences
......................... PHOBOS passed test VerifyReferences

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : NILP
Starting test: CrossRefValidation
......................... NILP passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... NILP passed test CheckSDRefDom

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running enterprise tests on : NORFAL.NET
Starting test: Intersite
......................... NORFAL.NET passed test Intersite
Starting test: FsmoCheck
......................... NORFAL.NET passed test FsmoCheck

C:\Documents and Settings\smithe>

 

[Brysk]

I got this error too

Metabase Update failed to properly initialize its context. It will retry initialization every 60 seconds until succeeds or shutdown is requested.

For more information, click

http://www.microsoft.com/contentredirect.asp.

 

[markdmac]

Did you recently demote another Exchange server?

I hope you find this post helpful.

Regards,

Mark

 

[markdmac]

I found one article that talked about a similar problem. Give this a try.

To work around this issue, create a new, bogus, disabled ASPNET account. To create this user account, follow these steps: 1. Start the Active Directory Users and Computers utility, and then locate the container where you want to create the new user account.
2. Right-click the Users container (where Users is the container that you want to create the user account in), point to New, and then click User.
3. In the First name box, type ASPNET , type ASPNET in the User logon name box, and then click Next.
4. Type a password for this account in the Password and the Confirm password boxes, click to clear the User must change password at next logon check box, click to select the Account is disabled check box, and then click Next.
5. Click Finish.


I hope you find this post helpful.

Regards,

Mark

 

[Brysk]

No...
When I start Best Pratice Analyser Tool, I have this error "No Exchange Organisation Container found in Domain", our domain is a child, I not able to check if the exchange server on the top of the forest is working.
I dont know what to check in the DNS, I am not able to find a MX record. Can you pinpoint in the right direction.

 

[Zelandakh]

Your IP says you've got a public IP with a public DNS. Is that right?

 

[markdmac]

OK, I think your priority here should be to contact the folkes that manage the parent domain and verify what changes have been done.

If there is no listing in AD then the problem is not with your server. Use ADSI Edit to open up AD just to verify that this is truly the case.

You will find Exchange in

Configuration Container/Services

While you are trying to reach the parent domain admins, check out the DNS settings on your Exchange server. They should only list internal DNS servers and not any ISP DNS. Your DNS Server should point ot itself on its NIC and the DNS Server Snap-In should list the ISP DNS on the Forwarders tab.

A missing MX record won't stop exchange from starting (but will prevent you from getting mail).

Sorry to say I will be away from a PC for a few hours now. Hopefully someone else can pick up this thread.

Just for the clarification of any that may follow, you ran the DCDIAG and NETDIAG from the Exchange server right?

What was done on the network prior to things going bad?

I hope you find this post helpful.

Regards,

Mark

 

[Brysk]

I dont know what is a public IP or even a public DNS, I am not able to contact our sysadmin, I've check in the DNS server I see my exchange server, I have create a MX record with my exchange server but without any result.

 

[Brysk]

ADSIedit.msc

Under Configuration - Service, I am not able to see Exchange...
DCdiag et netdiag have been under exchange server.

 

[markdmac]

Don't waste time with the MX record at this point. As I said it has nothing to do with your server not running.

If you have no Exchange attributes in your AD then somebody may have done an authoritative restore using an old backup or they may have simply deleted information. Either way it is really bad and you should be looking at your Disaster Recovery process.

You could attempt to reinstall Exchange on top of the existing install, however I am doubtful this will resolve your issue as the problems sound like they have originated from beyond your area of control.

You may need to consider contacting Microsoft for support if you are unable to get the right resources internally.

Best of luck.

I hope you find this post helpful.

Regards,

Mark

 

[Brysk]

I see CN=Microsoft Exchange but it is not container class.

I will wait until tomorrow, to be able to contact the other sysadmin thank for your help.

 

[Brysk]

If I go to the properties of CN=Microsoft Exchange, I receive this error : An Invalid Directory Pathname wass passed"
Anyone...

 

[Brysk]

Even more information...

Event Type: Error
Event Source: MSExchangeMU
Event Category: General
Event ID: 1047
Date: 19/12/2005
Time: 8:42:38 PM
User: N/A
Computer: HERMES
Description:
Metabase Update failed to properly initialize its context. It will retry initialization every 60 seconds until succeeds or shutdown is requested.

For more information, click

http://www.microsoft.com/contentredirect.asp.