• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7069
  • Last Modified:

Error 1068 : the dependency service or group failed to start.

This weekend th Exchange 2000 SP3 server went down.
The information store would not start again nor the system attendant. The database was corrupted but already got to fix it now it is in clean state.
The error i am getting is Error 1068: the dependency service or group failed to start.
I have read something about changing passwords but no password has been changed. I actually tried to start it with the administrator user and would not start either.
Tks
0
howtodoit
Asked:
howtodoit
  • 10
  • 9
1 Solution
 
rakeshmiglaniCommented:
which exchange service is not starting?
0
 
howtodoitAuthor Commented:
The systen attendant does not start and does not return an error.
Here is all I found on the application log. I copied the most important in reverse order (what is first in the transcript is what happened earlier).

Microsoft Exchange System Attendant is starting. Microsoft Exchange Server System Attendant, service startup complete, version 6.0 (build 6249.0).
-----------
Microsoft Exchange System Attendant is initializing 'DSACCESS.DLL'.
--------------
Process MAD.EXE (PID=4852).  DSAccess initialized successfully.
--------------
Unable to get the AppleTalk network address of the Microsoft Exchange Server computer.
-----------------
Virtual machine xxxxxxx is starting with flags 0x00000001.
------------
Microsoft Exchange System Attendant has been started for Exchange server 'EFEXSERVER' successfully.
------------
Microsoft Exchange System Attendant is initializing 'DSPROXY.DLL'.
-----------

The Directory Service Referral interface (RFRI) started successfully.
---------------------------
The MAD Monitoring thread is initializing.
------------------------------
The MAD Monitoring thread was unable to connect to WMI, error '0x8004100e'.
--------------------------------
Unexpected error The specified domain either does not exist or could not be contacted. Facility: Win32 ID no: c007054b Microsoft Exchange System Attendant  occurred.
---------------------------
Microsoft Exchange System Attendant failed to start.
-------------------------------
Permanent failure reported by policy group provider for 'CN=System Policies,CN=Efex,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=efex,DC=us':'MAD.EXE', error=80040103.  Taking provider offline.  
---------------------------------
Permanent failure reported by policy group provider for 'CN=System Policies,CN=Efex,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=efex,DC=us':'MAD.EXE', error=80040103.  Taking provider offline.  
--------------------------
Virtual machine EFEXSERVER is stopping.  
---------------------------
Microsoft Exchange System Attendant has been stopped for Exchange server '' successfully.
---------------------------
he Directory Service Referral interface (RFRI) stopped cleanly.
---------------------------
Process MAD.EXE (PID=4852). DSAccess is shutting down.
---------------------------



0
 
rakeshmiglaniCommented:
there appears to be a communication problem between the exchange server and DC
try to install and run the following MS tool
Microsoft Exchange Best Practices Analyzer v2.8
http://www.microsoft.com/downloads/details.aspx?familyid=DBAB201F-4BEE-4943-AC22-E2DDBD258DF3&displaylang=en
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
howtodoitAuthor Commented:
installed
0
 
howtodoitAuthor Commented:
Cannot connect to the Windows Management Instrumentation (WMI) repository on serverxxxxx. This could be the result of a network or permissions problem. Error: The type initializer for "System.Management.ManagementPath" threw an exception.
0
 
rakeshmiglaniCommented:
is the WMI service started on the exchange server?
0
 
howtodoitAuthor Commented:
WMI = Windows Management Instrumentation right?
If it is, yes it is started. I have just restarted the server but same thing happens.
I tried restarting the WMI and then starting the attendant but nothing happens,same error.
0
 
rakeshmiglaniCommented:
is the communication between the exchange server and DC working fine?
try to run dcdiag and netdiag to check that.
0
 
howtodoitAuthor Commented:
cant find them. Where do i run them from?
0
 
howtodoitAuthor Commented:
i got to run the ntdiag
It is telling me it is not finding a DC for my domain.
DC Discovery Test........................Failed
[fatal] Cannot find DC in domain xxxx. [error no such domain]
0
 
rakeshmiglaniCommented:
the exchange server is not able to contact the DC.
have you tried rebooting the DC/GC?
are you able to ping the DC/GC by name and ip address from the exchange server?
0
 
howtodoitAuthor Commented:
Yes, that seems to be the problem.
It's getting worse every minute. The problem seems to be in the DC part of the server. exchange and DC are in the same server.
I got it offline and using a provisory server while i "rebuild".
I am trying to make a bkup but as the attendant is not up, I cannot do it. Will it be enough copyin the directory MDBDATA ? what else should I "copy" in order to be able to restore the mailboxes later.
Regards
Alex
0
 
rakeshmiglaniCommented:
a backup will not work if the exchange services are not running
by default mdbdata folder has the exchange databases and log files
but you check whether the logs and databases are in a different folder
search for the .edb and .stm files as these are file extentions of the exchange databases
secondly check the location of transaction log files. if they all are in the same folder then you can take a backup of that folder
also, if you going to rebuild the box, make sure that you use the same exchange ORG and AG name.
0
 
howtodoitAuthor Commented:
All the log files and edb files are in the same directory, which is now backed up.
Now, I got a new server with W2K3 and exchange 2K3. The only thing I have is that directory, as the w2K is already all gone. How should I do to "recover" what is in there?
0
 
rakeshmiglaniCommented:
is this win2k3 server also a DC?
earlier you had exchange 2000 and now you have exchange 2003. is that correct?
did you create a new domain or added this win2k3 to the old domain?
0
 
howtodoitAuthor Commented:
Creatred everything new. The old DC went dead as a DC. I can boot the PC but wont work as a DC
I had W2k with exchange 2K.
Now: w2k3 with exchange 2k3 and I even changed the domain
0
 
rakeshmiglaniCommented:
so you did not restore the AD as you created a new domain
what about the exchange orginazation name and administrative group name?
are they the same as the old setup?
0
 
howtodoitAuthor Commented:
No, I changed them both
0
 
rakeshmiglaniCommented:
that might create a problem then.
if you try to mount these stores on the new server you will get event id 1088 in the app logs telling you that legacydn does not match
the work around is mentioned in
http://support.microsoft.com/kb/324606
http://technet.microsoft.com/en-us/library/bb267025.aspx
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 10
  • 9
Tackle projects and never again get stuck behind a technical roadblock.
Join Now