I DID IT!!!
Navigating de Microsoft KB, I have found this article: Q312859. In this
article explains how to increase the time out the service MExchangeSA has to
start. By default this time is 60 seconds. By increasing this time to 600
seconds, all works fine.
Alternatively, if you install Exchange 2000 SP2 or later, modify the default
topology detection timeout registry value setting. This registry value is
not present by default. If this registry value is not present, Exchange 2000
uses a value setting of 0x3C (60 decimal) seconds.
To modify the default topology detection registry value:
1.. Start Registry Editor (Regedt32.exe).
2.. Locate and click the following key in the registry:
3.. On the Edit menu, click Add Value, and then add the following registry
Value name: TopoCreateTimeoutSecs
Data type: REG_DWORD
Value data: 600
4.. Quit Registry Editor.
A value setting of 600 seconds is a good starting setting, but you can
reduce this setting if you want. This new registry value setting does not
indicate that Exchange 2000 services (which depend on DSAccess) take 10
minutes to start; instead, this value indicates that DSAccess has 10 minutes
to discover the topology.
Thanks for your interest.
> Hello Don.
> I was installing a new Windows 2000 Server in order to migrate our actual
> Windows NT 4 to Windows 2000. After the problems I mentioned I reinstall
> server completly, but I have't installed E2K SP3 yet.
> What I remember about the problem is that the Information Store Service
> the MTA Stacks Service didnt start because the System Attendant had not
> Ill make tests with a virtual machine (using VMWARE) and a will post a
> message with the results.
> Thak you very much.
> I?igo Gonzlez
> ODEI S.A.
> > Hello,
> > When the Exchange 2000 server reboots, take a look at the application
> > and see if you're getting any error messages. If you do get error
> > regarding Exchange 2000 server, kindly post back the specific error
> > on this thread.
> > Also, something came to my mind.
> > If you do get error messages upon startup, see if the error message
> > to the following KB articles:
> > Q325964 XADM: System Attendant Service Does Not Start, Error 9022
> > http://support.microsoft.com/support/kb/articles/q325/9/64.asp
> > Q280432 XADM: System Attendant Stops Working with a 9022 Event
> > http://support.microsoft.com/support/kb/articles/q280/4/32.asp
> > I look forward to hearing from you.
> > Thank you and have a nice day.
> > Sincerely,
> > Don Tan, MCSE/MCSA
> > Microsoft Online Support Professional
> > Get Secure! - www.microsoft.com/security
> > This posting is provided "AS IS" with no warranties, and confers no