From: Susan on 10 Feb 2005 19:18
you must find out why the directory service is not starting...without that
info, you have nothing to point you in the right direction...
"Fan Fan" <ffan102(a)hotmail.com> wrote in message
> Thank you again for the timely reply. Yes, the rebuilt-Exchange-Server is
> identical to to the one that crashed with the same Organization name, Site
> name etc. I checked all of the event logs and all error events are
> to the Exchange direcroty service not being able to start. The most
> one was event ID 7022 that says 'The Microsoft Exchange Directory Service
> Hung on Starting'. Please help.
> - Fan
> "Susan" <susan(a)nospam.com> wrote in message
> > did you check the app log and the system log? did you rebuild the
> > exactly as it needed to be rebuilt, and install Exchange with the exact
> > same
> > Org and site names?
> > "Fan Fan" <ffan102(a)hotmail.com> wrote in message
> > news:u$o%23Gr8DFHA.2608(a)TK2MSFTNGP10.phx.gbl...
> >> Susan,
> >> Thank for the help. I did the restore from the Exchange 5.5 backup
> >> after I read your post without over-written the existing Exchange
> > directory.
> >> I don't get the DS_E_INSUFFICIENT_ACCESS_RIGHTS error any more.
> > the
> >> Directory Service service won't start with 'error 1067 - The Microsoft
> >> Exchange Direcroty Service Hung on Starting'. At the event log, it
> >> Event ID 7022 with the same message. Any idea? Thank you.
> >> -Fan
> >> "Fan Fan" <ffan102(a)hotmail.com> wrote in message
> >> news:OIGbcR6DFHA.3032(a)TK2MSFTNGP12.phx.gbl...
> >> > Our ONLY Nt4.0 domain controller crashed so was the Exchange Server
> >> > due to power failure. We rebuild the NT4.0 dc and the Exchange Server
> > 5.5
> >> > from scratch. The ExchangeAdmin Domain account (same account with the
> > one
> >> > before the crash) was created and given the domain admin rights and
> >> > also
> >> > used as the Exchange 5.5 service account. All of the Exchange
> >> > started fine before the restore of the backup from the
> >> > creashed-Exchange
> >> > SErver. (unfortunately, we did not backup the NT40 before the crash)
> > after
> >> > the restore is done, the information store service refuce to start.
> >> > Then
> > I
> >> > ran the ISINTEG -patch to fix the database and I got the
> >> > DS_E_INSUFFICIENT_ACCESS_RIGHTS error and said the database can't be
> >> > updated. I know what the problem is: even though the service account
> >> > with the same name but the sucurity ID is different. Anybody know how
> >> > to
> >> > work around? I apprecate your help.
> >> >
> >> > Fan
> >> >