Windows 2008: Transaction support within the specified resource manager is not started or was shut down due to an error.

Follow me Yesterday a client reported an issue that they are unable to create schedule task on a SBS 2011 server, upon checking I found that the schedule task wizard launches fine and goes almost till completion and just as we click on finish we get the following error. Transaction support within the specified resource manager is not started or was shut down due to an error. I felt very lucky when with the first google search I stumbled upon various blogs and articles including Microsoft suggesting the corruption in transaction manager log and  the following command (from command prompt) to resolve the issue quick. fsutil resource setautoreset true c:\ Pumped with adrenaline, I performed the command (from command prompt) and rebooted the server but unfortunately the issue persisted upon the reboot. I did try the reset a couple more times & of course multiple reboots with no success. I went ahead and checked the event viewer which also was giving multiple error while loading. I did find multiple errors in it, mostly about Windows search service failing the start mostly because of again some transaction log. Refer the error events below Event ID 7034: The Windows Search service terminated unexpectedly.It has done this 12 time(s). Event ID 7023 The Windows Search service terminated with the following error: Transaction support within the specified resource manager is not started or was shutdown due to an error. Event ID 1006 The Windows Search Service has failed to create the new search index. Internal error <10, 0x80071a91, Failed to save Crawl Scope Manager changes: >. Event ID 1029 Windows Search Service failed to process the...

SBS 2008: Exchange Services Down with event id 2114 error 0x80040a02 (DSC_E_NO_SUITABLE_CDC)

Follow me Let me begin by saying that SBS servers are my least favourite ones and with Windows 2008 i.e. SBS 2008 its icing on the cake 🙂 .  Anyways, so a client reported with SBS 2008 server that Exchange services are down. Upon checking the server we found the following state The Server is unbearably slow and not responding at all Information storing service is stuck on Starting state System Attendant service is stuck on Stopping 🙂 We tried restarting the server in safe mode and were unable to login with Error “No Logon server available” We also tried safe mode with networking and failed with error “Netlogon service not started” PS: For Domain controller we should have tried to login to DSRM mode instead of SafeMode because on a DC, local SAM is disabled. I forgot to do that but just putting it here for other’s reference. We booted the server back to Normal mode and connected to services snap-in from another machine in the domain. We went ahead and disable all the Exchange & SQL services on the server. Apart from this we also did a clean boot on the server and rebooted it . (Refer Article, How to cleanboot) This time-server came back up quite fast and also it was responding OK.  We executed DCdiag on the server and found it to be clean.  Tried starting exchange services but the services failed to start. Upon examining the event viewer we found event Id 2114 with following error repeatedly Process MAD.EXE (PID=6276). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP)...