cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
342
Views
10
Helpful
3
Replies

Exchange services don't start automatically

abulatkin
Level 1
Level 1

Hello,

I have a Unity 4.0.4 VM, everything is in a separate domain on one server. I have problems with MS Exchange System Attendant (and due to dependency Information Store and MTA Stacks) service starting automatically on system startup. Wen I logon and start them manually they start OK.

Diagnostic tracing gave me the following event:

The Metabase Update service failed to start, error '80040a01'.

For more information, click http://www.microsoft.com/contentredirect.asp

I tried the solution suggested by Microsoft at

http://support.microsoft.com/default.aspx?scid=kb;en;314294

(I've assigned the user rights) but this didn't help.

I've seen some folks complaining about the same problem with Exchange 2000 SP3.

The workaround I've come up with so far is scheduling task that would run the following batch file at startup

@BigR off

net start msexchangesa

net start msexchangemta

net start msexchangeis

Does anyone know about this problem and if Cisco suggests a better workaround? Will Cisco Unity be supported by TAC if I use this scheduled task?

3 Replies 3

Hin Lee
Cisco Employee
Cisco Employee

I think this might be a better workaround. http://support.microsoft.com/default.aspx?scid=kb;en-us;312859

1. Start Registry Editor (Regedt32.exe).

2. Locate and click the following key in the registry:

HKEY_LOCAL_Machine\System\CurrentControlSet\Services\MSExchangeDSAccess

3. 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

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.

I had exactly the same errors on a new 4.0.4 install. This info sorted this out a treat.

Thanks

Had the same problem and this solved it!!!!

Thanks hinho