Hi I was getting an extended error on my secedit.sdb and so i researched this and found that it could be corrupted as well as the edb.chk and/or edb.log . So i renamed secedit.sdb, edb.chk, edb.log and res1.log and res2.log, rebooted the server and ran the command: secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose Now its just stuck at 4% completed. Its been like this for over 30mins. Is it supposed to take a long time to complete? Thanks in advance Raymond

I've not done it before but I'd restart the replication services in this case.

It finished but with errors. I now can't start my Exchange MTA service and Information Store. Keep getting a 1053 time out error.

is it Exchange 2003 or 2007? check the dependencies of MTA service and make sure they are running too. worst case re-start the server if possbile.

It's exchange 2003. I checked the dependencies of the MTA service and they are running. Tried restarting the MTA service, still getting an error. I have rebooted the server and still nothing.

At this point I'd suggest you to call Microsoft, I'm not sure what to check now.

How’s the issue currently? Please increase the diagnostics logging on the MTA and IS component, reproduce the timeout error, and then see if there’s any related error event in the application log Please run ExBPA against the exchange server for health checkPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.