01-23-2003 06:07 PM - edited 03-12-2019 10:24 PM
MS Exchange SA is set for Automatic (uses Local System account to logon), but fails to start. MS ExchangeMTA Stacks is set for Automatic (uses Local System account to logon), but fails to start. MS Exchange Information Store is set for Automatic, (uses Local System account to logon) but fails to start. After server completes the OS load process, I can manually start each Exchange service (without any errors). I can then start AvCsMgr manually and Unity is up and running.
01-23-2003 06:43 PM
Do the Exchange services stall out waiting for the NIC drivers to get their groove on? I've seen that before on some servers in the field - it took so long to finish initalizing that the services just timed out - are the retry times in the SCM for those services set or do they just give up after the first failure?
01-23-2003 07:33 PM
Hi Jeff,
I did some more poking around in the Microsoft Knowledge Base and discovered an article which appears to hit our issue. Here is the details. It fixed my problem.
Here is the link:
http://support.microsoft.com/default.aspx?scid=kb;en-us;312859
partial details of link...
Start Registry Editor (Regedt32.exe).
Locate and click the following key in the registry:
HKEY_LOCAL_Machine\System\CurrentControlSet\Services\MSExchangeDSAccess
On the Edit menu, click Add Value, and then add the following registry value:
Value name: TopoCreateTimeoutSecs
Data type: REG_DWORD
Radix: Decimal
Value data: 600
Quit Registry Editor.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide