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

Transfer FSMO Roles- using GUI or Cmd Line

Follow me Active Directory has five special roles which are vital for its smooth running as a multimaster system. Some functions of AD require there is an authoritative master to which all Domain Controllers can refer to. These roles are installed automatically and there is normally very little reason to move them, however if you demoting a DC and DCPROMO fails to run correctly or have a catastrophic failure of a DC or you are Installing a new DC that is a lot more powerful than your old DC, you will need to know about these roles to recover or transfer them to another DC. The Five FSMO roles are divided in two Categories as shown in Image below The Roles There are five FSMO roles, two per forest, and three in every Domain. Forest Wide Roles:   Schema Master The schema is shared between every Tree and Domain in a forest and must be consistent between all objects. The schema master controls all updates and modifications to the schema. Domain Naming When a new Domain is added to a forest the name must be unique within the forest. The Domain naming master must be available when adding or removing a Domain in a forest. Domain Wide Roles: Relative ID (RID) Master Allocates RIDs to DCs within a Domain. When an object such as a user, group or computer is created in AD it is given a SID. The SID consists of a Domain SID (which is the same for all SIDs created in the domain) and a RID which is unique to the Domain. When moving objects between...

Windows Server Backup on failing with Errors “Incorrect Function” and “There was a failure in preparing backup image of….”

Follow me Recently I got an opportunity to configure a windows 2012 R2 server backup on an external NAS, We were trying to set up the backup on a Buffalo NAS and also tried WD Cloud EX4 NAS. In both the case we ran into different error, this article suggest how we worked around the error to get the backup going for the server. We were trying to store the backup on a network location on both the NAS and we ran into following errors in both the cases WD Cloud EX4 NAS: The backup process started but then immediately failed with the error “Incorrect Function” and “There was a failure in preparing the backups image of one of the volume”. I checked the WD forums for solution but found that a lot of people are facing same error with no solution. Refer to error screenshot below The Buffalo NAS gave an error “ The Version does not support this version of the file format”   when researched we found that it’s a known issue and needed NAS to be rooted which I wasn’t willing to do to customer’s NAS. See the discussion below, in this reference http://blogs.technet.com/b/asiasupp/archive/2010/11/03/windows-server-backup-failed-with-error-quot-the-version-does-not-support-this-version-of-the-file-format-quot.aspx http://forums.buffalotech.com/index.php?topic=10737.0 Anyways, now that we know that both the NAS have their own issue we decide to set up the backups using a different approach. We decided to use a ISCSI LUN to store the backups. Fortunately our WD NAS had the option to create a LUN. If you have any other NAS, you need to find out how to create a LUN on it. Refer to following screenshot where we accessed...

Managing Server Core

Starting with Windows Server 2008, Microsoft brought new concept the Server Core, they suggested when the servers are only used to host applications and you generally do not have to do any other work on them, so why to waste their resources on unnecessary GUI. Its something like VW reducing 200 Kgs of weight off a 3 ton SUV and calling it more frugal and fuel-efficient. Anyway’s, I will keep my automobile passion off this article and will just talk about my latest encounter with a Windows 2008R2 Core. Yes, despite of numerous servers I come across in my Day to Day life only very rare of them are Windows Server Core, The situation was very typical, this Windows 2008R2 Core was actually a Hyper V server, it had a couple of machines on it and one of the virtual’s was the ONLY Domain Controller of the very same domain of which this server was a Part. Yes this wasn’t the most perfect domain design which one can ask for.  Client was use to of managing HyperV from another Windows 2008R2 Member Server in same domain. As it was destined the Domain controller running on this Hyper V crashed and the authentication for clients, including the admin access to the this Core server (using the domain admin account) wasn’t working.  At this situation I did quite a lot of research about various aspects of Managing or troubleshooting a Server Core, here is a crux of all that I found about managing Server Core Facts about Server Core: It’s a full fleshed server except that it doesn’t have a GUI...